About data transfer time
Data transfer time is how long it takes to move a file across a network at a given bandwidth. The data transfer time calculator answers the everyday question "how long will this download or upload take?" by combining the file size, your connection speed, and a real-world efficiency factor.
The core arithmetic is a single division: size divided by speed equals time. The catch that throws most people off is units. Internet plans are sold in megabits per second (Mbps, lowercase b), but files are stored in megabytes (MB, uppercase B), and one byte is eight bits. A file must be multiplied by eight to convert it to bits before dividing by a bitrate, otherwise the answer is wrong by a factor of eight.
Raw bandwidth also overstates real performance. TCP/IP overhead, network latency, congestion, Wi-Fi interference, and the speed of the remote server all eat into the advertised rate, so actual throughput usually lands between 60 and 90 percent of the headline figure. The efficiency slider in this tool lets you model that loss instead of assuming a perfect link.
How the calculation works
The tool converts the file to bits, converts bandwidth to bits per second, applies the efficiency factor, and divides.
file_bits = file_size_bytes x 8 effective_bps = bandwidth_bps x efficiency time_seconds = file_bits / effective_bps Reminder: 1 byte = 8 bits, so MB x 8 = Mb
- file_size_bytes is the size of the file in KB, MB, GB, or TB.
- bandwidth_bps is your connection speed converted from Kbps, Mbps, or Gbps to bits per second.
- efficiency is the fraction of advertised speed you actually achieve, typically 0.6 to 0.9.
- time_seconds is the estimate, which the tool then expresses in seconds, minutes, hours, or days.
Worked example
You want to download a 10 GB game on a 100 Mbps connection, assuming 80 percent real-world efficiency.
- Convert size: 10 GB = 80,000 megabits (10 x 1,000 x 8, using decimal GB).
- Effective speed: 100 Mbps x 0.80 = 80 Mbps.
- Time: 80,000 / 80 = 1,000 seconds.
- Readable: 1,000 seconds is about 16.7 minutes.
Transfer time reference
Approximate real-world download times at 80 percent efficiency. Times scale linearly with file size and inversely with speed.
| File size | 25 Mbps | 100 Mbps | 1 Gbps |
|---|---|---|---|
| 100 MB | ~40 sec | ~10 sec | ~1 sec |
| 1 GB | ~6.7 min | ~100 sec | ~10 sec |
| 10 GB | ~67 min | ~17 min | ~100 sec |
| 50 GB | ~5.5 hr | ~83 min | ~8.3 min |
Common pitfalls
- Confusing bits and bytes. The single biggest error. A 100 Mbps line moves about 12.5 MB per second, not 100 MB. Always multiply file size by eight before dividing by a bitrate.
- Trusting the advertised speed. "Up to 100 Mbps" is a ceiling, not a guarantee. Use an efficiency factor to model the throughput you actually get.
- Ignoring asymmetric upload speeds. Home plans often upload far slower than they download, so cloud backups take much longer than the same-size download.
- Forgetting the slowest link wins. Your transfer is capped by the weakest point: a slow server, congested Wi-Fi, or an old USB port can all bottleneck a fast internet line.
- Mixing decimal and binary units. Drives advertise decimal GB (1,000 MB) while operating systems often show binary GiB (1,024 MiB). The small difference shifts long-transfer estimates by a few percent.
Frequently asked questions
Why does my download take longer than the file size divided by my speed suggests?
Two reasons. First, internet speeds are sold in megabits per second but files are measured in megabytes, and one byte is eight bits, so you must multiply the file size by eight before dividing. Second, real throughput is only about 60 to 90 percent of the advertised rate because of TCP overhead, latency, congestion, and the speed of the server you are downloading from. This calculator includes an efficiency slider to account for that gap.
What is the difference between megabits and megabytes?
A bit is the smallest unit of data and a byte is eight bits. Network bandwidth is quoted in bits per second, written with a lowercase b, as in 100 Mbps. File sizes are quoted in bytes, written with an uppercase B, as in 1 GB. To convert, divide a bitrate by eight to get bytes per second, or multiply a file size in bytes by eight to get bits. Mixing the two up is the most common reason transfer-time estimates are off by a factor of eight.
How long does it take to download a 1 GB file at 100 Mbps?
At the theoretical maximum, 1 gigabyte is 8,000 megabits, so 8,000 divided by 100 Mbps is 80 seconds. In the real world, applying a typical 80 percent efficiency, it takes about 100 seconds. Faster links scale linearly: the same file takes roughly 8 seconds at 1 Gbps theoretical, or about 10 seconds at 80 percent efficiency.
Does upload speed matter for transfer time?
Yes, when you are the one sending data. Many home connections are asymmetric, with upload speeds far lower than download speeds, so backing up a large file to cloud storage can take much longer than downloading the same file. Enter your upload bandwidth in the bandwidth field when estimating an upload, and remember the same efficiency losses from overhead and latency apply in both directions.
What efficiency percentage should I use?
A good default is 80 percent for a healthy wired or strong Wi-Fi connection over a short network path. Use 90 percent for fast, low-latency links such as a local gigabit transfer, and as low as 50 to 60 percent for congested networks, distant servers, mobile data, or weak Wi-Fi. The efficiency factor captures everything the raw formula ignores, so adjust it to match the real conditions you expect.