monerod --prune-blockchain. A 256GB SSD holds a pruned node for years. Same security as a full node — just less historical data stored locally. Run your own node for maximum privacy.
| Aspect | Full Node | Pruned Node |
|---|---|---|
| Storage (2026) | 200-210 GB | 65-75 GB |
| Annual growth | ~25-30 GB/year | ~8-10 GB/year |
| Validation | Full | Full |
| Wallet sync | Works | Works |
| Serve old blocks | Yes (all) | Partial (1/8) |
| Initial sync time | 12-48 hours | 6-24 hours |
| Minimum SSD | 500 GB | 256 GB |
| Network contribution | Maximum | Good |
Monero's pruning keeps:
All block headers — needed to verify the chain of proof-of-work from genesis to present.
Recent blocks (last 5,500) — needed for wallet syncing and reorg handling.
1/8 of old transaction data — each pruned node keeps a different stripe. The network collectively retains all data.
What it removes: 7/8 of old transaction bodies that are only needed for bootstrapping new nodes from scratch.
| Scenario | Command |
|---|---|
| Start pruned (new sync) | ./monerod --prune-blockchain |
| Sync only pruned blocks | ./monerod --prune-blockchain --sync-pruned-blocks |
| Prune existing database | ./monero-blockchain-prune (offline tool) |
| Pruned + Tor | ./monerod --prune-blockchain --proxy 127.0.0.1:9050 |
| Check if pruned | ./monerod status (shows “pruned”) |
Note: Pruning is irreversible. To get a full blockchain back, you must re-sync from scratch.
Prune if: You have <500GB storage, want to run your own node on a laptop or small SSD, or just want the privacy benefit of not using remote nodes.
Don't prune if: You have plenty of storage and want to help the network serve full blockchain data to new nodes.
Running any node (pruned or full) is infinitely better than trusting a remote node with your transaction data.