"Will the replication finish before business hours?", "Can we pull the VM images over the site link this weekend?", "What uplink do we need for a 2 TB nightly backup?" All three are the same calculation in different directions, and all three are easy to get wrong by a factor of 8 (bits versus bytes) or by mixing GB with GiB.
The Bandwidth Calculator solves data volume = bandwidth × time × efficiency for whichever value you are missing: transfer time, data volume, or required bandwidth. It converts every unit exactly, keeps the theoretical and the efficiency-adjusted result apart, and runs in your browser.
What is the Bandwidth Calculator?
In simple terms
You pick a mode, enter the two values you know, and the calculator gives you the third — for example how long 500 GB takes over a 1 Gbit/s link, or how fast a link must be to move 1 TB in 8 hours.
Technical background
Throughput, volume and time are linked by one relation:
volume = bandwidth × time × efficiency
time = volume ÷ (bandwidth × efficiency)
bandwidth = volume ÷ (time × efficiency)Units matter more than the formula. Bandwidth is quoted in bits per second with decimal prefixes (1 Gbit/s = 10⁹ bit/s). Data volume is quoted in bytes, sometimes with decimal prefixes (GB = 10⁹ B) and sometimes binary (GiB = 2³⁰ B). One byte is 8 bits. The calculator converts everything to bits and seconds before dividing.
Efficiency is the share of the line rate that actually carries your payload. Ethernet framing, IP and TCP headers, TLS records, retransmissions and competing traffic all take a slice; on long, high-latency paths TCP's window can cap a single stream well below the link speed. None of that is modelled — you supply a percentage.
Why use the Bandwidth Calculator?
- Plan backup and replication windows with the required-bandwidth mode instead of guessing.
- Set expectations for large downloads, image deployments or data migrations.
- Estimate data volume for metered links or monthly transfer caps ("what is 100 Mbit/s for a full day?").
- Keep assumptions explicit. The theoretical value is always shown; the adjusted value appears only when you enable an efficiency assumption, and exports state which one you used.
- Exact unit handling for bits, bytes, SI and IEC prefixes.
Who should use it?
Backup and storage administrators sizing windows and links, network engineers planning WAN capacity, cloud engineers estimating migration times, MSPs quoting connectivity, and anyone who wants to know how long a download should take. For an actual measurement of your line, run the Internet Speed Test first and feed its result into the calculator.
How the Bandwidth Calculator works
All calculations run locally in your browser using exact fractions on BigInt.
- Inputs are parsed exactly. The same number rules as the other NetTools.tech converters apply: spaces and underscores are ignored, a single comma is a decimal comma, exponents are accepted.
- Conversion to base units. Data volume becomes bits (bit, B, kB … PB, KiB … PiB), bandwidth becomes bit/s (bit/s, kbit/s, Mbit/s, Gbit/s, Tbit/s, B/s, kB/s, MB/s, GB/s, KiB/s, MiB/s, GiB/s), duration becomes seconds (seconds, minutes, hours, days, weeks; a day is exactly 86,400 s).
- Validation. Volume, bandwidth and duration must be greater than zero. Efficiency, when enabled, must be more than 0% and at most 100%.
- Calculation. The theoretical result uses 100% efficiency. The adjusted result divides time and required bandwidth by the efficiency factor, or multiplies volume by it. If you enable efficiency but enter 100, the result is treated as theoretical.
- Formatting.
- Durations are shown as up to three parts, such as
1 h 14 min 4 sor4 d 15 h 6 min, rounded to whole seconds; below one minute as seconds (with decimals under 10 s), and below one second in ms or µs. A year in this format is 365.25 days. The exact number of seconds is listed next to each duration with 3 decimals. - Volumes are shown in the most readable decimal byte unit with the binary equivalent as a note, e.g.
3.6 TBand3.274 TiB. - Required bandwidth is shown in the most readable bit/s unit with the byte rate as a note, e.g.
277.778 Mbit/sand34.722 MB/s.
- Durations are shown as up to three parts, such as
- Formula line. Below the results the calculator prints the formula with your values in bits and seconds, so you can check the arithmetic.
- Comparison table. In transfer-time mode, "The same transfer at common speeds" lists your volume at 10, 50, 100 and 300 Mbit/s and 1 and 10 Gbit/s, theoretical and adjusted.
How to use the NetTools.tech Bandwidth Calculator
- Open the Bandwidth Calculator.
- Choose a Mode: Transfer time ("How long does it take to move this much data?"), Data volume ("How much data can move in this time?") or Required bandwidth ("What speed moves this data in time?").
- Fill in the fields the mode needs — Data volume with its Unit, Bandwidth with its Unit, and/or Duration with its Unit. Defaults are 500 GB, 1 Gbit/s and 8 hours.
- Optional: tick Apply an efficiency assumption and enter Efficiency as a percentage of bandwidth usable (default 90).
- In transfer-time and required-bandwidth modes, the Download presets load common sizes: DVD image (4.7 GB), Game (50 GB), CD image (700 MB) and Backup (1 TB).
- Read the result, the formula and, in transfer-time mode, the comparison table. Reset restores the defaults.
- Export with CSV, JSON, Copy all or Print. The export lists the mode, inputs, theoretical and adjusted results in base units (seconds, bits, bit/s), the comparison table and the assumptions.
Understanding the results
| Result | Meaning | What to look for |
|---|---|---|
| Main result | Theoretical value, or adjusted value when efficiency is applied | The caption says which: "Theoretical, at the full bandwidth" or "At 90% efficiency (assumption)" |
| Theoretical | Result at 100% of the line rate | A lower bound for time, an upper bound for volume |
| Adjusted (x%) / With x% efficiency | Result with your efficiency assumption | Only as good as the percentage you entered |
| Seconds note (time mode) | Exact duration in seconds | Use it for scripts and spreadsheets |
| IEC note (volume mode) | Same volume in TiB/GiB | Compare with OS-reported sizes |
| Byte-rate note (bandwidth mode) | Required speed in MB/s | Compare with tools that show bytes per second |
| Formula | The calculation in bits and seconds | Check unit choices here |
| Same transfer at common speeds | Your volume at six standard link speeds | Quick what-if for upgrades |
Example: sizing a link for a 1 TB nightly backup
A site produces a 1 TB backup that must reach the data center within an 8-hour window. Mode Required bandwidth, data volume 1 TB, duration 8 hours:
Theoretical minimum 277.778 Mbit/s (34.722 MB/s)
With 90% efficiency 308.642 Mbit/s (38.58 MB/s)
bandwidth = volume ÷ (time × efficiency)
= 8 000 000 000 000 bit ÷ (28 800 s × 90%)A 300 Mbit/s link is not enough once you allow 10% overhead; plan for more, plus growth. Cross-check in Transfer time mode: 500 GB over 1 Gbit/s takes 1 h 6 min 40 s in theory and 1 h 14 min 4 s at 90%. The comparison table for those 500 GB shows, theoretical and adjusted:
| Speed | Theoretical | At 90% |
|---|---|---|
| 10 Mbit/s | 4 d 15 h 6 min | 5 d 3 h 27 min |
| 100 Mbit/s | 11 h 6 min 40 s | 12 h 20 min 44 s |
| 1 Gbit/s | 1 h 6 min 40 s | 1 h 14 min 4 s |
| 10 Gbit/s | 6 min 40 s | 7 min 24 s |
In Data volume mode, 1 Gbit/s for 8 hours moves 3.6 TB (3.274 TiB) in theory and 3.24 TB (2.947 TiB) at 90%.
Common use cases
- Backup and replication window planning.
- Estimating cloud migration or initial seeding times before choosing between network transfer and shipping disks.
- Checking whether a monthly transfer cap is enough for a given average rate.
- Explaining download times to users ("a 50 GB game on 100 Mbit/s takes about 67 minutes at best").
- Comparing link upgrade options with the common-speeds table.
Troubleshooting
"must be greater than zero"
Volume, bandwidth and duration need positive values. Check that the field the mode uses is filled in; hidden fields from other modes are ignored.
"Efficiency must be more than 0% and at most 100%"
Enter a percentage such as 90, not a factor such as 0.9 (which would mean 0.9%) and not more than 100.
The time is eight times too long or too short
You probably picked a byte-rate unit (MB/s) where you meant a bit-rate unit (Mbit/s), or the other way round. Check the formula line: bandwidth is shown in bit/s.
Real transfers are much slower than the adjusted value
Measure actual throughput, and check for a single TCP stream on a high-latency path, Wi-Fi, VPN encryption, disk read or write speed at either end, or server limits. Latency and jitter can be checked with the Network Jitter Test.
Common mistakes
- Confusing Mbit/s and MB/s. A factor of 8.
- Mixing GB and GiB. A 500 GiB volume is 7.4% larger than 500 GB.
- Planning to 100%. Leave headroom for overhead, retransmissions, growth and other traffic.
- Ignoring the slowest component. Storage, CPU (for compression or encryption) or the remote end may cap throughput below the link.
- Using an efficiency you have not measured. The calculator cannot verify it.
Limitations
- Throughput only: no latency, TCP window, packet loss, congestion or protocol modelling.
- Efficiency is your assumption and is applied as a single constant factor.
- Constant rate assumed for the whole duration; burst, shaping and time-of-day effects are not modelled.
- Days and weeks are fixed lengths; durations are displayed with at most three parts, so very long results drop the smallest unit.
- Byte-rate units stop at GB/s and GiB/s.
Security & privacy
All values stay in your browser; nothing about your volumes, links or windows is sent to a server. The page may send an anonymous usage counter (tool name and view or run, no inputs or results) unless your browser uses Global Privacy Control or Do Not Track. The calculator does not measure your connection; for that, the Internet Speed Test exchanges test data with the NetTools.tech server.
Related tools
- Bits & Bytes Explainer — bits versus bytes and prefix families. Guide: Bits and bytes guide.
- Data Storage Converter — convert volumes between GB, GiB and others. Guide: Data Storage Converter guide.
- Unit Converter — transfer-rate conversions.
- Internet Speed Test — measure your real throughput. Guide: Internet speed test guide.
- Network Jitter Test — latency variation that affects real-time traffic. Guide: Network jitter test guide.
- Category overview: Conversion & calculation tools.
Summary
The Bandwidth Calculator solves volume = bandwidth × time × efficiency for time, volume or required bandwidth, with exact unit conversion and a clear split between theoretical and assumed-efficiency results. It is a planning tool for throughput; latency, protocol behavior and slow endpoints are outside its model, so measure before you commit to a window.
Frequently asked questions
How long does it take to transfer 500 GB over 1 Gbit/s?
In theory 4,000 seconds, which is 1 h 6 min 40 s, because 500 GB is 4 × 10¹² bits and the link moves 10⁹ bits per second. With a 90% efficiency assumption the calculator shows 1 h 14 min 4 s.
What is a realistic efficiency?
It depends on the protocol and the path. TCP over a clean wired Ethernet path typically delivers roughly 90–95% of the line rate, while VPNs, Wi-Fi and long-distance links can be much lower, so measure your own throughput where it matters.
How do I size a link for nightly backups?
Use the Required bandwidth mode: enter the backup size and the time window, and optionally an efficiency. Then add headroom for data growth and for other traffic sharing the link.
Does the calculator account for latency?
No. It calculates throughput only. High latency can limit a single TCP connection below the line rate, which parallel streams or TCP window tuning may be needed to overcome.
Mbit/s or MB/s?
ISPs and switches advertise megabits per second, while browsers and download managers usually show megabytes per second. Divide Mbit/s by 8 for MB/s, so 100 Mbit/s is at most 12.5 MB/s; the calculator accepts both unit families.
Why is my real download slower than the estimate?
The theoretical time assumes the full line speed is available all the time. TCP/IP and TLS overhead, Wi-Fi, other devices, server-side limits and congestion all reduce it, so use the efficiency option for a rough allowance or measure your throughput first.