A Polygon bridge is any protocol that moves tokens between Polygon PoS and another chain. The category covers four mechanism types: the native LxLy unified bridge (lock-and-mint to Ethereum), Circle CCTP (burn-and-mint for native USDC), Hyperlane warp routes (lock-and-mint or synthetic for ERC-20s), and intent or liquidity-pool aggregators that quote pre-priced fills.
​

Polygon PoS settles around 2-second blocks as an Ethereum sidechain with its own validator set, posting checkpoints to Ethereum. Bridges into Polygon either talk to the native bridge contract on Ethereum or wrap their own messaging and liquidity around it. The route a user picks comes down to which token they hold, how fast they need finality, and how the fees decompose. Polygon's docs are the canonical reference for native mechanics. The routes below are described by mechanism, not ranked as "best in absolute terms." Fit depends on the use case.
​

Seven routes cover most real Polygon bridging volume in 2026: the native Polygon Portal (LxLy), Circle CCTP V2, Hyperlane warp routes, LayerZero plus Stargate, Across, Squid, and LI.FI. Each uses a different routing mechanism, settles in a different time window, and prices fees differently. The table below summarizes the trade-offs, and the sections that follow explain each mechanism.
​

Aggregators and intent bridges often produce the lowest quoted fees on smaller transfers, while CCTP and the native bridge tend to win at large size where slippage and pool depth matter more than messaging overhead. Bridge fee mechanics explains how to read these costs end to end.
​

The Polygon Portal is the official lock-and-mint bridge between Ethereum and Polygon PoS. Tokens lock in the Polygon bridge contract on Ethereum and equivalent tokens mint on Polygon. Deposits typically confirm in about 15 to 30 minutes. PoS withdrawals require a checkpoint, often roughly 45 minutes to 3 hours. Plasma exits for POL can take up to 7 days.
​

The contract has been upgraded into the Unified Bridge, a single shared LxLy instance that AggLayer-connected chains opt into. It maintains a shared Global Exit Tree across Polygon PoS, Polygon zkEVM, and other CDK chains. Per the AggLayer Unified Bridge contract on Etherscan, the bridge held over $149M across 8 chains and processed roughly 302,000 transactions as of April 2026.
​

The native route adds no protocol fee. Users pay Ethereum gas on deposit and Polygon gas on the destination side. The trade-off is speed: PoS finality is fast on the way in, but exits remain checkpoint-bound, and Plasma exits sit behind the challenge window. Polygon's support docs cover deposit and exit steps. For patient users holding ETH or arbitrary ERC-20s, the native route minimizes protocol surface area: no third-party messaging layer, no pool, just the canonical contract.
​

CCTP is Circle's burn-and-mint protocol for native USDC. The user burns USDC on the source chain; Circle's attestation service signs the message; the user (or a relayer) mints native USDC on the destination. There is no wrapped token and no liquidity pool. CCTP V2 added Fast Transfer with finality typically in seconds to a few minutes on supported chains.
​

Native USDC launched on Polygon PoS in October 2023, with CCTP support following. Circle's launch note describes the rollout. CCTP V2 is live across more than a dozen chains including Polygon PoS, with V1 entering deprecation in 2026. CCTP avoids the wrapped-token problem that plagued earlier Polygon USDC bridges, where bridged USDC.e and native USDC ran as two separate balances.
​

Fee shape is gas-dominated for the standard path and adds a small per-transfer fee on Fast Transfer. Aggregators like LI.FI can route through CCTP and present a single quote. Circle CCTP V2 covers the full mechanism and supported chains. For USDC users, this is usually the lowest-friction route into and out of Polygon. The caveat: CCTP only moves USDC, not arbitrary tokens.
​

Hyperlane warp routes are token bridges built on Hyperlane's permissionless messaging layer. The pattern: an ERC-20 locks as collateral on the origin and a synthetic HypERC-20 mints on the destination, or paired collateral contracts rebalance the same token across chains. Polygon PoS is a supported Hyperlane chain, and warp routes can deploy for any ERC-20.
​

The mechanism shines for tokens that lack a native canonical bridge: long-tail ERC-20s, project tokens, stablecoin variants, or LSTs. Latency is typically sub-minute to a few minutes, set by the interchain security module configured per route. Fees decompose into source gas, destination gas, and an interchain message fee. Hyperlane's docs enumerate the warp route types (collateral, synthetic, multi-collateral).
​

Where CCTP only handles USDC, Hyperlane is the practical answer for the wider universe of ERC-20s that want a fast cross-chain footprint without bootstrapping a liquidity pool. Polygon's docs include a dedicated Hyperlane route reference covering the lock-and-mint pattern for vbToken bridging.
​

LayerZero is a generic messaging protocol; Stargate is the unified-liquidity bridge built on LayerZero that supports USDC, USDT, DAI, and ETH on Polygon. Stargate uses a delta-rebalanced pool model: the pool on each chain holds native asset, and the delta algorithm guarantees finality without wrapping. Output on Polygon is the native version of the asset, not a synthetic.
​

USDT0, the LayerZero OFT version of USDT, gives USDT a single omnichain balance across Polygon, Unichain, Arbitrum, Plasma, HyperEVM, and other LayerZero-connected chains. Bridging USDT0 settles in seconds to minutes and avoids the network-selection problem of legacy USDT transfers between BEP-20, ERC-20, and TRC-20 footprints. For Polygon, USDT0 is one path; Stargate's classic USDT pool is another.
​

Fees on Stargate include a small protocol fee, a LayerZero message fee paid in source-chain gas, and destination gas. Stargate's pool-depth mechanics mean fees can spike when a pool is imbalanced relative to demand, so quotes shift over short windows. L2Beat's Stargate v2 page tracks the contract set and risk profile. LayerZero-based routes are typically faster than the native bridge and cheaper than the pure-aggregator path on common stablecoin pairs.
​

Intent and aggregator bridges route to Polygon without owning the underlying transport. Across uses an intent solver model: the user deposits on the source, a relayer pre-funds them on Polygon in seconds, and the relayer settles back through UMA's optimistic oracle. Squid and LI.FI are aggregators that pick among CCTP, Hyperlane, Stargate, Across, and DEXs.
​

Across covers 15+ chains including Polygon, and intent-based bridges typically settle most Polygon transfers in well under a minute on liquid routes. The fee model is a single upfront quote covering the relayer's risk premium, capital cost, and destination gas. Across's published median bridge fee on common stablecoin transfers has often hovered in the very low cents range on smaller sizes; quotes for large transfers scale with relayer liquidity.
​

Squid routes across the 100+ chains it supports including Cosmos, Solana, and XRPL alongside EVM, composing Axelar transport with DEX swaps. LI.FI supports 60+ EVM chains plus Solana and selects among multiple bridges per route. Coverage of Squid and Jumper sits in a separate piece.
​

The trade-off across this category is execution model versus surface area. Across offers tight quotes on heavily-trafficked routes; Squid reaches chains the others do not touch; LI.FI offers neutrality across many underlying bridges. Eco Routes is an intent-based router that aggregates many of these rails (CCTP, Hyperlane, LayerZero, Stargate) behind a single solver-competitive quote, with Polygon PoS as a supported destination.
​

The right route depends on token, urgency, and size. Native USDC users usually prefer CCTP for low fees and native output. Patient ETH or ERC-20 holders prefer the native Polygon Portal for zero protocol fee. Time-sensitive transfers often quote cheapest on Across or LI.FI. Large transfers favor CCTP or the native bridge over pool-based routes.
​

Some heuristics that follow from the mechanism descriptions above:
​

None of these are absolute rankings. A bridge that is cheapest today can be the most expensive next week if a pool rebalances or a relayer goes offline. Fastest bridge mechanics and Best crypto bridges 2026 cover the broader fee and speed landscape.
​

Sources and methodology. Mechanism descriptions verified against Polygon, Circle, Hyperlane, LayerZero, Across, Squid, and LI.FI documentation as of May 2026. AggLayer Unified Bridge balance and transaction counts pulled from Etherscan in April 2026. Fee and latency ranges are typical windows, not guarantees, and shift with liquidity and gas. Figures refresh quarterly.
​