# Full nodes vs pruned nodes

A pruned node verifies everything an archival node does, then deletes old blocks to save disk space. Compare both and choose the right one.

Canonical page: https://mybitcoinexplorer.com/learn/full-vs-pruned-nodes
Topic: Nodes and the network
Published: 2026-10-29
Updated: 2026-10-30


## Same checks, different storage
> Diagram: Both node types verify every block; they differ only in what they keep — Download block → Verify: every rule → Update UTXO set → *Keep the block?: archival: yes · pruned: no

| | Archival full node | Pruned node |
|---|---|---|
| Downloads and verifies every block | Yes | Yes |
| Keeps all old blocks | Yes, hundreds of GB | No, only recent ones |
| Keeps the UTXO set | Yes | Yes |
| Can serve old blocks to others | Yes | No |
| Can rescan old wallet history | Yes | Only within kept blocks |

## How pruning works
After a block is verified and its effects are applied to the UTXO set, the raw block isn't needed to check new ones. A pruned node deletes old block files, keeping at least the most recent 550 MB (the minimum setting in Bitcoin Core).

## Which to choose
- **Pruned:** you want to verify and use your own wallet on limited disk.
- **Archival:** you run services that need history, like an explorer, an indexer or an electrum server.

### Worked example: MyBitcoinExplorer runs archival
An explorer must show any old block, so our node is unpruned and keeps every block since the [The genesis block](https://mybitcoinexplorer.com/learn/genesis-block) on a dedicated volume.


## What a pruned node is not
It's not a "light" node. A light client doesn't verify everything. See [SPV and light clients](https://mybitcoinexplorer.com/learn/spv-light-clients).


## Enable pruning in Bitcoin Core
Add a line like `prune=10000` to `bitcoin.conf` to keep about 10 GB of recent blocks. The minimum is 550 (MB). Restart Bitcoin Core and it deletes old block files as it goes.

## Pruning limitations to know
- You can't rescan a wallet for transactions older than the blocks you kept.
- You can't serve old blocks to new nodes syncing from you.
- Some tools, like address indexers, need an archival node.


## Key takeaways

- Pruned nodes verify everything but delete old block files.
- Archival nodes keep all blocks and can serve history.
- Both enforce exactly the same consensus rules.

## Common questions

### Is a pruned node less secure?

No. It verified every block itself. It just can't serve old blocks to others.

### Can I un-prune later?

Yes, but the node has to download the deleted blocks again.

### How much disk does a pruned node need?

As little as a few gigabytes, depending on the prune setting, plus space for the UTXO database.

### Is a pruned node a light wallet?

No. A pruned node fully validates every block; it just doesn't keep old ones.

## Related lessons

- [What is a Bitcoin node?](https://mybitcoinexplorer.com/learn/what-is-a-bitcoin-node)
- [Initial block download (IBD)](https://mybitcoinexplorer.com/learn/initial-block-download)
- [SPV and light clients](https://mybitcoinexplorer.com/learn/spv-light-clients)
- [What is the blockchain?](https://mybitcoinexplorer.com/learn/what-is-the-blockchain)