Bridge tokens across networks

Move between networks

A bridge moves supported value from a source network to a different destination network. Unify compares available independent and partner paths for the actual amount, asset and receiver. A route can include a source swap before delivery or a destination conversion when that specific executor supports it. Two tokens sharing a ticker on different chains do not establish a valid bridge. Check the exact destination contract and receiving network before authorizing any source transaction.

Open Convert ↗

How to bridge with Unify

1. Connect your wallet and select readable source holdings.
2. Choose a different destination network under Convert into.
3. Select the exact destination token and an optional receiving wallet.
4. Compare estimated delivery, the protected minimum and all disclosed costs.
5. Approve only the reviewed wallet requests. A destination swap also needs destination-network gas and wallet approval.
6. Keep the source transaction hash and follow History until destination evidence is available.

Successful approval does not submit a bridge, and a successful source transaction does not by itself prove destination delivery.

Compare available corridors

Base to Ethereum USDC and other supported corridors can have different delivery mechanisms and fixed costs. Unify USDC paths use verified Circle CCTP capabilities where the source, destination and forwarding requirements are supported. External routes can use other mechanisms and have different minimum sizes, fees or restrictions. Stock-token holdings may first need an eligible source swap; that does not imply the stock itself is bridgeable. Unsupported corridors stay unavailable rather than being presented as guaranteed delivery. Open the app for a current amount-specific comparison.

Standard, Fast and net received

A faster bridge mode can charge more than a standard option. Compare what reaches the destination after disclosed network and extra source costs, not just a route name or headline duration. Provider speed estimates do not certify future settlement times. Missing competitor coverage is not proof that the displayed candidate beats every route in the market. A protected token minimum is separate from its eventual dollar value. Read how included and separate fees are counted →

Why small amounts can be expensive

Destination execution, relaying and source transactions can create costs that do not shrink in proportion to the amount. These charges can dominate a sub-dollar transfer, especially when delivering to Ethereum. Compare a source-network swap or another supported destination if it meets your needs; neither is chosen without your review. Optional collection can reduce repeated bridge legs for eligible selections but introduces its own stages. No free bridge or universally lowest-price route is promised. Keep enough native gas for the required source actions.

Receiving wallets and separate stages

The connected wallet receives the output unless you select another supported receiving address. Review both the address and network carefully; cross-chain delivery cannot be assumed reversible. Some composed routes have separate source swaps and delivery stages, and multi-network portfolio operations are not one atomic transaction. A route refresh must preserve the reviewed receiver and protection. Supported wallets can batch eligible actions on a network, but a single click does not make bridge settlement instantaneous or remove external contract and delivery risks.

History, pending moves and recovery

History distinguishes approvals, source execution, provider observations and verified destination evidence where available. Keep the source hash and any order reference if delivery is pending. Recover moves checks existing records; it is not an instruction to send a duplicate source transfer. If a composed source swap completed but its bridge did not, inspect the checkpoint and current balance first. For a guided bridge-to-token route, USDC is delivered to your signing wallet before the final destination swap; Continue saved move never repeats a known source burn. Recovery depends on saved records and current provider and network responses. Submit a private support report → · Review safeguards → · Compare a same-network swap →