USDC moves across more than 20 chains in 2026, and the bridge you choose decides whether the recipient holds native USDC (mintable 1:1 with Circle) or a wrapped IOU like USDC.e that has to be swapped before it spends like the real thing. Circle's CCTP burns USDC on the source chain and mints fresh on the destination — every other route relies on lock-and-mint or liquidity pools, with different fee, slippage, and finality trade-offs.
​

This guide compares the eight bridges that actually move material USDC volume according to the DeFiLlama Bridges dashboard, with $1,000-transfer economics for each, and points you to the right pick by use case.
​

A USDC bridge is a protocol that moves USDC value from one blockchain to another. The two route types are burn-mint (source USDC is destroyed and Circle issues new native USDC on the destination) and lock-mint or liquidity pool (source USDC is held by a contract or LP, and a wrapped representation is issued or swapped on the destination). Native arrivals are fungible with on-ramp and off-ramp USDC; wrapped arrivals usually trade at a small discount and need a swap to become native.
​

Only Circle's Cross-Chain Transfer Protocol (CCTP) burns and mints natively. Every other bridge in this comparison either locks USDC in an escrow contract on Ethereum and mints a wrapped copy elsewhere (Wormhole, Stargate's pool model), or uses a relayer-funded liquidity network that hands the recipient pre-existing native USDC drawn from inventory (Across, LI.FI when CCTP is the selected route).
​

The table below compares the eight USDC-capable bridges by chains supported, fee on a $1,000 transfer, typical time-to-finality, and whether the recipient holds native USDC or a wrapped variant. Fees are quoted from each bridge's public docs or a sample quote pulled in May 2026; slippage applies only to AMM-style routes.

Coinbase Bridge ($5.8B TVL) and WBTC ($9.1B TVL) appear higher in the DeFiLlama bridge ranking, but the first is L2-only and the second is for BTC; neither is a general-purpose USDC route. The eight above are the bridges any USDC-mover should know.
​

CCTP is Circle's official cross-chain protocol that burns USDC on the source chain and mints fresh native USDC on the destination, with no wrapping or liquidity pool in between. CCTP V2 supports 11 chains as of May 2026 and adds a Fast Transfer lane that finalizes in roughly 20 seconds, a Hooks system for atomic post-transfer actions, and a $0 protocol fee — the user pays only source and destination gas.
​

Supported chains per Circle's docs include Ethereum, Arbitrum, Base, OP Mainnet, Polygon PoS, Avalanche, Solana, Sui, Linea, Sonic, and Codex. Because the destination USDC is freshly minted by Circle, it is fully redeemable through Circle Mint and indistinguishable from any other native USDC — no swap required before depositing to a CEX or paying out through a fiat off-ramp.
​

The trade-off is chain coverage: 11 chains is a fraction of what aggregators like LI.FI or Squid expose. If you need to land on a chain CCTP doesn't support, you need a wrapped or aggregator route. CCTP V2 also requires the destination chain to have deployed the V2 message transmitter; some chains still run V1 with a 13–19 minute attestation window.
​

Across is an intent-based bridge where the user signs an intent ("send 1,000 USDC from Arbitrum to Base") and a competitive market of relayers fronts the destination USDC from inventory, then claims a refund from the source after a UMA optimistic verification window. The user receives native USDC in 1–4 minutes; the relayer takes the finality risk.
​

Per the Across fee docs, the all-in fee on a $1,000 USDC transfer between L2s is typically $1–$2 (0.10–0.20%), which makes Across the cheapest production route for active L2-to-L2 USDC flow according to the DeFiLlama bridges dashboard. The intent model also avoids AMM slippage entirely — relayers compete on a fixed quote.
​

The catch: Across is EVM-focused and ships native USDC only on chains where a deep relayer market exists. Niche destinations may quote a higher fee or fall back to a longer settlement path. For Solana, Sui, or Aptos, route through CCTP or LI.FI instead.
​

The remaining five bridges all introduce some form of wrapping or pool exposure. Stargate uses LayerZero messaging plus a unified liquidity pool; Wormhole locks-and-mints via its guardian network and can relay CCTP for native USDC; Hop runs an AMM with bonders advancing funds; Synapse moves through nUSD with a stable-swap on arrival; Squid aggregates over Axelar's General Message Passing layer and defaults to axlUSDC. Each has a use case where it wins on coverage or composability, but none ships native USDC across the board.
​

Stargate covers 15+ chains via the LayerZero V2 stack and is the deepest non-CCTP USDC liquidity network — useful when the destination chain isn't on CCTP's list. Wormhole's strength is non-EVM coverage (Solana, Sui, Aptos, Sei) and its CCTP-relay mode that produces native USDC on supported pairs. Hop only covers Ethereum mainnet plus six L2s but is battle-tested for L2 retail flow. Synapse's stable-swap design hides slippage on small transfers. Squid's killer feature is one-click swap-and-bridge that lets a user pay in any token and land in USDC on a target chain.
​

LI.FI is a routing aggregator that scans CCTP, Across, Stargate, Hop, Wormhole, Synapse, Squid, and a dozen DEXes, then quotes the best end-to-end path on price, time, and reliability. For most users the pragmatic answer is to start with LI.FI: the aggregator will return the same CCTP route Circle offers when CCTP is fastest or cheapest, and substitute Across, Stargate, or a multi-hop swap when not.
​

According to the LI.FI integration docs, the aggregator supports 20+ chains and 15+ underlying bridges. Eco's Routes API uses a similar abstraction internally, exposing 15 chains through a single intent — though Eco is purpose-built for stablecoin payments rather than for arbitrary bridge routing.
​

The right bridge depends on what you optimize for: native USDC outcome, smallest fee, broadest chain coverage, or one-click swap-and-bridge. Use CCTP when the destination chain supports it and you need native USDC for a CEX deposit or fiat off-ramp. Use Across for the cheapest L2-to-L2 EVM transfer. Use LI.FI when you don't know which route is best and want the aggregator to pick.
​

By use case:

Eco is a stablecoin payments platform that abstracts cross-chain USDC movement behind an intent. A developer or end user expresses "I want USDC on chain X by time Y," and Eco's solver network selects the underlying transport — CCTP, a partner bridge, or its own liquidity — to deliver native USDC across 15 supported chains. Eco does not replace CCTP; it makes the choice of transport invisible to the application layer.
​

The practical difference for a builder: instead of integrating CCTP, Across, Stargate, and a fallback aggregator to cover the long tail of chains and edge cases, an Eco Routes integration handles routing, gas abstraction, and settlement in a single intent. For a user wiring USDC between two of the eight bridges in this comparison, the head-to-head choice still matters; for a payments product moving USDC behind the scenes, the abstraction layer matters more.
​

Bridge selection: the eight bridges are the USDC-capable routes with the deepest documentation and material volume on the DeFiLlama Bridges dashboard, May 2026. Fee and time-to-finality figures come from each bridge's public docs (linked inline) and sample quotes pulled in May 2026; live numbers move with gas and liquidity. USDC native vs wrapped outcomes are confirmed against Circle's CCTP supported chains list and each bridge's documentation. Stablecoin market figures (USDC supply $78.1B as of Q2 2026) are from DeFiLlama's stablecoins endpoint.
​

Primary sources: