What changed for ETH blob limits?

TLDR

Ethereum (ETH) just raised its blob capacity parameters, lifting the maximum blobs per block to 21 and the target to 14 via a small hard fork to boost rollup throughput this week.

1. Max blobs per block increased to 21%%CKPROTECTED2%% (from 15), expanding data headroom for L2s now.
2. The blob target rose to 14%%CKPROTECTED2%% (from 10), the key utilization threshold the network aims to operate around per developers.
3. Each blob is 128 KB, so blocks can now carry up to about 2.69 MB of blob data, helping stabilize rollup fees per the update.

Deep Dive

1. What Changed

Ethereum activated its second Blob Parameter Only fork on 7 Jan (UTC), raising the blob target to 14 and the ceiling to 21 to increase data availability for rollups. This was a planned, incremental scaling step to widen capacity without a full protocol overhaul as reported.

• The change affects proto-danksharding blobs, temporary data used by L2s to post batches efficiently.
• Max blobs per block went 15 to 21, target 10 to 14, executed around 1:01 am (UTC) on 7 Jan per coverage.

2. Why It Matters

More blob capacity helps L2s like rollups settle data with less competition, making fees smoother and less spiky when demand rises. With blobs at 128 KB each, the new ceiling allows up to roughly 2,688 KB of blob data per block, improving throughput and cost stability for rollups per the update.

1. The higher target (14) is the more important operating point; capacity near the 21 ceiling can strain node bandwidth and storage, so the target guides sustainable usage noted here.
2. Fees have been steadier since the first blob-parameter tuning in December, consistent with rollups moving more data off-chain as summarized.

3. What To Watch Next

Developers are discussing further, measured capacity increases and roadmap items that compound these gains. In the near term, a gas limit discussion (for example up to 80 million) is on the table; later in 2026, a planned Glamsterdam fork aims to raise capacity further and introduce parallel processing via Block Access Lists (EIP-7928) according to reporting.

• Key indicator: how often blob usage approaches the 14 target or the 21 cap.
• If usage persistently tests the cap, bandwidth and storage pressure could rise and trigger further parameter tuning per the notice above.

Conclusion

Ethereum increased blob capacity to give rollups more reliable, cheaper data posting, lifting the target to 14 and the max to 21. Near term, this supports lower and steadier L2 fees; medium term, watch blob utilization and roadmap steps like higher gas limits or parallelization to see how scaling continues to unfold.