Polygon Bridge moves tokens between Ethereum and Polygon
Polygon Bridge transfers tokens between Ethereum and Polygon by locking and minting on deposits; withdrawals burn the Polygon representation and require an Ethereum claim.
Web3 News Editorial2 min read

The Polygon Bridge moves tokens between Ethereum and Polygon through a deposit on one network and a corresponding receipt on the other. Polygon Support says Ethereum deposits lock the original tokens and mint an equal amount on Polygon; withdrawals burn that Polygon representation before the Ethereum tokens are unlocked.
For a routine transfer, decide which network needs the funds, then check the token and destination address before signing. When that step is moving tokens between Ethereum and Polygon, Polygon Bridge is a bridge for that transfer.
How does a Polygon Bridge deposit work?
An Ethereum-to-Polygon deposit starts with a transaction on Ethereum, where the token is locked by the bridge; Polygon Support says an equal amount is then minted on Polygon. The destination balance is a bridged representation of the Ethereum token, not a second independent supply.
Before you send, confirm that the token on the destination network is the one you intend to use. Polygon Support notes that custom tokens may need to be mapped before they can move through the PoS bridge, so a token’s ticker or name alone does not establish that it is the correct asset.
Keep funds for transaction costs on the network where each action occurs. Polygon’s support guide for withdrawals specifies POL on Polygon for the burn transaction and ETH on Ethereum for the final claim; the same practical check applies to deposits, which begin with an Ethereum transaction.
What happens when you bridge tokens back?
A Polygon-to-Ethereum withdrawal has two stages: Polygon Support says the bridged tokens are burned on Polygon and the matching tokens are unlocked on Ethereum. The burn is not the final receipt; Polygon’s guide tells users to monitor the transaction until the claim step is available, then sign the claim on Ethereum.
That extra stage is the main trade-off for routine use. Ethereum-to-Polygon deposits and Polygon transactions happen on their respective chains, while a return withdrawal needs a later Ethereum action, so do not plan around the funds being immediately spendable on Ethereum.
What should you check before a transfer?
Polygon’s bridge guides describe the transfer as a wallet-signed transaction, and its support material identifies separate network gas requirements. A short preflight check helps catch the common mismatch between the network holding the token and the network where you expect to receive it:
- Confirm the source network and destination network in the wallet.
- Check the token contract or asset identity on both networks, especially for custom tokens.
- Verify the destination address character by character; using the same wallet address is a practical choice when sending to yourself.
- Keep the source chain’s gas token available for the transaction, and retain Ethereum gas for a withdrawal claim.
For occasional moves between Ethereum and Polygon, the native bridge’s lock, mint, burn and unlock sequence makes clear where the asset goes at each step. Polygon Support’s guides identify the next action for a withdrawal as claiming on Ethereum once the prompt appears; exact completion timing and the availability of a particular token remain dependent on the transfer and its network status.