Data Transfer Time Calculator

Type MB, Mbps, and efficiency. 500, 1000 and 80 give 5.00 s. 100, 100 and 100 give 8.00 s. 10, 10 and 50 give 16.00 s. Transfer time, not iperf.

This is (MB × 8) / (Mbps × eff/100). MB as megabits, not 1024. A backup window sits on backup window.

Input data

This field is always in MB. For large volumes, convert first (1 GB = 1024 MB; 1 TB = 1024 GB) or use the GB/TB presets below — typing millions of MB by hand is easy to get wrong.

Quick examples:

Results

Enter data and click Calculate.

For GB/TB-scale backups and migrations, convert to MB carefully or use the presets — huge hand-typed MB values make the estimate unreliable.

How it works

Data Transfer Time Calculator in this calculator divides megabits by effective speed. 500 MB, 1000 Mbps and 80% give 5.00 s. 100 MB, 100 Mbps and 100% give 8.00 s. 10 MB, 10 Mbps and 50% give 16.00 s. Formula: (MB × 8) / (Mbps × eff/100). Transfer time, not iperf.

Fields: data-size, data-speed, data-efficiency-pct. 500 × 8 = 4000 megabits. 1000 × 0.8 = 800. 4000 / 800 = 5. 100 × 8 / 100 = 8. 10 × 8 / (10 × 0.5) = 16. MB here does not go through 1024.

5.00 s does not come from iperf3. 8.00 s is not a WAN measurement. 16.00 s does not know TCP. You type three numbers. The calculator does not probe a link.

Backup window next door divides GB by pace. File download time takes a file and a unit. Here 500 MB and 80% stay 5.00 s, transfer time alone.

Type 500, 1000 and 80, then Calculate. The result is 5.00 s. A comma in 80,5 works. Zero Mbps does not divide. This is not live throughput.

500, 1000 and 80 give 5.00 s. 100, 100 and 100 give 8.00 s. 10, 10 and 50 give 16.00 s. Another efficiency at 500 changes 5.00 s.

Formula

seconds = (MB × 8) / (Mbps × eff/100). MB as megabits, not 1024. Transfer time, not iperf.

How to use

  1. Type 500 MB, 1000 Mbps, and efficiency 80.
  2. Click Calculate. The result is 5.00 s.
  3. 100 MB, 100 Mbps and 100% give 8.00 s. 10, 10 and 50% give 16.00 s.
  4. Transfer time, not iperf.
  5. A GB window sits on backup window.

500 MB, 1000 Mbps and 80% = 5.00 s

Transfer time from MB and Mbps. 500, 1000 and 80 give 5.00 s. This is not iperf.

Data
Field data-size in MB. 500 at 1000 and 80% leaves 5.00 s.
Transfer
MB × 8 / effective Mbps. 10 MB, 10 and 50% give 16.00 s.
Calculator
Seconds from the formula. 100 MB and 100 Mbps leave 8.00 s. Not a probe.

Examples

Example 1

  • 500 MB
  • 1000 Mbps
  • efficiency 80%

5.00 s

How long at 500 MB, 1000 Mbps and 80%? 5.00 s. Transfer time, not iperf.

Example 2

  • 100 MB
  • 100 Mbps
  • efficiency 100%

8.00 s

What about 100 MB, 100 Mbps and 100%? 8.00 s.

Example 3

  • 10 MB
  • 10 Mbps
  • efficiency 50%

16.00 s

What about 10 MB, 10 Mbps and 50%? 16.00 s.

Related calculators

File download time

File Download Time Calculator: size, unit, speed, and Mbps.

Use calculator →

Backup window

Backup window: GB and throughput.

Use calculator →

IOPS & Disk Throughput

IOPS and disk throughput: ms, block KB, and parallelism.

Use calculator →

RAID Capacity

RAID Capacity Calculator: disk count, size, and level.

Use calculator →

Cost Per Request

Cost Per Request Calculator: a price per million and a request count.

Use calculator →

All IT calculators

Common questions

What about 500 MB, 1000 Mbps and 80%?

5.00 s. (500 × 8) / (1000 × 0.8). Transfer time, not iperf.

What about 100 MB, 100 Mbps and 100%?

8.00 s. 800 / 100.

What about 10 MB, 10 Mbps and 50%?

16.00 s. 80 / 5.

Is this iperf or a link measurement?

No. Three typed fields. No TCP and no retransmits from the network.

Does 500 MB go through 1024?

No. The formula is MB × 8 as megabits. 1024 stays outside this calculator.

What does efficiency 80 do?

It scales Mbps. 1000 × 0.8 = 800, then 4000 / 800 = 5.00 s.

Does a comma in 80,5 work?

Yes. 80,5 at 500 and 1000 gives a different time than 80.

Where do I time a backup window?

On backup window. Here 5.00 s from 500 MB stays.

Does zero Mbps count?

No. Speed must be positive. This is not an empty link from a monitor.

Knowledge sources

The calculator counts bits, bytes or throughput from your numbers. Below are SI and bit definitions (NIST).

Page updated in 2026.

Scale: volume × throughput

Transfer time grows linearly with data volume and shrinks with effective throughput. This calculator takes size (MB), speed (Mbps), and an optional efficiency % — useful for backups, replication, and migrations where a nominal link is never 100% “clean.”

Backup and maintenance windows

If the nightly window is 4 h and a 70% efficiency estimate says 5 h, you will miss it — tighten scope, buy bandwidth, add parallel paths, or move off-peak. The same logic applies to migration maintenance windows.

Link variability and efficiency

  • The result is an estimate, not an SLA — bandwidth swings stretch real time.
  • WAN / VPN links usually show lower efficiency than in-DC LAN.
  • Long transfers can slow during peak hours — schedule large jobs off-peak.

Backup, sync, migrations

  • Full backup / initial sync — largest volume; plan with 70–85% efficiency headroom.
  • Incremental sync — much smaller delta; the same link often suffices.
  • DC↔DC migration — account for latency and a shared uplink with production.

Examples

  • 1 TB (≈1,048,576 MB) @ 100 Mbps, 100% eff. → about 23.3 h; at 80% eff. → about 29 h.
  • 500 MB @ 1 Gbps, 80% eff. → effective 800 Mbps, about 5 s.
  • Initial 200 GB vs incremental 8 GB on the same 100 Mbps link — full sync takes hours; incremental often minutes.