Rex says
The fast lane for the math you almost remember from school. Type the numbers, get the answer, move on with your day.
Try a scenario
Click to load — tweak from there.Inputs
Result
Estimated transfer time (minutes)
83.33
In seconds
5000.0
In hours
1.389
Theoretical time at rated speed (no overhead)
4000.0
Psst — share this and help Rex grow
One click, a permanent link with your numbers baked in.
How to use this
- 1Enter data size.
- 2Enter size unit.
- 3Enter link bandwidth.
- 4Enter bandwidth unit.
- 5Enter real-world efficiency (%).
- 6Read your estimated transfer time (minutes) on the right — it updates as you type.
- 7Hit Share to keep the scenario or send it to someone.
About this calculator
Transfer time calculations frequently go wrong because of a unit mismatch: bandwidth is quoted in bits per second (Mbps, Gbps) while file sizes are quoted in bytes (MB, GB), and the conversion factor is 8, not 1000 or 1024. This calculator takes a data size in your chosen unit, a link speed in your chosen unit, and an efficiency factor to account for real-world overhead — TCP/IP headers, protocol negotiation, and the fact that almost no real connection sustains its rated theoretical maximum — and returns the actual expected transfer time. A typical real-world efficiency factor is 70-85% of rated bandwidth for a well-tuned connection, dropping lower over long-distance or high-latency links due to TCP window limits, which is why this tool defaults to 80% rather than assuming the full advertised speed.
Worked example
Using the values the calculator loads with:
Inputs
- Data size: 500
- Size unit: GB
- Link bandwidth: 1
- Bandwidth unit: Gbps
- Real-world efficiency: 80 %
Results
- Estimated transfer time (minutes): 83.33
- In seconds: 5,000
- In hours: 1.389
- Theoretical time at rated speed (no overhead): 4,000
What each field means
Inputs
- Data size
- The data size used in the calculation. Starts at 500 so you have a working example on load.
- Size unit
- Pick the option that matches your situation — the maths changes per option. Choices: MB, GB, TB.
- Link bandwidth
- The link bandwidth used in the calculation. Starts at 1 so you have a working example on load.
- Bandwidth unit
- Pick the option that matches your situation — the maths changes per option. Choices: Mbps, Gbps.
- Real-world efficiency (%)
- The real-world efficiency used in the calculation, measured in %. Starts at 80 % so you have a working example on load. Accepted range: 1–100 %.
Results
- Estimated transfer time (minutes)
- Returned as a decimal number and shown as the headline result. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
- In seconds
- Returned as a decimal number. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
- In hours
- Returned as a decimal number. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
- Theoretical time at rated speed (no overhead)
- Returned as a decimal number. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
FAQ
Why is my actual transfer time always longer than advertised?
Advertised bandwidth is a link-layer ceiling, not a guaranteed throughput. TCP/IP overhead, packet retransmission, other traffic sharing the link, and TCP's slow-start ramp-up all cut into effective throughput, and long-distance links suffer further from bandwidth-delay-product limits unless window scaling is properly tuned. 70-85% of rated speed is realistic for a healthy local network; long-haul internet transfers often land lower.
Why does the calculator use 8 bits per byte and not divide by 1024?
Network bandwidth is universally quoted in bits per second using base-10 (1 Mbps = 1,000,000 bits/sec), while file sizes are usually quoted in bytes using base-2 conventions in some tools (1 GB = 2^30 bytes) and base-10 in others (1 GB = 10^9 bytes). This calculator uses base-10 throughout for consistency with how ISPs and cloud providers quote both bandwidth and storage.
How much faster is a physical drive shipment than network transfer for huge datasets?
Past a certain size, physically shipping drives ('sneakernet' or a service like AWS Snowball) beats network transfer on pure time — a 10Gbps link needs about 9 days to move 100TB even at 100% efficiency, while shipping drives overnight moves the same data in 1-2 days including shipping transit. The crossover typically sits around 20-50TB depending on your actual sustained bandwidth.
Accuracy and limitations
- Results are rounded for display; the underlying calculation keeps full precision.
- Very large or very small inputs may hit floating-point limits in the browser.
- Inputs outside the accepted range are clamped rather than rejected.
Related tools
File/Media Transfer Duration Estimator
Estimate upload or download time for a batch of files over your connection.
Bandwidth Needed for N Concurrent Users
Size your uplink for a target number of simultaneous users.
Cloud Egress Bandwidth Cost Calculator
Find out what shipping data out of the cloud actually costs you.
Cite this calculator
Writing about this topic? Grab a citation — every link helps keep these tools free.
RevenueLab. (2026). Data Transfer Time Calculator. Retrieved from https://www.revenuelab.fyi/toolbox/data-transfer-time-calculator
<p>Source: <a href="https://www.revenuelab.fyi/toolbox/data-transfer-time-calculator" target="_blank" rel="noopener">Data Transfer Time Calculator — RevenueLab</a> (2026).</p>
Source: [Data Transfer Time Calculator — RevenueLab](https://www.revenuelab.fyi/toolbox/data-transfer-time-calculator) (2026).