Our earlier guide on gas fees on Base covers the basics: gas is the small network fee paid in ETH, and on Base it is usually a fraction of a cent. That is true and it is the right level of detail for a first read. But if you have ever looked closely at a transaction on a block explorer and wondered why the fee is split into a few different lines, this article is for you. A Base transaction fee is actually built from three separate pieces, and they do not all behave the same way.
Two fees, not one
Every transaction on Base pays for two different things at once.
The first is the L2 execution fee. This covers the actual computation, updating balances, running a smart contract, recording the result on Base's own chain. This part is cheap and fairly stable, because Base has plenty of capacity for the volume it handles day to day.
The second is the L1 data fee. Base is a rollup, which means it does not try to be secure on its own. Instead, it periodically bundles up batches of transactions and posts a compressed record of them to Ethereum, so that Ethereum's much larger and more battle tested set of validators can anchor Base's history. Publishing that data on Ethereum costs money, because Ethereum block space is not free, and Base passes a small slice of that cost on to whoever created the transaction.
In practice, the L1 data fee is usually the bigger of the two numbers, and it is the one that moves around the most. When Ethereum itself is busy, the cost of posting data there rises, and that shows up as a slightly higher fee on Base, even though nothing about Base's own traffic changed. When Ethereum is quiet, the same Base transaction gets cheaper. This is the main reason a swap on Base can cost noticeably more on one day than another, even if the Base network feels equally calm both times.
Where EIP-1559 fits in
The L2 execution fee itself is not a single flat number either. Base uses the same fee mechanism Ethereum introduced with EIP-1559, split into a base fee and a priority fee.
The base fee is set by the protocol itself, not by you or by whoever you are transacting with. Each block, the network looks at how full the previous block was compared to a target size, and adjusts the base fee up or down accordingly. Busier blocks push it up a little, quieter blocks let it drift down. You never choose this number, your wallet reads it from the network and pays whatever it currently is. Unlike a typical network fee, the base fee is not paid out to anyone, it is burned, removed from circulation entirely.
The priority fee, sometimes called a tip, is the small optional amount you add on top to signal urgency. On a network as fast and roomy as Base, the priority fee is normally tiny or close to zero, because there is rarely a queue worth jumping. It matters more on Ethereum mainnet, where block space is genuinely scarce and a higher tip can mean the difference between a transaction landing this block or several blocks later.
Base's version of this mechanism is tuned for its own conditions. Blocks can flex well beyond their target size to absorb a sudden burst of activity without the base fee spiking hard, and the base fee itself is designed to move gradually rather than in sharp jumps between blocks. The overall effect is fees that respond to real demand but rarely swing wildly from one moment to the next.
Why this is worth knowing
None of this changes what you actually do as a user. Your wallet calculates all three pieces automatically and shows you a single estimated total before you confirm, exactly as described in our gas fees guide. You do not need to set a base fee, a priority fee, or an L1 data fee by hand.
What it does explain is two things people sometimes find confusing. First, why the fee for what feels like the same action can differ from day to day, sometimes even hour to hour. If Ethereum is congested from unrelated activity elsewhere, Base's L1 data fee rises with it, and your swap costs a bit more, through no fault of Base's own traffic. Second, why fees on Base still stay low even during those moments. The execution side, which is the part Base fully controls, remains cheap and predictable. Only the smaller L1 slice moves with Ethereum, and it is a slice, not the whole bill.
The short version
A Base transaction fee is not one charge, it is three: an L2 base fee set automatically by the protocol and then burned, an optional priority fee that acts as a tip and is normally negligible on Base, and an L1 data fee that pays your share of anchoring the transaction back to Ethereum. The first two follow Base's own EIP-1559 style fee market and stay cheap because Base has room to spare. The third rises and falls with Ethereum's own congestion, which is why the total can shift a little even when nothing on Base itself has changed. Your wallet does the math for you either way, but knowing the pieces makes an unexpected fee change a lot less mysterious.