# Ethereum Node Requirements Still Start at 2 TB Despite Pruning

By Simon Yoon

Canonical URL: https://www.tokenpost.com/news/technology/24420
Published: 2026-09-26T13:10:00.000Z
Updated: 2026-09-26T13:10:00.000Z
Section: Technology

> A complete node combines execution and consensus clients, while snap-synced Geth data alone can require 500 GB or more.

Ethereum node operators still face substantial storage requirements despite pruning tools that reduce the amount of historical blockchain data kept locally.

A complete Ethereum node uses both an execution-layer client and a consensus-layer client. Minimum hardware includes a two-core CPU, 16 GB of RAM, a 2 TB NVMe solid-state drive and at least 25 megabits per second of bandwidth.

Snap-synced Geth requires 500 GB or more of storage, while consensus-client data generally adds another 200 GB. Full-node guidance recommends a 4 TB drive, underscoring why the storage footprint of one pruned client does not represent every node configuration.

Ethereum’s storage needs continue to grow as blockchain data accumulates. EIP-4444 permits execution clients to discard certain historical data beyond the specified epoch threshold.

Pruning lowers disk demands while shifting access to some older records to external data providers or archival nodes. Running a node lets users check the chain themselves and broadcast transactions to the network.

The network’s node software is designed to run on ordinary computers, making hardware accessibility a key part of Ethereum’s decentralization model. Storage remains the main constraint, while synchronization speed varies with the client, configuration and sync method.

Glamsterdam was being tested on the Platåberget testnet in August. The upgrade affects both Ethereum’s consensus and execution layers.