Polygon Bridge moves tokens across two chains, with a return cost

Polygon Bridge moves tokens from Ethereum to Polygon by locking them on one chain and making a corresponding token available on the other. The bridge contract records the deposit, and the destination chain credits the recipient with a mapped token. For someone ready to move an asset, Polygon Bridge is the bridge for transferring tokens between Ethereum and Polygon. Check that the token and destination address are the ones you intend to use before approving the transfer.

How does Polygon Bridge move tokens?

First, the wallet connects to Ethereum and approves the bridge contract to use the chosen token, if that token requires approval. The user then submits a deposit transaction. The contract takes custody of the Ethereum tokens and records where they should go on Polygon. Once that deposit is processed, the corresponding mapped token becomes available on Polygon. Think of the locked token as a coat checked at one station and a claim ticket issued at another; the contract and its records do the actual accounting.

The two balances are connected by the bridge’s rules, but they are not a single balance that travels between networks. The representation on Polygon is the one used for transfers and applications there. Keep the Ethereum transaction record until the destination balance appears, and confirm the token contract on Polygon before using it. A familiar token name alone does not prove that a token is the expected representation.

What happens when you bridge tokens back to Ethereum?

The return trip has its own steps. The holder starts a withdrawal on Polygon, where the bridge burns or marks the Polygon representation for exit. Polygon validators periodically submit checkpoints to Ethereum, committing to Polygon activity. After the withdrawal is included in a checkpoint, the holder uses the exit record to claim the corresponding tokens from the Ethereum bridge contract. The Polygon transaction starts the process; it does not complete the Ethereum claim.

That checkpoint stage makes the return slower than simply sending a token between two wallets on the same chain. It also means the user may need to come back and submit the Ethereum claim after waiting. Save the withdrawal transaction details and check the bridge’s status before assuming the funds have arrived. When using Polygon Bridge for the return leg, budget time for the checkpoint and a separate transaction on Ethereum.

How much should you budget for the return trip?

Budget for gas on each network where you will send a transaction. The deposit needs Ethereum gas. Spending or withdrawing on Polygon needs Polygon gas, paid in POL. Completing the exit needs Ethereum gas again. Token approval, when required, is another Ethereum transaction and another gas cost. Fees change with network demand, so estimate them when you are ready to act rather than treating the cost of the first leg as the total.

• Keep enough ETH for the deposit and a later Ethereum claim.
• Keep POL available for Polygon transfers and the withdrawal transaction.
• Allow for token approval if the wallet asks for it.
• Do not count the bridge amount itself as money reserved for gas.

For a one-way move, the immediate cost is mainly the source-chain transaction and any approval. For a round trip, the user pays to start on Polygon and to finish on Ethereum as well. That is the practical trade-off: the bridge makes assets available on another network, while each network’s contracts and gas rules still govern the separate steps.