Across vs. Hyperlane: Which Bridge Should You Choose in 2026?

Across is the more straightforward pick when you want to move tokens between supported chains and review an estimated destination amount before signing. It also offers bridge-and-swap transfers, so you can send one token and receive another where the route supports it. Its quote is useful for comparing the amount leaving your wallet with the expected output, but it is not a promise that every route has the same cost or timing.

Hyperlane is broader in purpose: its Nexus interface provides a consumer-facing bridge, while the underlying protocol supports cross-chain messages and developer integrations. That makes it more relevant if you are building or using apps that need more than a token transfer. Its claimed reach is 150+ chains, but that does not mean every token and route is available. For a one-off transfer, check that the exact source, destination and asset are supported before choosing either service.

Across presents a live quote, but it does not publish a single fixed fee schedule. The total can vary with the route and market conditions; source-chain gas may also apply, and a bridge-and-swap route includes conversion pricing in the output. Review the destination amount and any separate wallet gas estimate before approving. If the quote changes or the output is worse than expected, pause and request a fresh quote.

Hyperlane does not publish fee amounts. You may need to account for source-chain gas and, depending on what you do next, destination-chain gas. A route may also have relayer or bridge charges, and a swap adds exchange pricing and slippage considerations. Do not assume a transfer is free or that one route costs the same as another. Compare the transaction preview and expected received amount before proceeding. On fee transparency alone, Across has an edge because it displays a quote, though neither supplies a universal price you can rely on for every transfer.

Across describes a model using bonded relayers, liquidity pools and an optimistic oracle. It lists two audits, but does not identify their names, scope, dates or findings, so the count alone cannot tell you what was reviewed. Its architecture does not remove smart-contract, oracle, liquidity or network risks, and a fast fill is not the same as final settlement.

Hyperlane is permissionless and lets developers configure validators, relayers and contract extensions. That flexibility means the security setup may differ by deployment and route. No audits are listed, and you should look for route-specific details before sending funds. Neither protocol should be treated as risk-free or as a custodial service with guaranteed recovery. Verify the destination network and token address, understand the transaction prompts, and consider a small test transfer before moving a significant amount. If you cannot establish the route’s security setup or the consequences of a failed transfer, wait rather than guessing.

Across’s flow is built around connecting a wallet, choosing source and destination networks, selecting tokens, and checking a quote before you sign. Some transfers may also ask you to approve a token allowance. Read each wallet prompt and avoid approving anything you do not understand. Across advertises fast fills, but timing can vary with liquidity, congestion and the route; do not treat a speed claim as a guarantee.

Hyperlane’s Nexus is also a bridge interface: connect a compatible wallet, choose a network pair and asset, then review and approve the transaction. Wallet compatibility can differ across the multiple virtual-machine environments Hyperlane supports, so do not assume the same wallet works on every route. You will generally need the source asset and native gas token to submit a transaction. If you want a clearer quote-first flow, start with Across. If your task involves a specific Hyperlane-connected app or message, use Nexus only after confirming route support and costs.