How Long to Download 1 GB at 10 Mbps

1 GB at 10 Mbps takes 13 minutes 20 seconds

A 1 GB file is 1,000 MB, and one byte holds 8 bits, so the file is 1,000 x 8 = 8,000 megabits. Divide 8,000 by the 10 Mbps your plan delivers and the answer is 800 seconds, which is 13 minutes 20 seconds.

The same speed in bytes is 10 / 8 = 1.25 MB per second. At that rate a 5 MB photo takes 4 seconds, a 100 MB app update takes 80 seconds, and this 1 GB file takes 800. Nothing else changes the arithmetic: a bigger file multiplies the time, a faster plan divides it.

Megabits are not megabytes

The lowercase b is the whole trap. Mbps means megabits per second, the unit every ISP, speed test and router box uses. MB/s means megabytes per second, the unit Steam, Windows Update and your browser's download tray use. One is 8 times the other.

So a 10 Mbps line moves 1.25 MB/s, not 10 MB/s. A browser showing 1.2 MB/s is describing a healthy 10 Mbps connection, not a broken one. If you divide 1,000 MB by 10 without converting, you get 100 seconds; the right answer is 800 seconds, eight times longer.

Strictly, the byte is 8 bits and the mega prefix is decimal in both cases, so 10 Mbps is 10,000,000 bits per second and 1.25 MB/s is 1,250,000 bytes per second. The NIST table of SI prefixes is the reference for the decimal side of that.

Both units turn up in the same house. The router status page reports the link in Mbps, a speed test reports Mbps, and the Windows Task Manager network tab also reports Mbps. Steam, the PlayStation store and the Chrome download shelf report MB/s. A 10 Mbps plan therefore reads about 1.2 MB/s where you watch a progress bar and about 10 where you test the line.

13 min 20 s, 13 min 39 s or 14 min 19 s: which gigabyte?

Three numbers circulate for this download, and all three come from different definitions of a gigabyte. The decimal one is the one to quote. With 1 GB = 1,000 MB the file is 8,000 megabits and takes 800 seconds.

The shortcut where 1 GB is rounded to 1,024 MB gives 8,192 megabits and 819.2 seconds, or 13 minutes 39 seconds. It is a mental estimate many people make, and it runs 0.6 percent longer than the decimal answer, so it is a fine middle guess.

Windows is the source of the third. The file properties dialog labels a binary gigabyte as GB, but it counts GiB: 1,073.7 MB, or 8,589.9 megabits. That file takes 859 seconds, 14 minutes 19 seconds. The file has not changed size; only the unit name has.

For planning, use the decimal figure. It is how download servers, data caps and store listings count a gigabyte, and it is the number the calculator above uses by default.

The same file at other speeds

Doubling the speed halves the time, so the gains look large at the slow end and thin at the top. Moving from 10 to 25 Mbps saves 8 minutes on this file; moving from 500 to 1,000 Mbps saves 4 seconds.

Scale the table up by file size. A 10 GB game on the same 10 Mbps line takes 8,000 seconds at the full rate, which is 2 hours 13 minutes, and about 2 hours 28 minutes at 90 percent. On a 100 Mbps line the same game takes 13 minutes 20 seconds. That is the difference a plan change buys.

Why the real download runs about 10 percent slower

TCP headers, acknowledgement packets, Wi-Fi retries and the server's own limits all take a bite. On a clean wired connection the loss usually runs 5 to 10 percent. On Wi-Fi in another room it is often 10 to 15 percent, and on a congested evening it can be worse, because cable and fixed wireless share capacity with the neighbors.

Use 90 percent as a working number: 800 / 0.9 = 888.9 seconds, or 14 minutes 49 seconds. At 95 percent the file takes 14 minutes 2 seconds; at 85 percent it takes 15 minutes 41 seconds. The spread between a good day and a bad one is about a minute and a half on this file. Each row below is the same formula run at that delivered speed, so entering 9.5 Mbps in the calculator above returns 14 minutes 2 seconds.

Two more things slow a download that the arithmetic cannot see: startup and distance. Every transfer opens with a round trip to resolve the address and set up the session, which costs 20 to 100 ms, and a server on another continent adds more. On a 13 minute download that is noise. On a 5 MB file it is the whole story.

A quick way to find your own overhead: run a speed test, then watch the rate in the download window for a large file. If the test says 10 Mbps and the window settles at 1.05 MB/s, you are getting 8.4 Mbps, or 84 percent of the plan. That ratio is stable on a given connection, so it is the number to feed the calculator.

What a 10 Mbps line is good for

Ten megabits down sits below the current federal benchmark. In 2024 the FCC raised the fixed broadband benchmark from 25/3 Mbps to 100 Mbps down and 20 Mbps up in its 2024 Section 706 report, so a 10 Mbps service is now counted as below broadband. That does not make it useless; it makes it a connection with a narrow job.

One 1080p stream needs about 5 Mbps, so a single video session fits with room to spare. Two of them plus a video call do not. A 4K stream wants 15 to 25 Mbps and will buffer on this line. Big transfers are the real pain: 1 GB is 13 minutes, 50 GB is about 11 hours, and a 500 GB backup runs for more than four days.

Where 10 Mbps still shows up: DSL at the edge of the service area, a phone hotspot on a weak signal, a throttled unlimited plan after the cap, and rural fixed wireless. Check the FCC broadband map for what is offered at your address before assuming 10 Mbps is the only option.

Household math matters more than one file. A 1080p stream, a video call and a phone backup running at the same time will saturate 10 Mbps and make all three stutter. The same household on a 100 Mbps line has ten times the room, which is the reason the federal benchmark moved.

Checking your own numbers

Run a speed test on a wired connection, not on Wi-Fi, and use the download figure in Mbps. Divide it by 8 to get MB/s, which is what your download window shows. If the test says 10 Mbps and the window says 1.2 MB/s, both are right.

Then check the file size unit. A 1 GB entry in a download list may mean 1,000,000,000 bytes or 1,073,741,824 bytes. Multiply by 8 and divide by your speed for the honest answer, or let the calculator above do it: set the size to 1, pick the unit, and set the speed to 10. The FCC broadband speed guide explains how advertised speeds are measured and how to test yours.

Every number in this article falls out of the same formula the widget uses, so if your result differs, one of the three inputs is different: file size, unit, or delivered speed. That is the whole model, and it is why a 10 Mbps line is predictable in a way a congested evening is not.

Two habits make a slow line bearable. Use a client that resumes, so a dropped connection does not restart a multi hour transfer from zero, and start large downloads overnight when the neighborhood node is quieter.