Should you run a Bitcoin full node or pruned node? This guide explains the difference, what pruning does and does not compromise, and which setup is right for you.
Running a Bitcoin node is one of the most powerful ways to participate in the network. But when you start researching, you'll encounter a choice: run a full archival node that stores the entire blockchain history, or a pruned node that keeps only recent blocks.
Most people should run a pruned node. Here's the complete breakdown.
A Bitcoin full node independently downloads and verifies every block and transaction ever added to the Bitcoin blockchain. It maintains the complete UTXO set (unspent transaction outputs) and can answer queries about any transaction back to the genesis block.
Storage requirements (2026): ~650–700 GB and growing at ~60–70 GB/year
When people say "run your own node," they're usually talking about a full node. It's the gold standard: no trust in anyone else's data, complete history, able to serve other nodes.
A pruned Bitcoin node downloads and verifies the entire blockchain but then deletes old block data, keeping only the most recent blocks and — crucially — the full UTXO set.
A pruned node:
Storage requirements: As low as 2–10 GB, depending on configuration
| Feature | Full Archival Node | Pruned Node |
|---|---|---|
| Verifies all transactions | Yes | Yes |
| Maintains UTXO set | Yes | Yes |
| Validates new blocks | Yes | Yes |
| Stores complete history | Yes | No |
| Serves historical data to peers | Yes | No |
| Storage (2026) | ~650–700 GB | 2–10 GB |
| Storage growth/year | ~60–70 GB | Stays flat |
| Hardware requirement | High (large SSD) | Low (any storage) |
| Helps network bootstrapping | Yes | No |
| Trustless for your wallet | Yes | Yes |
| Runs on Raspberry Pi 4 | Technically (slowly) | Yes, easily |
This is the most important point: pruning does not reduce your security or trustlessness for personal use.
Your pruned node:
Pruning only affects your node's ability to serve historical data to other nodes. For your own use — verifying your wallet transactions, not trusting third parties, participating in network consensus — a pruned node is fully equivalent to a full node.
A full archival node is specifically needed if you:
If none of these apply to you, a pruned node serves your needs perfectly.
Pruning is built into Bitcoin Core. To enable it, add to your bitcoin.conf:
prune=550
The number is in megabytes. The minimum is 550 MB. Common settings:
| Setting | Storage Used | Weeks of History Kept |
|---|---|---|
prune=550 | ~550 MB | ~2–3 weeks |
prune=2000 | ~2 GB | ~8–10 weeks |
prune=10000 | ~10 GB | ~40+ weeks |
prune=0 (default) | ~650 GB | All history |
For most personal users, prune=550 or prune=2000 is ideal. Your full UTXO set is always maintained regardless of this setting.
Almost any hardware works:
Requires more serious hardware:
Umbrel (umbrel.com): Supports both modes. Default installation often starts with pruned and lets users upgrade to full archival if they add storage.
Start9 Server One: Runs full archival node by default; 2 TB SSD included.
RaspiBlitz: Full archival node focused; requires 1 TB+ SSD.
Nodl: Full archival node hardware.
myNode: Supports both modes.
Whether pruned or full, your node must perform an Initial Block Download (IBD) — downloading and verifying the entire blockchain from the beginning.
This takes the same time regardless of pruning because Bitcoin Core verifies everything before pruning old data.
Typical IBD times (2026):
After IBD completes, pruning engages and old block data is deleted. Ongoing sync is minimal bandwidth.
If you want to run a Lightning Network node, the requirements change:
However, running Lightning with a pruned node may require careful configuration. Most pre-built node packages (Umbrel, Start9, RaspiBlitz) handle this automatically.
Run a pruned node if:
Run a full archival node if:
Verdict: For 95% of Bitcoin holders who want sovereignty without running data center infrastructure, a pruned node is the right choice. Set prune=2000 in Bitcoin Core, sync once, and you have a fully sovereign Bitcoin node on minimal hardware.
Is a pruned node less secure? No. A pruned node verifies every block from genesis — it just deletes the raw block data afterward. Your UTXO set is complete and your validation is identical to a full node.
Can I switch from pruned to full without re-syncing? Unfortunately, no. If you want to switch from pruned to full archival, you must re-download the entire blockchain from scratch.
Can a pruned node mine Bitcoin? Bitcoin mining requires valid block templates, not historical data. A pruned node technically can mine but the economics of mining require specialized ASIC hardware and pool connections — node storage type is irrelevant.
Do I need a static IP to run a node? No. You can run a node on a dynamic IP, but for best connectivity, configure your router's port forwarding for port 8333. A Tor-only node is also an option for privacy.
How much bandwidth does a Bitcoin node use? A fully connected node (8 outbound + multiple inbound connections) uses roughly 100–200 GB/month for a full archival node, and somewhat less for a pruned node. You can limit connections and bandwidth in bitcoin.conf.
Get our free Beginners Guide to Buying Bitcoin plus weekly insights for long-term holders.
A Bitcoin full node downloads 600+ GB during initial sync and uses 200+ GB/month ongoing. This guide covers exact bandwidth requirements by connection type, how to manage upload costs, and whether pruning helps.
Running your own Bitcoin node protects your financial privacy in ways most users never consider. This guide explains exactly what threats a personal node defends against and how to set it up correctly.
How much bandwidth does a Bitcoin node use? Complete breakdown of IBD data, ongoing monthly usage, pruned vs full node differences, and how to limit bandwidth.