Across Bridge
Networks
Live preview — open the official Across app from your own wallet.
Official app: app.across.toIntent-based transfersSupported networks include Ethereum, Base and Solana
What is Across Bridge?
Across is an intent-based cross-chain protocol for moving assets between supported networks through its transfer app and developer APIs. Its developer documentation explains integration paths for swaps, bridge actions and builders.
Across Bridge at a glance
CategoryCross-chain bridge
NetworkMulti-chain
TokenACX
Primary productAcross Bridge and Swap API
CustodyNon-custodial bridge protocol
Across bridge fees & speed
Across is built around fast cross-chain fills, with its docs describing roughly 2 second mainnet fills across major supported chains. The cost a user sees is route-specific: it can include origin-chain gas, destination execution assumptions, relayer economics, liquidity availability, and the quoted bridge or swap fee. Across does not have one universal fee that applies to every transfer. For users, the best answer is the live quote in the Across app or API because it reflects token, size, chain pair, and route conditions. Across also exposes quote and fee endpoints for integrators who need programmatic estimates before building a transaction.
Across supported chains and tokens
Across supports many chains through its bridge and Swap API, including Ethereum, Arbitrum, Base, Optimism, Polygon, BNB Smart Chain, Linea, Solana, Unichain, World Chain, Ink, Lisk, Mode, Zora, and other deployments shown in its contracts page. Support is not identical for every token or route, so users should verify both the origin chain and destination chain before sending. Stablecoins such as USDC are common Across routes, while other assets depend on chain liquidity and API support. The official chain and token checker tools are the most reliable way to confirm a specific route.
How to track an Across bridge transaction
Across deposits can be tracked by transaction hash, deposit ID, or depositor address through Across tracking tools and API endpoints. A normal route has several stages: the user sends the origin-chain transaction, a relayer fills the destination side, and settlement/refund accounting happens after the protocol verifies the transfer. If a transfer appears delayed, the useful information is the origin transaction hash, origin chain, destination chain, token, amount, and recipient. Across documentation includes tracking endpoints for a single deposit, deposit lifecycle status, and deposits for a given depositor, which is the search intent behind most 'Across bridge pending' queries.
Across bridge limits and large transfers
Across limits are route-dependent rather than a single fixed maximum. Transfer size depends on supported token liquidity, origin and destination chains, current relayer capacity, and parameters returned by the quote or limits endpoints. For large transfers, users should check the live Across quote first and avoid splitting blindly because route economics can change with amount. Integrators can query supported routes and limits before presenting a transaction. If a route is unavailable, it may mean that the chain pair, token, size, or current liquidity state is not supported at that moment.
How to bridge Across Bridge
- Open the appUse the primary action to visit the official Across interface and connect a wallet you control.
- Choose a routeSelect the token, origin network, destination network and amount supported by the app.
- Review the quoteCheck the destination amount, route details, fees and estimated timing before signing.
- Confirm and trackApprove token spending if prompted, sign the transaction and monitor transfer status in the app.
Ready to bridge?
Open the official Across app and verify the domain before you sign.
Across vs other bridges
| Dimension | Across | Alternative |
|---|---|---|
| Core model | Fast relayer-filled cross-chain intents | Liquidity pools, messaging, or canonical bridges |
| Typical user check | Live quote, route, and destination fill | Bridge fee, finality, and liquidity |
| Integrations | Swap API and embedded actions | Protocol-specific SDKs or bridge UI |
| Chains | Broad multi-chain support with active route checks | Varies by bridge |
| Best for | Fast route-dependent transfers | Token- or ecosystem-specific routes |
Across Bridge FAQ
How fast is Across bridge?
Across documentation describes mainnet fills around 2 seconds for supported routes, but the exact user experience depends on the origin transaction confirmation, token, chain pair, route, and relayer availability. The bridge can feel very fast once the origin transaction is accepted, but users should still wait for the Across app or tracker to show completion before assuming funds are final on the destination chain.
What fees does Across charge?
Across fees are quote-based. A transfer can reflect origin gas, destination execution, route liquidity, relayer economics, and bridge or swap parameters. There is no single fee percentage that accurately describes every Across transfer. Users should compare the output amount shown in the official app, while developers can use Across API endpoints to retrieve quotes, supported routes, and limits before asking a user to sign.
Which tokens can I bridge with Across?
Across supports specific tokens on specific chain routes, with stablecoins such as USDC commonly used across many routes. Support changes by chain, liquidity, and API configuration. The reliable way to answer this query is to check the official Across token checker, app quote, or Swap API for the exact origin chain, destination chain, input token, output token, and transfer amount.
What is the ACX token?
ACX is the token associated with Across Protocol. It is separate from the bridge asset being transferred. A user bridging USDC or ETH through Across does not need to treat ACX as the output token unless they are intentionally buying or interacting with ACX. For token price, contract, and market data, users should rely on established listings such as CoinGecko or CoinMarketCap.
Can Across bridge to Solana?
Across documentation lists Solana among deployed or supported chains, but route availability still depends on the token, origin chain, destination chain, and live API support. Users should not assume every EVM token can move to Solana through Across. Check the official app or API route response for the exact token and amount before sending a transaction.
What should I do if an Across bridge is pending?
First, confirm that the origin-chain transaction succeeded. Then use the Across status tracker with the transaction hash or deposit details. A pending status can relate to origin confirmation, relayer fill timing, route liquidity, or refund/settlement processing. Do not resend the same transaction unless the wallet clearly shows the original transaction failed. Keep the chain pair, token, amount, and recipient address available for support.