What Is Blob Space? A Clear Guide to Ethereum’s New Data Layer

If you follow Ethereum or rollups, you have likely seen the question: what is blob space?
Blob space is a new kind of data space added to Ethereum to make rollups cheaper and faster.
Instead of storing all rollup data directly on-chain forever, Ethereum now has a separate area for large, short-lived data chunks called blobs.

This guide explains blob space in plain language. You will learn what blobs are, why Ethereum added them, how they work under the hood, and what this change means for fees, scalability, and data availability.

Defining blob space in the Ethereum context

Blob space is a separate data area attached to Ethereum blocks, reserved for large pieces of temporary data.
These data pieces are called blobs, short for binary large objects, and they are used mainly by rollups to publish transaction data cheaply.

Two data layers inside each Ethereum block

In simple terms, Ethereum now has two main layers of data in each block that serve different purposes and have different lifetimes.

• Call data (normal block space) – small, permanent data stored in the main chain state.
• Blob space – large, temporary data chunks kept for a limited time, separate from state.
• Commitments to blobs – small proofs stored on-chain that link the blobs to the block.
• Rollup usage – rollups use blob space to post their transaction data for verification.
• Cheaper data availability – blob space is priced differently, so data-heavy use cases pay less.

The key idea is that Ethereum consensus cares that blob data was available to the network at the right time, but Ethereum does not keep the full blob forever in the same way as normal transaction data.

Why Ethereum introduced blob space

Before blob space, rollups had to post their data as call data in Ethereum transactions.
Call data is permanent and stored by all full nodes, so the gas cost for large data was high and kept growing with usage.

As rollups grew, this model had problems. Rollup users paid high L1 data fees, and rollup growth started to push up gas prices for everyone.
Ethereum needed a cheaper, more scalable way to provide data availability for rollups without bloating long-term storage.

Main goals behind adding blob space

Blob space was added to reach several linked goals that all support a rollup-first scaling roadmap for Ethereum.

Blob space solves this by making data availability cheaper, keeping long-term chain size under control, and giving Ethereum a cleaner separation between execution and data.
This change lets the base layer focus on security and consensus while rollups handle most user activity.

What exactly is a blob?

A blob is a large, structured data chunk attached to an Ethereum block but stored outside the normal execution payload.
Blobs are not directly readable by the EVM, but they are linked to the block through cryptographic commitments that act like fingerprints.

You can think of a blob as a data package that a rollup posts to Ethereum.
The blob contains compressed transaction data or state updates, which rollup nodes use to reconstruct the rollup chain and verify correctness.

How blobs relate to smart contracts

The EVM only sees a small reference to the blob, not the full content.
Smart contracts work with these references instead of raw blob bytes, which keeps execution light while still letting the network agree that specific data was published.

This design means blobs help with data availability and verification, while normal contract logic stays focused on state changes and balances.

How blob space works inside an Ethereum block

To answer “what is blob space” fully, you need to see how blobs connect to normal blocks.
Each block can carry a limited number of blobs, and each blob is referenced by a commitment stored on-chain.

The high-level flow is that a rollup creates a blob with its data, the blob is included in a block as blob space, the block stores a small commitment to that blob, and nodes use the commitment to verify the blob’s integrity.

Step-by-step: from rollup data to blob inclusion

The process for using blob space follows a clear sequence. These steps show how rollup data moves from L2 to Ethereum L1.

1. The rollup batches many L2 transactions into a single data payload.
2. The rollup client compresses this payload and formats it as a blob.
3. A transaction on Ethereum references the blob and requests inclusion.
4. Ethereum builders include the blob and its commitment in a block.
5. Full nodes download the blob, check the commitment, and store it temporarily.
6. Rollup nodes read the blob, update their L2 state, and verify correctness.
7. After the retention window passes, many nodes prune the old blob data.

Because the actual blob content lives outside the execution payload, Ethereum clients can treat blob data differently from normal transaction data, which allows pruning while still keeping the compact commitments in block history.

Blob space vs normal block space (call data)

Understanding the difference between blob space and normal block space helps you see why this change matters.
Both carry data, but they serve different goals and follow different rules.

In normal block space, data is permanent and directly used by smart contracts.
In blob space, data is temporary and used mainly for off-chain verification by rollups and light clients.

This split lets Ethereum price long-term storage and short-term data availability separately, which is key for scaling and for keeping node operation reasonable.

Key differences between blob space and call data

This comparison shows why blob space is so useful for scaling: rollups get cheaper, flexible data availability, while the base chain avoids permanent storage of every byte of rollup data.

How blob space lowers rollup costs

Rollup fees are mostly data fees, not computation fees.
Every batch of rollup transactions must be published somewhere that others can read and verify.
On Ethereum, this was call data before blobs, which made large batches expensive.

Blob space introduces a cheaper, more flexible market for data.
Rollups can post large blobs without paying the same high gas price as permanent call data.
The network can also adjust blob pricing based on demand, without disturbing normal transaction gas as much.

Effects on users and rollup design

The result is lower average fees for rollup users and more room for throughput on L2, while Ethereum L1 remains the secure base.
Rollup teams can design protocols that assume cheaper data availability, which encourages more complex apps on L2.

Over time, this cost shift should help move more activity from L1 to L2, while keeping Ethereum as the shared security and data anchor.

What blob space is used for in practice

Today, blob space is mainly used by rollups that follow a data availability on Ethereum model.
These rollups publish their transaction data in blobs so that anyone can reconstruct the rollup chain if needed.

Typical uses of blob space include posting batched rollup transactions, posting proofs or state roots linked to that data, and providing data availability guarantees for fraud proofs or validity proofs.

Beyond rollups: other potential blob use cases

Other possible uses include data-heavy protocols that need short-term public data, such as large voting snapshots or temporary market data.
However, rollups are by far the main driver and will likely remain the primary users of blob space.

As more L2 systems mature, blob space will become a core part of how Ethereum applications share and verify data across many different chains.

Limits, expiry, and data availability in blob space

Blob space is not infinite, and blob data does not live forever.
Ethereum sets a cap on how many blobs each block can include and how long nodes keep blob data.

The network keeps blob data available for a set window, long enough for rollups and light clients to perform checks.
After that period, many nodes can safely prune the blobs, while the small commitments remain on-chain as part of block history.

Why pruning blob data is safe

This design balances three needs: rollups get reliable data availability, node operators avoid unbounded storage growth, and Ethereum keeps consensus data lean.
As long as data is available during the safety window, rollups can finalize their state safely.

After that point, the commitments and rollup state serve as proof that the data was present when needed, so full blob bytes can be discarded by many nodes.

Why blob space matters for Ethereum’s roadmap

Blob space is a key part of Ethereum’s long-term scaling plan.
The network is moving toward a rollup-centric model, where most user activity happens on L2, and L1 provides security and data availability.

By separating execution from data availability, Ethereum can scale throughput by large factors through rollups, without turning L1 into a heavy, hard-to-run chain.
Blob space is a concrete step in that direction and sets the stage for further data sharding upgrades.

What blob space means for developers and users

For developers, blob space changes fee models and design choices.
Teams building rollups, bridges, and data-heavy apps need to plan around blob pricing and blob limits per block.

For users, the effect shows up as cheaper L2 fees and more responsive apps, even if they never hear the word blob in daily use.
Many modern rollups already rely on blob space behind the scenes.

Recap: answering “what is blob space” in one place

Blob space is a new data layer on Ethereum that carries large, temporary blobs used mainly by rollups.
Blobs are referenced by small commitments stored in blocks, while the full blob data is kept off the main state and pruned after some time.

By moving rollup data from permanent call data into blob space, Ethereum reduces data costs, protects long-term node storage, and supports a rollup-first scaling path.
If you use a modern rollup, your transactions likely already depend on blob space, even if you never see it directly.