Arbitrum bridge fees, wait times, and transfer options

Updated on 10 September, 2026

Arbitrum bridge connects Ethereum and Arbitrum through smart contracts that handle deposits and withdrawals. Moving ETH to Arbitrum One can fund transaction fees there, while supported token deposits use token gateways. The direction matters: deposits and canonical withdrawals follow different settlement processes. Total cost includes the transactions that the route requires, and canonical withdrawals need a later claim. Choose a route by its destination asset, available balance, confirmation requirements, and any deadline for using the funds.

Deposits and recoverable execution failures

A canonical deposit submits a transfer on the parent chain and produces a corresponding operation on the child chain. Ethereum is the parent of Arbitrum One. For token gateway deposits, a retryable ticket carries the instruction that completes the destination operation. Its creation and execution are separate events, so successful submission can precede delivery.

If automatic execution fails, an existing, unexpired ticket can allow another execution attempt. Different gas conditions can resolve a gas-related failure, but extra gas cannot fix every contract rejection. The ticket status and execution error distinguish a recoverable attempt from a request that needs further investigation. Simple native ETH deposits use a separate mechanism; a missing balance alone does not establish a retryable failure.

How long does a withdrawal take to become spendable?

A canonical withdrawal from Arbitrum One or Nova to Ethereum typically takes about a week to become claimable. The funds become spendable after the containing assertion receives confirmation and someone successfully executes the claim on Ethereum.

An assertion records a claim about the child chain's state. The withdrawal must enter an assertion and pass the applicable dispute process before the parent chain accepts its message. Batch posting, assertion timing, and any dispute affect that wait. A successful source transaction therefore starts the withdrawal without making the destination funds immediately available.

The bridge's withdrawal status and countdown reflect the relevant request. A countdown reaching its endpoint still leaves the claim transaction to complete. Paying more gas cannot shorten the protocol's dispute requirement. When funds must arrive before a firm deadline, an unconfirmed canonical withdrawal cannot provide that certainty.

The transactions behind the total fee

Bridge costs follow the operations that a transfer requires, rather than a universal percentage of the amount. A token approval, deposit, recovery attempt, and withdrawal claim can each consume gas when applicable. Changing the transfer amount alone does not reveal the final cost.

Approval and deposit costs

An ERC-20 deposit needs sufficient allowance for the appropriate spending contract. If the existing allowance covers the deposit, another approval may be unnecessary. Otherwise, approval adds a source-chain transaction before the deposit. A retryable-based deposit also needs funding for message submission and destination execution. The wallet's estimate belongs to that particular request and network conditions. The amount that enters the bridge is separate from the balance needed to pay these transaction costs.

Withdrawal and claim costs

A canonical withdrawal incurs a source-chain transaction cost and later requires gas for parent-chain execution. Arbitrum transaction fees account for execution resources and applicable parent-chain data costs. These inputs can change independently of the transferred token's value. A low initial withdrawal estimate does not include a promise about the later Ethereum claim cost. Compare estimates for the complete route, retaining enough gas currency wherever a further transaction remains necessary.

Transfer options and the balances they require

The available approach depends on where the assets already sit and what the destination accepts. These options describe different transfer models, not a promise that every interface supports every asset. An exchange withdrawal also depends on that exchange's enabled network and withdrawal conditions.

Direct exchange withdrawals can avoid a separate wallet-to-bridge deposit when the exchange already holds the funds. Their availability and processing rules belong to the exchange.

Native ETH and token gateway deposits

Native ETH and ERC-20 tokens use different deposit mechanics. That distinction affects allowances, destination assets, and the records that identify delivery.

Native balance credit

A simple ETH deposit sends ETH into the parent-chain bridge contract and credits the destination through a native deposit message. It does not need an ERC-20 allowance. Recipient handling can differ for contract callers, so ordinary wallet address behavior should not be assumed for every account type.

Paired token contracts

A standard ERC-20 gateway deposit escrows tokens on the parent chain and mints the corresponding amount on the child chain. Routers select the gateway associated with the token. Custom gateways accommodate token behavior that the standard mechanism cannot handle. The destination contract identifies the asset; a matching ticker alone does not establish compatibility with an application or exchange.

Which records establish that a transfer finished?

A completed transfer needs the destination operation's successful record, linked to the source request and intended recipient.

Open full-size image

For a gateway deposit, ticket creation and successful redemption have distinct records. The source transaction hash helps trace that relationship, but it is not the destination execution hash. For withdrawals, confirmation makes the message executable; the later execution record establishes the claim. A wallet display can lag behind these records. Conversely, a source receipt alone cannot establish that the destination received the asset. Preserve the source hash and corresponding destination record when reconciling balances.

Liquidity bridges when the deadline changes the choice

A liquidity bridge can supply destination funds without making the recipient wait for the canonical withdrawal to settle. The provider funds that delivery through its own mechanism.

Open full-size image

Availability depends on the supported route, asset, transfer size, and destination liquidity. Provider fees and additional contract or provider assumptions accompany the service. The quoted asset and recipient amount matter because the destination application must accept what arrives. A faster estimate does not establish unlimited liquidity or guarantee a deadline.

Compare the complete quote before committing funds. Once a canonical withdrawal has started, a separate liquidity transfer does not cancel it or shorten its confirmation process.

Arbitrum One, Nova, and intermediate chains

Arbitrum One and Arbitrum Nova maintain separate balances even when a wallet uses the same address. Switching the wallet's network changes the ledger that it displays; it does not move funds. A canonical transfer between these networks can pass through Ethereum as a withdrawal followed by a deposit, where the asset supports both legs. That route inherits the withdrawal's confirmation requirement and the costs of another deposit. A direct provider route follows its own availability and settlement conditions.

Destination gas and a usable balance

Receiving a token and having the means to use it are separate requirements. Arbitrum One and Nova use ETH for gas. A token balance therefore does not itself fund a subsequent ordinary wallet transaction. ETH held on Ethereum also does not pay a transaction fee on Arbitrum One. The destination must contain the asset that the intended application accepts, plus the necessary gas funding. If those requirements differ from the quoted output, the transfer alone will not complete the intended task.