What does this calculator do?
This is the inverse of a transfer-time question: you know how much data has to move and how long you have, and you need the rate that makes it fit. That question comes up when sizing a replication link, a nightly backup path or a migration window. The calculator reports two rates and keeps them apart. The payload rate is the raw data divided by the time. The nominal link rate is that payload rate divided by the efficiency factor — the capacity you actually have to provision so that the payload still fits once overhead is paid. Units follow the standards exactly: kB, MB, GB and TB are powers of ten (1 GB = 10⁹ bytes) while KiB, MiB, GiB and TiB are powers of two (1 GiB = 2³⁰ bytes). The two ladders are never mixed, so "1 GB = 1024 MB" is not treated as a universal rule.
Formula
Divide the total bits by the seconds available, then gross the result up for overhead.
totalBits = size × unitFactor × 8 payloadRate = totalBits ÷ seconds nominalRate = payloadRate ÷ (efficiency ÷ 100)
How to use it
Enter the data size with its unit, then the length of the window in seconds, minutes, hours or days. Set efficiency to the share of the link you expect to actually use for payload — leaving it at 100 gives the theoretical minimum, which will be too optimistic for a real circuit. Provision against the nominal rate, and remember that if the link carries anything else during the window you need capacity for that too.
Worked example
500 GB inside an 8-hour window: 500 × 10⁹ bytes is 4 × 10¹² bits, and 8 hours is 28,800 seconds, so the payload rate is about 138.8889 Mbps — roughly 17.3611 MB/s. At 100% efficiency that is also the nominal rate, about 0.1389 Gbps. Assume 80% efficiency instead and you must provision about 173.6111 Mbps.
Frequently asked questions
Why are there two rates in the result?
The payload rate is what your data needs. The nominal rate is what the link must be rated for once protocol overhead, retransmissions and other traffic take their share. Ordering a circuit at the payload rate leaves no margin at all.
What efficiency should I assume?
There is no universal number. A clean local wired path often sustains 90–95%; a long-distance or shared WAN link with encryption may deliver 50–80%. Measure your own path if the window is tight.
Does a faster link always shorten the window proportionally?
Not necessarily. On high-latency paths a single TCP stream can be limited by the receive window rather than by bandwidth — see the Bandwidth-Delay Product Calculator — and the storage at either end can become the limit before the network does.
Sources
- NIST — Prefixes for binary multiples (IEC 80000-13): kibi/mebi/gibi are powers of 1024, while kilo/mega/giga are powers of 1000. This is why Mbit/s, MB/s and MiB/s are never mixed here.
- BIPM — The International System of Units (SI Brochure): decimal prefixes (k = 10³, M = 10⁶, G = 10⁹) and the second, the basis of every data-rate and transfer-time conversion.
- RFC 7323 — TCP Extensions for High Performance: the bandwidth-delay product and why a link needs a window of that size to stay full.
- Reviewed: 2026-08-10
Related calculators
Last updated: 2026-08-10 · v1.0.0 · Report an error