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.
One of the most common questions from people considering running a Bitcoin node is: "How much bandwidth will it use?" The answer matters whether you're on a metered home internet plan, running on mobile data, or just want to know the cost.
Here's the complete breakdown.
When you first start a Bitcoin node, it downloads the entire blockchain history. As of 2026, the complete blockchain is approximately 650–700 GB.
During IBD, your node downloads this data as fast as your connection allows:
| Connection Speed | Time to Complete IBD | Data Used |
|---|---|---|
| 100 Mbps | 15–20 hours | ~650 GB |
| 50 Mbps | 30–40 hours | ~650 GB |
| 25 Mbps | 60–80 hours | ~650 GB |
| 10 Mbps | 150+ hours | ~650 GB |
| 5 Mbps (slow home DSL) | 5–7 days | ~650 GB |
IBD is a one-time event. Once your node is synced, ongoing bandwidth drops dramatically.
After IBD, your node only needs to keep up with new blocks and transactions. Bitcoin currently adds about 60–70 GB of new blocks per year (~5–6 GB/month).
But your actual bandwidth usage depends heavily on your node configuration — specifically how many peer connections you allow.
If you run Bitcoin Core with default settings:
The majority of bandwidth on a fully connected node is serving other nodes — sending block and transaction data to peers who request it.
If you close port 8333 (no inbound connections):
A pruned node discards old block data but otherwise functions identically for validation. A pruned node with inbound connections closed:
Pruning reduces storage but does NOT reduce bandwidth — you still download and verify all data during IBD, and must process new blocks continuously.
| Type | Direction | Bandwidth Share |
|---|---|---|
| Block downloads (new blocks, 10 min avg) | Inbound | Low — 1–4 MB per block |
| Transaction relay (mempool) | Both | Moderate — constant stream |
| Serving block history to other nodes | Outbound | Highest — if port 8333 open |
| Peer discovery (addr messages) | Both | Minimal |
If your node has port 8333 open and allows inbound connections, serving block data to newly syncing nodes will dominate your bandwidth usage.
Add to bitcoin.conf:
maxuploadtarget=5000
This limits your node's total upload to 5 GB/day (5,000 MB). Useful if you have a monthly data cap.
maxconnections=20
Reducing from the default 125 to 20 significantly reduces bandwidth without eliminating peer connectivity.
listen=0
This disables all inbound connections. Your node only connects outbound. Bandwidth drops to 10–30 GB/month.
For users on metered connections or data caps:
prune=550
listen=0
maxconnections=8
maxuploadtarget=1000
Expected usage: Under 15 GB/month after IBD.
| Node Configuration | Monthly Bandwidth (after IBD) |
|---|---|
| Full node, inbound open (default) | 200–400 GB |
| Full node, no inbound | 15–30 GB |
| Pruned node, inbound open | 150–350 GB |
| Pruned node, no inbound | 10–20 GB |
| Pruned + maxuploadtarget set | Configurable |
If you run an Electrum server (like Electrs or Fulcrum) on top of your Bitcoin node to serve your own wallets, add significant bandwidth:
Running a Lightning Network node alongside Bitcoin Core adds:
If you have an ISP data cap:
| Monthly Cap | Recommendation |
|---|---|
| Unlimited | Run full node with inbound connections |
| 2 TB/month | Full node with inbound, monitor usage |
| 1 TB/month | Full node, consider limiting upload |
| 500 GB/month | Pruned node, limit inbound/upload |
| Under 500 GB | Pruned node, disable inbound, use maxuploadtarget |
| Under 100 GB | Not recommended without strict limits |
| Device | Default Config | Estimated Monthly Bandwidth |
|---|---|---|
| Umbrel (default) | Full node, port 8333 open | 200–400 GB |
| Start9 Server One | Full node, port 8333 open | 200–400 GB |
| RaspiBlitz | Full node, configurable | Varies by config |
| myNode | Full or pruned, configurable | Varies |
All pre-built node solutions allow you to adjust these settings. Check your ISP data situation before enabling inbound connections.
Does running a Bitcoin node use a lot of data? After initial sync (650 GB one-time), a fully connected node uses 200–400 GB/month. A pruned node with no inbound connections uses only 10–20 GB/month — comparable to moderate video streaming.
Can I run a Bitcoin node on a home internet plan with a 1 TB data cap? Yes, but configure it carefully. Use maxuploadtarget to limit how much data you serve to other nodes. A pruned node with limited upload can stay well under 100 GB/month.
Does a pruned node use less bandwidth than a full node? No — a pruned node downloads the same data during IBD and receives the same new blocks. The difference is storage, not bandwidth. However, a pruned node can serve less historical data to peers (since it deleted old blocks), reducing upload bandwidth.
How much bandwidth does the Lightning Network add? A small personal Lightning node adds roughly 5–20 GB/month on top of Bitcoin Core bandwidth. A large routing node with many channels can use significantly more.
Can I run a Bitcoin node on cellular/mobile data? Technically yes but practically no for most users. IBD alone is 650 GB — exceeding most mobile data plans. A pre-synced node on a low-traffic config could run on fast home broadband but cellular is not practical.
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.
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.