Out of Gas Error What It Means and How to Fix It

05 September 2026

An "out of gas" error means a transaction consumed its entire gas limit before the network could finish executing it. The transaction reverts. Every state change is undone. But the gas you already spent is not refunded.

This is not the same as a transaction that fails for other reasons. A revert can happen because a smart contract’s conditions were not met - for example, a swap that would cause unacceptable slippage. In that case you might get your gas back, minus the base fee. Out of gas is different: the network ran out of computational room mid-execution. You pay for every unit of gas the transaction used up to the point it stopped.

There is a related error: "gas required exceeds allowance." That usually means the gas limit you set was lower than what the transaction actually needs. The network refuses to start because it knows the limit is too low to finish. No gas is consumed in that case.

Typical gas needs for common operations

Gas needed varies by network congestion and contract complexity, but rough benchmarks exist. As of late August 2026:

• A simple ETH transfer: 21,000 units.
• Swapping tokens on a DEX: 150,000 to 300,000 units.
• Minting an NFT on a busy collection: 200,000 to 500,000 units.
• Interacting with a complex DeFi contract: 400,000 to 1,000,000 units.

If your wallet shows an estimate of 60,000 for an NFT mint, something is wrong. That number is far below what the operation typically needs. Spotting these mismatches early saves wasted fees.

What causes an out of gas error

The most common cause is setting a gas limit too low. Wallets and dApps often auto-estimate. Those estimates can fail for unusual contract logic or during network spikes.

Another cause: the contract itself uses more gas than expected. Developers can write inefficient code. Or the transaction path involves loops that run longer than anticipated.

A third cause is that the transaction’s complexity changes between estimation and submission. If many users are hitting the same contract, the state shifts. The actual gas needed becomes higher than the estimate.

The practical fix

Raise the gas limit manually. Do not trust the auto-fill blindly.

Open the advanced settings in your wallet. Find the gas limit field. Add a buffer. For a swap, 200,000 is often safe, but 300,000 gives more room. For an NFT mint, 400,000 is conservative. The extra cost is minimal - you only pay for what you use, up to the limit. So a higher limit does not mean a higher fee unless the transaction actually needs that much gas.

Better yet: simulate the transaction first. Some wallets and block explorers let you run a dry call. If the simulation completes, you know the gas limit is sufficient. If it fails with out of gas, increase the limit and try again.

For the "gas required exceeds allowance" variant, the fix is the same. Increase the limit until the transaction is accepted.

What not to do

Do not lower the gas limit to save money. That is the fastest way to trigger an out of gas error. The gas you lose on a failed transaction will cost more than the tiny buffer you tried to save.

Do not ignore the error and retry with the same settings. That guarantees the same result.

Do not assume the dApp’s suggested gas limit is correct. It is an estimate, not a guarantee.

Final note

Out of gas errors are a feature of Ethereum’s design, not a bug. Every computation costs gas. When the limit runs out, the network stops. The fix is mechanical: give the transaction more room to breathe.

Check the estimate against known benchmarks. Simulate when possible. And remember: a failed transaction still costs you. A successful one costs only what it uses. Spending a few extra seconds on the gas limit is worth the difference.

Back to gas fees