Start with bits and bytes
There are eight bits in one byte. Mbps means millions of bits per second; MB/s means millions of bytes per second. For decimal units, divide Mbps by eight to find ideal MB/s. A 100 Mbps connection therefore has an ideal rate of 12.5 MB/s before overhead or other limits.
Keep the unit beside each number. A value of 50 without a unit means very different things in a calculator. Some applications use binary MiB/s, adding another difference. Check the app’s label instead of assuming its number uses the same unit as your internet plan.
Divide file size by transfer speed
An ideal transfer time in seconds is file size in bits divided by speed in bits per second. For decimal GB and Mbps, a convenient formula is GB × 8,000 ÷ Mbps. This is arithmetic, not a measurement of your current connection.
A 10 GB file at a steady 100 Mbps takes 800 seconds in that ideal model, or 13 minutes 20 seconds. At 50 Mbps it takes 1,600 seconds, or 26 minutes 40 seconds. These examples assume the server keeps up and the connection is available throughout.
| Speed | Ideal time for 10 GB |
|---|---|
| 25 Mbps | 53 min 20 sec |
| 50 Mbps | 26 min 40 sec |
| 100 Mbps | 13 min 20 sec |
| 500 Mbps | 2 min 40 sec |
Make a planning allowance explicit
Real transfers may encounter protocol overhead, interruptions, server limits or other activity. Choose a visible efficiency assumption instead of quietly promising the ideal result. At an illustrative 85% efficiency, use 85 Mbps in place of 100 Mbps in the calculation.
That makes the 10 GB estimate about 15 minutes 41 seconds. The 85% figure is a planning setting, not a universal performance rule. If your transfer normally sustains only 40 Mbps, entering a 100 Mbps plan with a small allowance remains too optimistic. A measured sustained rate is a better input.
Find the slowest part of the route
The file passes through several limits: the server, your internet connection, your router, the link to the device and the device itself. A faster plan does not make a busy download server send faster. Moving nearer the router does not alter a provider’s upstream capacity.
The CRTC distinguishes downloads, which bring data to you, from uploads, which send data out. It also identifies home equipment, connected devices and outside conditions as performance factors. Use upload speed for a cloud backup and download speed for receiving a file.
Compare under useful conditions
For a surprisingly slow transfer, record the rate and its unit. Try a reputable speed test under representative conditions. A wired connection can help separate Wi-Fi limitations from the rest of the route, provided the cable, adapter and router support the expected speed.
Change one condition at a time. A test taken beside the router while other devices are idle is not directly comparable to yesterday’s distant-room download while someone uploaded a video. Note the conditions so that the comparison answers a specific question instead of producing another unexplained number.
Choose speed around a real task
Ask which waiting times matter. Reducing a weekly transfer from half an hour to fifteen minutes may be useful. A faster plan may offer little improvement for a task limited by its remote server. Compare your actual common tasks before paying for speed you cannot use.
Run a few file sizes and speeds through the calculator. The result sets an expectation rather than promising an arrival time. A download that needs verification, installation, extraction or processing may continue working after the network transfer finishes. Include that later work when planning when you can use the file.
Sources & further reading
CRTC — Internet performance and reliability ↗CIRA — Internet speed explained ↗This guide is based on the sources linked above, with original explanations and examples. Software interfaces and service features can change. A documentation-based guide is not a hands-on product review. Read our editorial policy or report a correction.