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 a Bitcoin full node requires downloading and storing the entire blockchain, then staying synced as new blocks arrive. For most home internet connections, the ongoing bandwidth usage is manageable — but the initial sync can be a significant data transfer.
This guide covers exactly how much bandwidth a Bitcoin node uses, how to manage it, and what connection types are practical for running a node.
When you first set up a Bitcoin full node, it must download the entire blockchain history from the genesis block (2009) to the current tip. This is called the Initial Block Download or IBD.
As of early 2026:
| Connection | Speed | IBD Duration |
|---|---|---|
| 1 Gbps fiber | Full speed | 1-2 days |
| 200 Mbps cable | ~150-200 Mbps effective | 2-3 days |
| 50 Mbps | ~40 Mbps effective | 4-6 days |
| 25 Mbps | Limited | 7-10 days |
IBD is not just download speed — it is also CPU-intensive (verifying signatures and scripts for every transaction). Faster processors complete IBD faster even at the same download speed.
For home internet plans with data caps, verify your cap before starting IBD. 600+ GB is a significant portion of typical 1 TB/month caps.
After IBD completes, ongoing bandwidth is much lower. Bitcoin adds approximately one block every 10 minutes, each up to 4 MB (effective data size 1-2 MB on average including witness data).
Block data per month: ~1.5 MB × 6 blocks/hour × 24 hours × 30 days ≈ 6.5 GB of block data
However, a full node also exchanges mempool transactions, peer announcements, and other overhead:
Typical monthly bandwidth for a full node:
Upload is significantly higher than download because your node serves blockchain data to other nodes on the network. A generous node that accepts incoming connections can upload hundreds of GB per month.
Bitcoin's network health depends on nodes sharing data. When you run a full node with incoming connections enabled, you serve:
A node that is well-connected (8-16 incoming connections) can easily upload 200-300 GB/month. On metered connections or plans with upload caps, this is a meaningful cost.
Limit upload connections: In bitcoin.conf, set maxconnections=8 (default is 125 for listening nodes). Fewer connections = less upload.
Set upload target: Bitcoin Core allows setting a daily upload target:
maxuploadtarget=5000
This limits to approximately 5 GB/day (150 GB/month). Bitcoin Core will reduce serving historical data to non-critical peers when approaching the limit.
Disable listening: Setting listen=0 in bitcoin.conf prevents incoming connections entirely. Your node downloads data but serves nothing. This makes you a "leech" on the network — only recommended if bandwidth is severely constrained.
A pruned node downloads the full blockchain for verification but deletes old blocks after validation, keeping only recent data. This reduces disk requirements from 600+ GB to as low as 1-2 GB (with extreme pruning) or 10-50 GB for a typical setup.
Does pruning reduce bandwidth? Not significantly for ongoing operations. A pruned node still downloads all blocks as they arrive — it just deletes them after verification. The ongoing monthly bandwidth is similar to a full archival node.
IBD bandwidth is the same — pruned nodes still download the entire blockchain during initial sync, then delete old blocks. The storage reduction is dramatic; the bandwidth reduction is minimal.
Minimum recommended: 25 Mbps download, unlimited or 200+ GB/month data plan.
Comfortable setup: 100+ Mbps download, unlimited data plan. This covers IBD quickly and allows generous upload serving.
Not recommended: Metered mobile connections, strict data caps under 100 GB/month, slow DSL below 10 Mbps.
Schedule IBD: Some home setups can schedule large downloads during off-peak hours (overnight) to stay within data caps or avoid congestion. Bitcoin Core does not natively schedule, but router-level traffic shaping or QoS settings can prioritize or limit node traffic at certain times.
Use wired connection: Running a Bitcoin node over WiFi is possible but introduces reliability issues. Wired Ethernet is strongly preferred for uninterrupted sync and peer connections.
Separate from household traffic: If your node is aggressively serving peers (high upload), it may saturate your connection and affect other household internet use. Router QoS settings can limit the node's bandwidth.
Raspberry Pi nodes (popular for home setups via Umbrel, RaspiBlitz, Start9) have the same blockchain bandwidth requirements as any other node — the hardware does not change the data volume.
Raspberry Pi 4 and 5 have Gigabit Ethernet, making them capable of fast IBD on fast connections. USB 3.0 SSD speeds are sufficient for the storage side.
How long does the initial Bitcoin blockchain download take? Typically 2-7 days on a broadband connection. A 200 Mbps connection with a fast SSD can complete IBD in 2-3 days. Slow HDD storage or weaker CPUs can extend this to a week or more.
Does running a Bitcoin node slow down my internet? During IBD, yes — it uses significant bandwidth that may affect other household usage. During normal operation, the download impact is minor (15-25 GB/month). Upload can be more impactful if you allow many incoming connections.
Can I run a Bitcoin node on a metered connection? Not easily. IBD requires 600+ GB download upfront. Ongoing bandwidth of 200+ GB/month makes metered LTE/5G connections impractical and expensive for most node operators.
What is the minimum internet speed for a Bitcoin node? A node will technically function at any speed, but 25 Mbps download is a practical minimum for reasonable IBD completion times. Slower connections lead to extended sync times and the node may fall behind blocks temporarily.
Does pruning reduce bandwidth usage? Pruning reduces storage requirements dramatically (600 GB → as low as 2 GB) but has minimal impact on bandwidth. You still download all blocks — you just delete them after verifying.
Get our free Beginners Guide to Buying Bitcoin plus weekly insights for long-term holders.
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.
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.