Data Transfer Time Calculator

Estimate how long a file or backup takes to transfer from its size and the connection speed, accounting for the 8-bits-per-byte conversion.

This data transfer time calculator is for developers, system administrators, and anyone moving large files who wants to know how long it will take before they start. It is handy for planning backups and restores, estimating cloud uploads and downloads, sizing migration windows, and sanity-checking whether a connection is fast enough for the job. Enter a file size and a connection speed and it returns the transfer time in seconds, minutes, and hours, with the tricky bits-versus-bytes conversion handled for you.

The catch with transfer times is that file sizes are quoted in bytes (megabytes, gigabytes) while connection speeds are quoted in bits per second (megabits per second). There are 8 bits in a byte, so a file's size in megabits is eight times its size in megabytes. The calculator converts your file size to megabits, then divides by the connection speed in megabits per second to get the time in seconds, and also shows that in minutes and hours. It uses the common decimal convention where one gigabyte is 1,000 megabytes, matching how internet speeds and storage are usually advertised.

Suppose you upload a 1 gigabyte file over a 100 megabit per second connection. One gigabyte is 1,000 megabytes, which is 8,000 megabits. Divide 8,000 by 100 and you get 80 seconds, or about 1.3 minutes, in the best case. A 500 megabyte file over a slower 50 megabit per second link works out the same way: 500 megabytes is 4,000 megabits, divided by 50 gives 80 seconds again. Notice how halving both the size and the speed leaves the time unchanged - time depends on the ratio of the two.

Bits, bytes, and the math are the same everywhere, but advertised internet speeds and their real-world delivery vary widely by country and provider. Some markets quote speeds in megabits per second, others promote gigabit fibre, and actual throughput often falls short of the headline figure because of contention and distance. There is also a labelling subtlety: storage and network marketing use decimal units (1 gigabyte = 1,000 megabytes), while operating systems sometimes report binary units (1 gibibyte = 1,024 mebibytes), which makes measured sizes look slightly different. This calculator uses the decimal convention.

• Confusing megabits with megabytes. Speeds are in megabits per second and sizes in megabytes; forgetting the factor of 8 makes the estimate eight times wrong.
• Expecting to hit the advertised speed. Real transfers run slower because of protocol overhead, latency, network congestion, and disk read or write limits.
• Ignoring the slowest link in the chain. The transfer is limited by whichever is slower - your connection, the server, or the storage device.
• Mixing decimal and binary units. A file shown as some number of gibibytes by the operating system is slightly larger in megabytes than the round decimal figure.
• Forgetting overhead on many small files, where per-file delays can dwarf the raw transfer time of the data itself.

When you are planning a maintenance or migration window, treat the calculated time as a best case and add generous margin. Real throughput is commonly a good deal lower than the line speed, especially over long distances or busy networks, and transferring many small files is far slower than one large file of the same total size. Test with a representative sample before committing to a schedule, and where possible run large transfers during off-peak hours to get closer to the theoretical figure.

• Data-rate units - Reference (retrieved 2026-06-11)