Cost components
Expect source-chain gas, destination claim gas when required, token approval gas, and any route-specific fee shown before signing. Polygon's Portal guide explains where users choose routes and check transaction status.
Bridge to Polygon, from your wallet
Polygon Bridge — Move supported tokens between Ethereum and Polygon networks while reviewing route, gas, claim, and security assumptions.
Live preview — open Polygon Bridge to bridge on Polygon.
PolygonNon-custodial
What is Polygon Bridge?
Polygon bridge usually refers to using Polygon Portal to move supported assets between Ethereum and Polygon networks. The official Polygon Portal docs describe a trustless two-way bridge for Polygon PoS and Ethereum, where deposits lock tokens on Ethereum and mint pegged tokens on Polygon, while withdrawals burn on Polygon and unlock on Ethereum. Users still need to review network gas, route support, token contracts, and claim steps.
How Polygon Bridge works
Polygon Portal presents the route, token, amount, wallet prompt, and transaction status. The exact settlement path depends on the source network, destination network, and token.
- Pick the official entry pointStart from Polygon Portal or Polygon docs, then confirm the URL before connecting a wallet.
- Choose route and tokenSelect source chain, destination chain, token, amount, and receiving wallet if the interface supports a separate recipient.
- Review cost componentsCheck network gas, any route fee, token approval, estimated arrival, and whether a later claim transaction is required.
- Track and claimAfter signing, monitor the transaction page and complete any required claim on the destination side.
Fees and security
There is no single Polygon bridge fee. Cost and risk change with gas markets, token approvals, the selected bridge path, and the trust model.
Trust model
Native bridge flows use smart contracts and chain verification rather than an exchange account, but that does not remove smart-contract or user-error risk. Ethereum.org's bridge overview explains common trusted and trustless bridge tradeoffs.
Token verification
Use the exact token shown in the portal, verify contract addresses for custom tokens, and avoid links sent through ads or direct messages. Polygon docs note that users can add custom tokens when a token is not listed.
Route notes before bridging
Polygon Portal can include native and third-party routes in the same interface, so read the confirmation screen instead of assuming every path has the same bridge design.
PoS and Ethereum
For Polygon PoS to Ethereum, expect a burn-and-unlock withdrawal flow and possible claim steps. The official PoS bridge overview is the best starting point.
zkEVM status
Polygon's own materials mark zkEVM as sunsetting, so check the current official status before using routes that involve it. Start with the Polygon zkEVM page and avoid stale third-party instructions.
Third-party options
If the portal offers a third-party bridge, its liquidity, fee logic, and security assumptions may differ from the native bridge. Treat the provider's official docs and Ethereum.org's bridge risk notes as required reading.
Common Polygon Bridge Routes
Start by matching the source chain, destination chain, and claim requirements before signing.
Ethereum to Polygon PoS
Deposit into Polygon PoS Native
Use this when funds are on Ethereum and the destination app or wallet expects Polygon PoS assets. Deposits lock supported tokens on Ethereum and mint pegged assets on Polygon PoS.
Docs ↗Polygon PoS to Ethereum
Withdraw back to Ethereum Claim
Use this when you need the Ethereum version of a token again. Review burn, checkpoint, exit, gas, and claim steps before starting.
Docs ↗Polygon Portal
Official bridge interface Official
Use the portal to select chains, tokens, amount, and status tracking from a single Polygon interface. Confirm the route details because native and third-party options can appear together.
Open ↗Custom Token Route
When a token is not listed Verify
Use only after verifying the token contract on the correct network. A listed balance is not a substitute for checking the contract and destination support.
Docs ↗Assets Users Often Check
Availability can vary by route, so treat these as assets to verify in the portal before bridging.
Ether
Ethereum network asset Gas
Bridge only after confirming whether the destination receives wrapped ETH or a chain-specific representation. Keep enough ETH for Ethereum gas.
Docs ↗
POL
Polygon ecosystem token Native
Check whether your route, wallet, and app expect POL on Polygon PoS or a different network representation. Network selection matters.
Open ↗
USDC
Circle dollar token Stable
Verify the exact USDC version and contract before moving funds. Stablecoin names can look similar across networks.
Docs ↗
USDT
Tether dollar token Stable
Confirm the token contract and destination support before bridging. Do not assume an exchange deposit address supports every network.
Docs ↗
Wrapped Bitcoin
Tokenized BTC exposure Wrapped
Use extra care with wrapped assets because issuer, chain, and contract details define what you actually receive.
Docs ↗Native bridge vs third-party route
Polygon Portal may show native and third-party paths. Ethereum.org's bridge guide explains why trust model and custody assumptions matter.
| Route type | What to check | Best fit |
|---|---|---|
| Native Polygon bridge | Claim steps, gas on both sides, supported token mapping | Users who prefer Polygon's official bridge contracts |
| Third-party bridge | Provider docs, liquidity, fee logic, custody or verifier assumptions | Users comparing alternative routes inside or outside the portal |
| Exchange transfer | Supported network, deposit address, withdrawal status, account custody | Users who already plan to use a centralized account |
Polygon Bridge FAQ
What is the official Polygon bridge?
Polygon Portal is the official interface for bridging and managing assets across Polygon networks. The Polygon Portal docs describe wallet connection, bridging, claims, transaction status, and custom token handling. Always type or bookmark the official URL instead of following ads or direct-message links.
How does the Polygon PoS bridge move tokens?
For the PoS bridge, deposits lock supported tokens on Ethereum and mint pegged tokens on Polygon; withdrawals burn pegged tokens on Polygon and unlock the originals on Ethereum. Polygon's official PoS bridge overview describes that lock/mint and burn/unlock model.
What fees apply when using Polygon Bridge?
Fees are components, not a fixed universal number: source-chain gas, destination claim gas when required, token approval gas, and any route-specific fee shown by the interface. Polygon's Portal guide shows that users review the route and transaction status in the bridge flow.
Is Polygon Bridge safe?
No bridge removes risk. Native bridge flows reduce some third-party custody concerns, but users still face smart-contract risk, network risk, phishing, wrong-network deposits, and token-contract mistakes. Ethereum.org's bridge risk section gives a plain overview of common bridge risks.
Can I bridge directly between Polygon PoS and Polygon zkEVM?
Do not assume direct native routing. Polygon's Portal docs state that the native bridge does not support direct bridging between Polygon PoS and zkEVM chains. Also check Polygon's current zkEVM status before using any zkEVM-related route.
What should I check before signing a bridge transaction?
Confirm the official URL, source network, destination network, token contract, recipient, approvals, gas asset, estimated arrival, and claim requirement. The Polygon Portal instructions show the normal flow for choosing a route and tracking a bridge transaction after signing.