Arbitrum Gas Fees: How Nitro Calculates Them
How Arbitrum gas fees work: Nitro's fee formula, estimating with NodeInterface, what makes fees spike and how to quote them safely in your app.
Reviewed by Maurice Sobiera

An Arbitrum gas fee is the amount of ETH you pay for a transaction on Arbitrum. It combines the gas for running the transaction and the cost of posting its data to Ethereum. Nitro, Arbitrum’s node software, folds both into one gas price. You can read the current price with the RPC call eth_gasPrice.
TL;DR:
- The total fee combines L2 execution and the L1 posting cost into one number,
P * (L2G + (L1P * L1S) / P).- Use
NodeInterface.gasEstimateComponents()to estimate a fee before sending. Arbitrum’s documentation says the result is approximate.- Fee spikes usually come from the Ethereum base fee, from poorly compressible calldata or from changes to the chain’s configuration.
- Add a safety margin when you quote a fee to a user. We suggest 10 to 15 percent, which is our rule of thumb and not an Arbitrum recommendation.
- Chaingateway’s Arbitrum endpoints make the gas fields optional, so you do not have to compute them yourself for ERC-20 transfers.
Table of Contents
- Where do I find the current Arbitrum gas price?
- How does Arbitrum calculate fees?
- How do I estimate gas before sending an Arbitrum transaction?
- What causes Arbitrum gas fees to spike?
- What does an Arbitrum transaction cost?
- How can I lower Arbitrum fees?
- How do I send Arbitrum transfers through an API?
- Sources
- FAQ
Where do I find the current Arbitrum gas price?
Call eth_gasPrice on an Arbitrum RPC endpoint. It returns the network’s current suggested price. You can also read it from a block explorer such as Arbiscan, or from a Chaingateway call (see below). Each source samples at a slightly different moment, so the numbers can differ by a small amount.
After a transaction is mined, the effectiveGasPrice field of its receipt shows what you actually paid. It can differ from the earlier quote, because the price can move between quote and inclusion.
Gas trackers often show speed tiers such as Standard, Fast and Rapid. These come from Ethereum mainnet, where users bid against each other with priority fees. Arbitrum’s default ordering policy is first come, first served. According to the Arbitrum gas and fees documentation, arrival time sets the order, and the sender pays the base fee. Tips are only collected if the chain owner enables them. On Arbitrum, the speed tier therefore makes little difference.
Watch these signals if you want an early warning of cost changes:
- Block utilization on Arbitrum, which shows how close the chain runs to its gas targets.
- The Ethereum mainnet base fee, because the L1 posting cost is derived from it.
- The ETH/USD price, which trackers use to convert gwei into dollars.
A tracker that shows a dollar amount is multiplying a gas amount by a live ETH price. The dollar figure moves even when the gwei number stays the same.
How does Arbitrum calculate fees?
Arbitrum charges for two things, and the total is TXFEES = P * (L2G + ((L1P * L1S) / P)). This is the formula from the Arbitrum gas estimation guide. The terms are:
| Term | Meaning |
|---|---|
P | The L2 gas price. It starts at a floor price and increases with demand |
L2G | Gas used by the transaction’s computation on Arbitrum, without the posting cost |
L1P | The estimated cost of posting 1 byte to the parent chain. Take l1BaseFeeEstimate and multiply it by 16 |
L1S | The size in bytes of the data posted to the parent chain, including a fixed overhead of about 140 bytes |
Dividing the L1 cost by P converts it into L2 gas units, and adding it to L2G gives one gas number. The wallet multiplies it by the price.
The data posted to Ethereum is compressed before it is posted. The Arbitrum documentation says each transaction’s footprint is estimated by compressing it alone with Brotli at its lowest level and charging 16 gas per byte of the result. Calldata that compresses well therefore costs less.
Two mechanisms keep the price stable. First, the L2 gas price has a floor, which you can read with getMinimumGasPrice on the ArbGasInfo precompile. Second, the base fee uses several gas targets, each with its own adjustment window. Targets with short windows absorb brief demand spikes. Targets with longer windows, up to one day, move the long-term price.
Ethereum’s EIP-4844, which introduced blob space, changed how rollups post data. It is specified in EIP-4844. The Arbitrum fee documentation describes parent chain cost in terms of calldata gas, so read the batch poster documentation for how blobs affect your costs. We do not quote a percentage here.
How do I estimate gas before sending an Arbitrum transaction?
For a simple transfer, eth_estimateGas usually returns a gas limit that already includes the L1 posting component at current prices. The result can drift, because L1P changes independently of your transaction. If you show a quote in a UI, poll the estimate more than once and add a margin.
For a split into components, call NodeInterface.gasEstimateComponents(), which is documented in the NodeInterface reference. It returns four values:
gasEstimate: use it as the gas limit.gasEstimateForL1: the part of the estimate that pays for L1 posting, the bufferBin the guide.baseFee: the L2 gas priceP. Multiply it by the gas limit to get the total cost.l1BaseFeeEstimate: multiply by 16 to getL1P.
Subtract gasEstimateForL1 from gasEstimate to get your L2 execution gas, L2G. The documentation warns that these estimates are approximate and the actual fee may differ. Tell your users the same.
For retryable tickets (messages from Ethereum to Arbitrum), use NodeInterface.estimateRetryableTicket() or the SDK’s ParentToChildMessageGasEstimator.estimateAll(). The guide says these return all gas information needed to send a successful transaction.
Never show the raw eth_estimateGas output as the final cost. Add a margin on top. We use 10 to 15 percent, because the L1 base fee can move between the estimate and inclusion. That figure is our own rule of thumb.
What causes Arbitrum gas fees to spike?
Most spikes start one layer up, on Ethereum, not inside Arbitrum.
- A jump in the Ethereum base fee flows into
L1Palmost immediately. - Calldata that compresses poorly raises your per-transaction cost even when the network is calm.
- A configuration change, such as a new minimum base fee set by chain governance, moves the price floor without any change in demand.
- Sustained high utilization pushes the L2 price up, even if the L1 side stays flat.
If you show fee estimates to users, watch the Ethereum base fee before Arbitrum’s own utilization. The mainnet side moves first and often more sharply.
What does an Arbitrum transaction cost?
A transaction costs the sum of the two parts, in ETH. We do not quote a typical price in dollars, because the price depends on the gas price, the L1 base fee and the ETH rate at that moment.
Use the formula to compute your own number. This worked example uses invented inputs, not live data, to show the arithmetic:
| Input | Value |
|---|---|
P (L2 gas price) | 0.02 gwei |
L2G (execution gas) | 21,000 |
L1P * L1S (L1 posting cost, in gwei) | 1,000 |
The L1 cost converts to L2 gas as 1,000 / 0.02 = 50,000 gas. The total is 0.02 gwei * (21,000 + 50,000) = 1,420 gwei, or 0.00000142 ETH. In this example, the L1 part is more than twice the execution part. That is why the L1 base fee matters so much.
Which operation costs more follows from the formula. A native transfer has little calldata. An ERC-20 transfer has more calldata and more execution. A DEX swap has the most of both. Show a range instead of a single number, and lean toward the high end when you set expectations.
How can I lower Arbitrum fees?
The L1 posting cost is the more controllable half of the fee. These habits reduce it:
- Use consistent function selectors and pack parameters. Repetitive calldata compresses better than unique byte patterns.
- Batch similar operations into one transaction where your design allows it, so the fixed posting overhead is paid once.
- Estimate through
NodeInterfacebefore you send, and do not guess. - Log the estimated and the actual fee for each transaction during development. A few hundred samples show how much margin your contract calls need.
How do I send Arbitrum transfers through an API?
Building your own gas pipeline means calling NodeInterface, tracking L1 base fee drift and padding retryable tickets. If you only send tokens, an API can take that work over.
Chaingateway’s Arbitrum endpoints cover ERC-20 and ERC-721 transfers, balances, addresses and webhooks. In the OpenAPI definition, POST /api/v2/arbitrum/transactions/erc20 requires only from, contractaddress, to and amount, plus password or privatekey. The gas fields (gas, gasprice, maxFeePerGas, maxPriorityFeePerGas) are optional. GET /api/v2/arbitrum/gasprice returns the current gas price.
curl -X POST https://app.chaingateway.io/api/v2/arbitrum/transactions/erc20 \ -H "Authorization: Bearer $CHAINGATEWAY_TOKEN" \ -H "X-Network: testnet" \ -H "Content-Type: application/json" \ -d '{"from": "0x...", "contractaddress": "0x...", "to": "0x...", "amount": 100, "password": "wallet-password"}'To get confirmation events without polling, create a webhook with POST /api/v2/arbitrum/webhooks. Webhooks are not retried automatically, so check GET /api/v2/arbitrum/webhooks/notifications/failed as part of your reconciliation. See the Arbitrum API page and the pricing page for details.
Sources
Frequently asked questions
There is no fixed ranking, because fees change with demand and with the cost of the base layer. Layer 2 networks built on Ethereum, including Arbitrum, usually cost less than Ethereum mainnet, because most computation runs off the base layer. Compare current fees for the transaction type you need.
Gas and token amounts are not interchangeable. A gas fee is paid in the network’s native asset, which is ETH on Arbitrum. The dollar value depends on the ETH price and on the gas your transaction uses.
Gas fees pay for the computation and data your transaction uses. On Arbitrum, the fee also covers posting transaction data to Ethereum, which is included in the single price Nitro shows you.
A gas fee is the cost of executing an action on a blockchain, such as a transfer, a swap or a contract call. On Arbitrum it combines the L2 execution cost with a share of the Ethereum posting cost, computed with P * (L2G + (L1P * L1S) / P).
Partly. With Chaingateway, the gas fields of an ERC-20 transfer are optional, and GET /api/v2/arbitrum/gasprice returns the current gas price. If you need a quote with a split into L2 and L1 parts, call NodeInterface.gasEstimateComponents() yourself.
Ready to build this yourself? Get your API key — 7-day trial, no card required — or see the Arbitrum API for the full endpoint reference.