> For the complete documentation index, see [llms.txt](https://traes.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://traes.gitbook.io/docs/polygon-to-sui-bridge/polygon-to-sui-bridge-complete-step-by-step-guide.md).
# Polygon to Sui Bridge: Complete Step-by-Step Guide
First meeting with the Polygon to Sui Bridge? [The Rezentix app](https://rezentix.com/) keeps it to one form and about 5 to 20 minutes. What catches most Polygon users off guard is that both networks start their addresses with 0x, yet a valid Sui destination string runs 66 characters long instead of the 42 characters used on EVM chains.
### Moving Funds Along the Polygon to Sui Bridge
Step 1: Reach the bridge from a trusted link
Use a browser where your Polygon wallet extension is installed, then load [Rezentix](https://rezentix.com/). Mobile wallet users can open it inside the wallet's built-in browser instead.
Step 2: Use Connect Wallet to link your Polygon wallet
Approve the request and check that the wallet shows the Polygon network. A small POL balance should sit in the wallet for fees.
Step 3: Set Polygon and your token in From
Choose the token you want to send from your Polygon balance. If a token you hold is missing from the list, the wallet is usually set to another network.
Step 4: Select Sui in To and add an Amount
Paste the Sui address of the receiving wallet and enter the amount. A Sui address is normally 66 characters with the 0x, against 42 for a Polygon address.
Step 5: Press Swap once the quote matches
Read the amount that will arrive, then press Swap and approve the prompts in order. A token permission can come before the transfer itself.
Step 6: Give the transfer a few minutes
Keep the page open while it runs, and watch the Sui wallet for the incoming balance. A Sui explorer shows it too once it lands.
### What Drives the Cost and the Wait
On the Polygon to Sui bridge, the amount you send is the biggest cost driver, because Polygon network fees are small. A typical total runs about $0.40 to $3, with larger transfers paying more of the bridge's share. A burst of Polygon traffic can nudge the network fee up for a short while.
Timing runs 3 to 10 minutes on most days, mostly spent waiting on Polygon confirmations before funds are released on Sui. The quote shown just before you confirm is the figure to plan around, and this range is only a guide.
### Receiving on Sui: Address Length and Wallet Setup
When you move funds from Polygon to Sui, the receiving wallet must be a Sui wallet, because Sui is not an EVM network. It needs its own account and its own address. A Sui address begins with 0x, as an Ethereum-style one does, but it carries 64 characters after the prefix instead of 40. Copy it using the Sui wallet's Receive button, and compare its length against your Polygon address before you paste.
On the starting side, Polygon fees are paid in POL. On the Sui side, SUI is the token that pays fees, so a new wallet holding only the bridged token cannot move it onward until it has some SUI. Sui reaches finality within seconds, which means the wait on this route comes from the Polygon side and the bridge, not from Sui itself.
Follow the sending transaction on PolygonScan and the arrival on a Sui explorer such as Suiscan. The most common mistake on this route is pasting a Polygon 0x address into the Sui field, since both begin the same way.
### Points That Save You a Retry
* Small transfers feel the fees, and a first transfer may leave you with tokens you cannot move on Sui until you add some SUI. That is the main downside of this route.
* Keep a little $POL beyond what you send, since [Polygon](https://polygon.technology/) takes its network fee from that balance.
* Plan to bridge Polygon to Sui only after a Sui wallet exists, and note which account you will use. One wallet can hold several accounts, each with a different address.
### Once the Funds Show Up on Sui
After a Polygon-to-Sui transfer, open your Sui wallet and look for the token in the assets list. A token you have not held before may need a refresh before it appears. If the balance is there but you cannot send it onward, check that the wallet also holds a little SUI for fees.
### Different Tools for the Same Crossing
* Kestrel Connect — Supports a wide list of Polygon tokens, but its Sui route offers fewer choices for the destination token.
* Larkspur Bridge — Offers a clean layout for first-time users, though transfers can take longer in busy periods.
### Quick Answers Before You Send
#### How to bridge Polygon to Sui with a hardware wallet
A hardware wallet can sign the Polygon side when it is linked through your browser wallet and the app your device uses for EVM networks is open. Confirm the details on the device screen. For a POL to Sui bridge, the Sui destination can be a separate wallet, so copy its address from there.
#### Setting up a Sui wallet first
Install a Sui wallet, create an account, and copy its address. The wallet is for Sui only, so your Polygon wallet stays exactly as it is. The Sui wallet can sit empty until the transfer arrives.
#### Polygon gas token for the swap
Polygon fees are paid in POL, in amounts that are small next to Ethereum's. If you are sending POL itself, leave part of it unsent so the fee can still be paid.
*Have your Sui address copied and ready? Then open* [*the bridge*](https://rezentix.com/) *and set up the swap.*
*Jamal Whitfield — Explains everyday crypto tools without jargon, one task at a time.*
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://traes.gitbook.io/docs/polygon-to-sui-bridge/polygon-to-sui-bridge-complete-step-by-step-guide.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
