Why Bitcoin's Block Size Is Limited

A new Bitcoin block arrives about every ten minutes, and there's a hard limit on how much data it can hold. That limit is why fees spike when the network is busy, and it was the subject of the most bitter argument in Bitcoin's history.

Why have a limit at all?

Every full node downloads and checks every block. That independent checking is what lets Bitcoin run without trusting anyone: if a miner breaks the rules, nodes reject the block. The system only works if lots of people can afford to run a node.

Bigger blocks raise that cost. More bandwidth, more storage (the chain is already several hundred gigabytes) and more processing for each block. Large blocks also travel more slowly between miners, which favours big, well-connected mining operations over small ones. Push block size far enough and only data centres can validate the chain. At that point you're trusting them.

So the limit is a deliberate trade-off. It gives up throughput in exchange for keeping verification within reach of ordinary people.

Where did the 1 MB limit come from?

Satoshi Nakamoto added a 1 MB cap in 2010, mainly as an anti-spam measure while the network was small and blocks were nearly empty. For years it didn't matter. By 2015, blocks were filling up and fees were rising, and the question of whether to raise the cap became urgent.

What was the block size war?

Two camps formed. One wanted to raise the limit (to 2 MB, 8 MB or more) so Bitcoin could process more payments on-chain and stay cheap to use. The other argued that bigger blocks would erode decentralisation step by step, and that scaling should come from more efficient transactions and layers built on top.

The fight ran through proposals, conferences and competing software from about 2015 to 2017. It was settled in two ways at once. In August 2017 SegWit activated on Bitcoin, and in the same month a group that wanted much bigger blocks forked off to create Bitcoin Cash.

What did SegWit change?

SegWit (Segregated Witness) replaced the 1 MB size limit with a block weight limit of 4 million units. Signature data, the "witness", is counted at a quarter of the weight of other data. In effect, blocks can carry more transactions without raising the cost of validating them in the same proportion. Real blocks now commonly run around 1.5 to 2.5 MB.

SegWit also fixed a long-standing bug called transaction malleability, which cleared the way for Lightning.

Taproot, activated in 2021, built on this. It makes complex spending conditions cheaper and more private by making them look like ordinary payments on-chain. It left the weight limit alone.

How does Bitcoin scale, then?

In layers. The base chain is treated as a settlement layer: slow, expensive per byte, and very hard to change. The Lightning Network lets two parties open a payment channel with one on-chain transaction, send any number of payments back and forth off-chain, then settle the final balance with one more. Exchanges and custodians also batch many withdrawals into single transactions.

The result is a fee market. When demand for block space outruns supply, users bid with fees, and miners include the highest fee rates first. That's why fees jump during busy periods, such as sharp market moves or bursts of inscription activity, and fall back when things calm down.

What does this mean for you day to day?

Two practical things. First, when the market is moving fast, on-chain fees often rise at exactly the moment you'd want to move coins. If you might need to move funds in a hurry, plan for that. Second, the fee you pay depends on how many bytes your transaction takes up, not on how much bitcoin you send. Our guide to how Bitcoin transactions work explains why a small payment from a wallet with many small inputs can cost more than a large one.