TLDR
There is no single date. Ethereum plans to raise blob capacity in stages starting in 2026, with execution payloads migrating into blobs between 20262028 per the roadmap outlined by Vitalik Buterin (roadmap summary).
- In 2025, upgrades increased blob throughput and enabled PeerDAS, laying the groundwork (network overview).
- Larger non-ZK-EVM-dependent gas limit increases begin in 2026 (roadmap details).
- Timing can shift with core dev coordination; expect progressive increases rather than a single switch.
Deep Dive
1. 2025 Foundations
Ethereum (ETH) implemented upgrades in 2025 that increased blob throughput and activated PeerDAS (data availability sampling), which lets nodes verify data by sampling rather than downloading everything, enabling higher blob counts without straining nodes. These changes set the stage for future capacity increases (network overview).
2. 2026 Begins Capacity Increases
The next phase starts in 2026 with larger gas limit increases that do not depend on ZK-EVMs, alongside initial opportunities to run ZK-EVM nodes. This creates room for higher throughput and supports more blobs per block as safety mechanisms mature (roadmap details).
Improvements will arrive in steps. Expect throughput to rise and L2 data availability costs to trend lower, but changes will be gradual rather than instantaneous.
3. 20262028 Migration Into Blobs
Between 2026 and 2028, developers plan to reprice gas, adjust state structures, and migrate execution payloads into blobs. This migration is the key to safely supporting higher blob counts and sustained capacity growth while preserving decentralization (roadmap summary).
Blob capacity increases are tied to architectural shifts. As execution moves into blobs, throughput and rollup data capacity should expand, potentially lowering L2 fees over time.
Conclusion
Blob capacity on Ethereum is increasing in a staged plan. Foundations were laid in 2025, larger gas limit increases begin in 2026, and the migration of execution into blobs between 20262028 enables higher blob counts. The effect should be progressively better throughput and cheaper data availability for rollups, with exact timing subject to core dev coordination.
