You click "Approve," the wallet shows a fee, you confirm, and a few seconds later you've paid more to grant permission than you expected to pay for the actual trade. Nothing broke. You just paid for a storage write on a busy network, and nobody warned you what that means.
Here's the short version: a token approval doesn't move funds. It writes a permission into the token contract's storage, and the EVM charges you for changing permanent state. A standard ERC-20 approve typically lands somewhere in the tens of thousands of gas, but the exact figure swings with whether you're overwriting an existing allowance, which chain you're on, and what the mempool looks like when your transaction lands.
What your approval transaction actually writes
When you approve a token, you're updating a mapping inside the token contract: spender address, allowance amount. That's it. No tokens leave your wallet. The cost comes from the storage write, and the EVM prices a fresh storage slot differently from one that already holds a non-zero value.
This is where a lot of people get surprised. Suppose you approve 500 USDC to a DEX, then later decide you want to approve 1,000. Some contracts and interfaces route that through a two-step process: set the allowance to zero, then set the new amount. Two transactions, two gas payments. A single overwrite is cheaper in gas terms, but the zero-first pattern exists for safety reasons on certain tokens. Before you hit confirm, know which path your wallet is taking.
What moves the gas number
Storage state
A first-time approval on a token you've never touched costs more than a repeat approval, because you're initializing a storage slot rather than updating one. If you've approved that spender before, you're usually paying less.
Network and timing
On Ethereum mainnet, base fees move with demand. A quiet Sunday morning and a busy airdrop day are different worlds. On cheaper chains, the same approval can cost a fraction of a cent. The transaction logic doesn't change; the price of computation does.
Token contract quirks
Not all ERC-20 tokens are built the same. Some carry extra logic in their approve function, fee-on-transfer mechanics, or hooks that add gas. A token that looks standard on a block explorer may still cost more to approve than a plain vanilla one.
A real scenario: the approval you should have postponed
Say you're on Ethereum mainnet during a moderately busy afternoon. You connect to a new DEX, approve USDC for the first time, and the wallet quotes a gas estimate. You accept without looking closely. The approval confirms for what feels like a lot relative to the trade size you had in mind.
What actually happened: you paid for a cold storage write to a contract you'd never interacted with, at a base fee that reflected current demand, plus a priority tip to get included promptly. Nothing went wrong. You just paid full freight for a first-time state change during peak hours. Had you waited for a quieter window, or approved on a cheaper chain where the same pool existed, the number would have looked very different. The lesson isn't "avoid approvals." It's "check the fee environment before you approve something you could do later."
Habits that keep approval gas from eating your edge
You can't eliminate approval costs, but you can stop them from being an afterthought.
- Batch where possible. Some interfaces let you approve and swap in one flow, saving a separate transaction.
- Approve exact amounts when you trust the contract. An unlimited approval costs roughly the same gas as a limited one but saves you re-approving later.
- Watch the base fee. Wallets show it; a quick glance before confirming tells you whether you're in a cheap window.
- Use the right chain. If the same asset and venue exist on a lower-fee network, the approval math changes entirely.
On a platform like Azbit, the approval step is one line item in a broader cost picture, and it's worth treating it that way rather than as invisible overhead.
Approval gas at a glance
| Factor | Effect on gas |
|---|---|
| First-time approval (new storage slot) | Higher |
| Re-approval (existing slot) | Lower |
| Zero-then-set two-step | Two transactions |
| High network demand | Higher base fee |
| Token with extra logic | Higher per-call cost |
Frequently asked questions
Why does approving a token cost gas when I'm not sending anything?
Because an approval changes the token contract's stored state. You're writing a permission record into a storage mapping, and the EVM charges for that write. No tokens move, but the blockchain still records a permanent change, and permanent changes cost gas.
Is it cheaper to approve a small amount or an unlimited amount?
In most standard ERC-20 contracts, the gas cost of approve is essentially the same whether you set a small number or the maximum. The storage write happens either way. The real savings from a large approval come later, when you avoid paying for a second approval transaction.
Can I get an approval refund?
No. Once a transaction is confirmed, the gas is spent. Some contracts refund gas when you clear an allowance back to zero, but that's contract-specific behavior, not a general rule, and it doesn't apply to the original approval cost.
Does revoking an approval cost gas too?
Yes. Revoking means sending another transaction that sets the allowance to zero, which is itself a state change. It's often cheaper than the original approval because you're clearing an existing slot, but it's not free.
Next time your wallet quotes an approval fee, open the advanced view and check the base fee and the storage-change line before you confirm. That one habit will tell you more than any general rule.