Bandwidth and duration
Network Transfer Time Calculator
Estimate how long a file, backup, or data set takes to transfer using exact bit and byte units. Compare the theoretical minimum with an explicit efficiency assumption or measured goodput; inputs and results stay in your browser.
Estimate the transfer
Enter the useful data amount and rate, then choose whether to apply an explicit planning assumption.
Load an example
Private by default. Calculations run locally in your browser. The site does not send or save calculator inputs.
Transfer estimate
Transfer duration
————
This is a steady-rate planning estimate. It does not test the network or simulate packets, latency, congestion, retransmissions, storage, CPU, or protocol behavior.
Normalized data
- Entered amount
—- Total bytes
—- Total bits
—- Unit definition
—
Nominal path
- Entered rate
—- Normalized bit rate
—- Normalized byte rate
—- Unit definition
—
Duration
- Theoretical minimum
—- Theoretical seconds
—- Primary estimate
—- Primary total seconds
—
Applied model
- Basis
—- Applied goodput
—- Difference
—- Nominal ratio
—
Auditable formula
Theoretical—
Estimate—
Model boundary
Calculation contract
Exact units and visible assumptions.
The calculator preserves the distinction between bits and bytes, decimal and binary prefixes, and mathematical minimums versus assumption-based estimates.
Normalize the data
The selected data amount is converted exactly to bits. A byte is eight bits, while decimal and IEC binary prefixes retain their different factors.
Normalize the rate
The nominal or measured rate is converted exactly to bits per second. Uppercase B remains distinct from lowercase bit.
Calculate the duration
Every duration is calculated as an exact ratio. Rounding happens only when the result is formatted for display.
Planning workflow
From link speed to a defensible estimate.
Start with the ideal lower bound, then add only an assumption or measurement you can explain in a backup plan, migration worksheet, or change record.
Select the exact units
Choose the unit shown by the source rather than silently converting GB to GiB or Gbit/s to GB/s.
Choose one estimate model
Use theoretical-only for the mathematical minimum, efficiency for an explicit planning assumption, or measured goodput for an observed application rate.
Record the boundary
Copy the normalized inputs, formula, duration, and model note together. The answer remains an estimate rather than a completion promise.
Worked minimum
1 TB at 1 Gbit/s
A decimal terabyte contains eight trillion bits. At one billion bits per second, the ideal transfer requires exactly 8,000 seconds.
- Data amount
1,000,000,000,000 B- Total data
8,000,000,000,000 bit- Nominal rate
1,000,000,000 bit/s- Formula
8×10¹² ÷ 10⁹- Total seconds
8,000 s- Theoretical minimum
2 h 13 min 20 s
Model comparison
1 GB at 1 Gbit/s
The ideal duration is eight seconds. An explicit 80% efficiency assumption and a measured goodput of 800 Mbit/s each produce a ten-second estimate, but they describe different evidence.
- Theoretical minimum
8 s- Nominal throughput
1 Gbit/s- Efficiency assumption
80%- Effective goodput
800 Mbit/s- Efficiency estimate
10 s- Measured-rate estimate
10 s at 800 Mbit/s
Unit reference
Small symbols, large differences.
Case and prefix system are part of the value. Select the unit literally shown by the link, operating system, appliance, or storage documentation.
Eight bits make one byte
1 B = 8 bit. A rate of 1 GB/s is eight times a rate of 1 Gbit/s.
Powers of 1,000
1 GB = 1,000,000,000 B. Network link rates such as Mbit/s and Gbit/s use decimal prefixes.
Powers of 1,024
1 GiB = 1,073,741,824 B. Binary byte units use KiB, MiB, GiB, TiB, and PiB.
Model boundary
Efficiency is an aggregate assumption.
Efficiency means useful application goodput divided by the entered nominal rate. It can summarize a planning assumption, but it does not identify which technical factor reduced throughput.
- Included
- Exact unit conversion
- Included
- Theoretical minimum
- Optional
- Explicit efficiency
- Optional
- Measured goodput
- Not simulated
- Protocols, RTT, loss, congestion
- Not simulated
- Storage, CPU, compression, caching
Operational uses
Estimate the window, then validate the system.
The result is most useful as a transparent first bound. Compare it with observed goodput and with the storage, host, protocol, and shared-link limits in the real path.
Check a backup window
Compare the theoretical minimum with the time available, then use measured goodput from a representative run for a more grounded estimate.
Size a data move
Document the source data amount, nominal path rate, selected model, and assumptions before scheduling a bulk migration or replication task.
Expose unit mistakes
Normalize reported values to bit/s and B/s to catch eightfold bit-versus-byte errors and decimal-versus-binary mismatches.
Evidence and related tools
Units and goodput with defined meanings.
NIST defines the decimal and IEC binary prefix systems. RFC 8238 distinguishes throughput and goodput terminology; this calculator uses goodput for useful application data delivered per second.
Common questions
Network transfer calculator behavior
What is the difference between Mbit/s and MB/s?
Mbit/s is millions of bits per second; MB/s is millions of bytes per second. Because one byte contains eight bits, 1 MB/s equals 8 Mbit/s.
What is the difference between GB and GiB?
GB is decimal: one billion bytes. GiB is binary: 1,073,741,824 bytes. The calculator keeps both definitions exact instead of treating their labels as interchangeable.
Why can a real transfer take longer than the theoretical minimum?
The ideal result assumes the full entered rate carries useful data continuously. Protocol behavior, contention, loss, endpoint limits, storage, CPU, and other factors can reduce sustained application goodput.
What should I enter for efficiency?
Use a percentage you can support with a planning standard or observation. The calculator deliberately supplies no universal default. When possible, use measured goodput from a representative transfer instead.
What is measured goodput?
It is the observed rate of useful application data delivered per second. This mode assumes that rate remains constant for the estimated transfer; it does not perform a live speed test.
Does the calculator model latency, TCP, packet loss, or protocol overhead?
No. Version 1 does not simulate RTT, handshakes, slow start, congestion, retransmissions, packet framing, MTU, or protocol headers. Efficiency may summarize an external assumption, but the tool does not calculate those factors.
Why can measured goodput be higher than the nominal rate?
The calculator preserves that input and displays a warning. Unit mismatch, compression, caching, aggregation, or different definitions of useful and transmitted data may explain it and should be investigated.
Does this calculator test my Internet or network speed?
No. It generates no traffic and measures no connection. It converts the size, rate, and optional assumption or measurement you provide into a deterministic duration estimate.