Pruned vs. Full Nodes
Pruned vs. Full (Archival) Nodes
A common hurdle for beginners wanting to run their own Bitcoin node is the massive storage requirement. As of 2026, the entire history of the blockchain is over 600 gigabytes and growing.
Fortunately, Bitcoin is designed with an elegant solution that slashes this storage requirement by 98%: Node Pruning.
🏛️ What is an Archival Node?
An Archival Node (often simply called an unpruned full node) is a computer that stores the entire history of the Bitcoin network on disk forever.
- File Structure: It stores raw block data inside files named
blk????.dat(where????is a counter, e.g.,blk0000.dat,blk0001.dat). - Role in the Network: Because it keeps every historical block, an archival node can serve historical data to new nodes joining the network. When a new node does its Initial Block Download, it connects to archival nodes to fetch old blocks.
- The Downside: It requires a large, expensive 1TB+ solid-state drive (SSD), and this storage requirement increases every 10 minutes as new blocks are mined.
✂️ What is a Pruned Node?
A Pruned Node is a full node that validates the entire blockchain during startup but discards old, raw block files once they have been verified and processed.
A pruned node does NOT compromise on security. It performs the exact same mathematical validation of every transaction and block from 2009 to the present day. The validation process is identical to an archival node. The only difference is that once a historical block has been thoroughly verified, the node deletes the raw block file from its hard drive to free up space.
How Pruning Works
- Initial Download: The pruned node starts up and downloads Block 1.
- Validation: It verifies the block and updates its UTXO set (the database of unspent coins, located in the
chainstatedirectory). - Repeat: It repeats this for Block 2, Block 3, and so on.
- Deletion: Once the node has downloaded and validated a user-defined threshold of blocks (e.g., 550MB worth of data), it deletes the oldest raw
blk????.datfiles from disk, keeping only the UTXO database and the most recent blocks.
📊 Comparison: Pruned vs. Archival Node
| Feature | Archival Full Node | Pruned Full Node |
|---|---|---|
| Disk Space Required | ~600+ GB | ~10 GB |
| Consensus Enforcement | 100% Independent | 100% Independent |
| Initial Sync Requirement | Must download & validate all blocks | Must download & validate all blocks |
| Serves New Syncing Peers | Yes (can seed the network) | No (does not have historical blocks to send) |
| Historical Wallet Rescan | Yes (can scan old transactions) | No (limited to the pruning window) |
⚙️ How to Configure Pruning in bitcoin.conf
To enable pruning, you simply need to add a single line to your bitcoin.conf file before launching Bitcoin Core:
# Enable pruning and set the target limit in megabytes (minimum is 550)
prune=550
By setting prune=550, Bitcoin Core will ensure that your raw block file storage never exceeds 550 megabytes. When combined with the essential chainstate UTXO database (which is ~5-8GB), your entire node footprint will comfortably fit inside less than 10 gigabytes!
This allows you to run a fully secure, trustless, consensus-enforcing Bitcoin node on a cheap laptop, an office PC, or even a basic home server without buying expensive external storage.
TeachMeBitcoin is an ad-free, open-source educational repository curated by a passionate team of Bitcoin researchers and educators for public benefit. If you found our articles helpful, please consider supporting our hosting and ongoing content updates with a clean donation: