Definition
A pruned node is a Bitcoin full node that fully validates every block during the initial download but then deletes old block files once they are no longer needed, keeping only the most recent blocks plus the UTXO set. The result is a node that gives you the same trust-minimized validation as an archival full node while using a fraction of the disk space — often around 7–10 GB instead of 600+ GB.
Same security, smaller footprint
A common misconception is that pruning weakens validation. It does not. Pruned nodes verify every signature, every script, and every consensus rule from the genesis block forward — they simply discard the raw historical blocks after checking them. Your node still independently confirms that the chain is valid and tracks your own coins without trusting anyone.
The trade-offs
The cost of pruning is that the node cannot serve old blocks to other peers, and it cannot rescan the full chain for an imported wallet without re-downloading. It also offers no speedup on the initial block download — every block is still fetched and verified before being pruned. Pruning is enabled in Bitcoin Core with the prune configuration setting, which sets a target on-disk size.
Pruned nodes make running your own validation practical on small or low-cost hardware. See the broader full node entry and our self-hosting resources for choosing the right setup.
In Simple Terms
A pruned node is a Bitcoin full node that fully validates every block during the initial download but then deletes old block files once they…