What Is Polygon Bridge and How Does It Work for PoS Transfers?

Use Polygon Bridge when you need a supported token on Polygon PoS for an app or payment, or need to return its bridged form to Ethereum. It moves value between the two networks through bridge contracts; it does not move the original token contract from one chain to another. The useful question before transferring is which token contract you need at the destination.

What Does the Bridge Move?

The Polygon PoS bridge connects Ethereum mainnet, chain ID 1, with Polygon PoS, chain ID 137, for assets that have a supported route. For a typical ERC-20 deposit, the Ethereum token is held in a bridge contract and a corresponding token becomes available on Polygon. Withdrawing reverses that relationship, so the amount is represented on one side or the other.

“Corresponding” does not mean every token with the same ticker is interchangeable. A mapped bridged token can have a different contract, issuer and set of accepted uses from a token issued natively on Polygon. Check the destination app’s required network and contract address before deciding what to bridge.

How Does a Transfer Actually Settle?

An Ethereum-to-Polygon deposit starts with a transaction on Ethereum. An ERC-20 may first require an allowance transaction, then the deposit locks the tokens; Polygon’s state-sync process observes that event and credits the mapped representation on Polygon. The Polygon Bridge interface coordinates the request, but a confirmed Ethereum transaction alone does not mean the Polygon balance has arrived.

A withdrawal starts on Polygon with a burn of the bridged token. Polygon validators include the burn’s block in a checkpoint submitted to Ethereum; after that, an exit transaction supplies proof of the burn to release the escrowed asset. This is why a withdrawal can show as complete on Polygon while the token is still absent from the Ethereum wallet: the Ethereum claim remains to be made.

For example, depositing 1,000 units of a mapped ERC-20 gives you roughly 1,000 units of its Polygon representation, subject to the token’s transfer rules. It does not promise the same market price or cover gas. On the way back, the burn and the Ethereum exit are separate transactions, and the withdrawal cannot be cancelled after the burn.

What Time and Gas Should You Budget?

Deposits commonly take minutes after Ethereum confirmation, while PoS withdrawals can take tens of minutes to several hours because they wait for a checkpoint and an Ethereum exit. Polygon checkpoints are generally produced around every 30 minutes, but congestion or a delayed relay can extend the wait. Treat an interface estimate as a planning figure, especially when you need the funds by a deadline.

You pay gas on the chain where you submit each transaction: ETH for Ethereum approval, deposit or exit transactions, and POL for Polygon transactions. An illustrative Ethereum transaction using 120,000 gas at 20 gwei costs 0.0024 ETH; an ERC-20 approval, if needed, is additional. The actual gas used and gas price depend on the token, contract call and network conditions.

The cost comparison changes with transfer size. Two Ethereum transactions can be a meaningful fraction of a small withdrawal, even when Polygon gas is low. Compare the full quoted cost and expected arrival time with a liquidity bridge or exchange route, including any spread, transfer fee and token conversion.

Which Route Fits the Token You Need?

Choose the route by the destination token contract, then by speed and total cost. If the receiving app expects an Ethereum-backed representation on Polygon, a bridge from Ethereum to Polygon preserves that route back to the escrowed asset. For that deposit or a return withdrawal, use the Polygon Bridge to move supported tokens between Ethereum and Polygon. A liquidity bridge may deliver sooner, but its output and price depend on available liquidity.

USDC is the mistake to catch before signing. Bridging Ethereum USDC through the PoS route can produce USDC.e on Polygon, while Circle also issues native USDC there; the two have different contract addresses. If the recipient requires native USDC, choose a route that delivers native USDC, such as an applicable CCTP route, or account for a separate swap. A matching ticker in a wallet is insufficient evidence.

How Do You Complete and Check the Transfer?

Set the source and destination networks, select the exact supported asset and amount, and confirm the destination wallet can control the receiving address. Keep ETH on Ethereum for any required approval, deposit or exit, and POL on Polygon for a withdrawal and later use. Review the token contract and the wallet’s transaction details before signing; sending tokens directly to a bridge contract address is not a substitute for initiating a deposit.

After signing, save the source transaction hash and check its status on the source chain. For a deposit, then check the mapped token balance on Polygon; for a withdrawal, wait for checkpoint eligibility and complete the Ethereum exit before checking the Ethereum balance. If the interface lags, those chain records distinguish a pending relay or claim from a failed source transaction.