How Long to Download 1 GB at 25 Mbps

1 GB at 25 Mbps takes 5 minutes 20 seconds

A 1 GB file takes 320 seconds at 25 Mbps, which is 5 minutes 20 seconds. The route is short. One gigabyte is 1,000 megabytes, one byte is 8 bits, so the file is 1,000 x 8 = 8,000 megabits. Divide by the 25 megabits the line carries each second and you get 320.

In bytes the same link moves 25 / 8 = 3.125 MB per second. That is the number a browser, Steam or the Windows download shelf will show, and it is why a 25 Mbps plan never displays 25 in a download window. At 3.125 MB/s a 5 MB photo lands in 1.6 seconds, a 100 MB app update in 32 seconds, and this gigabyte in 320.

That last row is worth keeping in mind when a plan is sold by speed and capped by volume. A 25 Mbps line left at full rate for an hour moves 11.25 GB, so a 1.2 TB monthly cap allows about 106 hours of saturated downloading. Nobody saturates a line for 106 hours, which is why caps rarely bind at this speed.

Megabits and megabytes: why the factor is 8

Every wrong answer to this question comes from one letter. Mbps is megabits per second, the unit on the plan, the router page, the speed test and the FCC label. MB/s is megabytes per second, the unit on a download progress bar. The byte is 8 bits, so the megabyte figure is always the megabit figure divided by 8.

Skip the division and the arithmetic looks like 1,000 MB / 25 = 40 seconds. The right answer is 320 seconds, eight times longer. This is not a rounding difference. It is the difference between a download that finishes before the kettle boils and one that runs through a coffee break.

Both prefixes are decimal here. The NIST table of SI prefixes defines mega as 10 to the sixth, so 25 Mbps is 25,000,000 bits per second and 3.125 MB/s is 3,125,000 bytes per second. The binary prefixes, kibi, mebi and gibi, are a separate family built on powers of 1,024, and they are covered below because Windows still uses them under the old names.

A practical check: if the number in your download window is roughly one eighth of the number on your bill, everything is working as intended. A 25 Mbps plan that shows 3.0 to 3.1 MB/s is healthy. One that shows 0.4 MB/s is not, and the cause is usually Wi-Fi rather than the line itself.

The same gigabyte at 10, 50, 100, 200 and 500 Mbps

Download time for a fixed file scales inversely with speed, so the 320 seconds at 25 Mbps halves at 50 Mbps and doubles at 12.5 Mbps. The table below uses the decimal gigabyte, 8,000 megabits of payload, and assumes the line runs at its rated speed with no overhead.

Two features of that table matter more than the individual rows. The first is that the gains flatten in usefulness rather than in mathematics: dropping from 5:20 to 2:40 saves a coffee, and dropping from 40 seconds to 16 seconds saves less time than the walk to the kitchen. The second is that at high speeds the file is no longer the bottleneck. A server that uploads at 100 Mbps cannot fill a 500 Mbps line, and a 1 GB file from a congested mirror often arrives at the same 20 MB/s on both plans.

A useful rule for planning: past about 100 Mbps, download time depends more on where the file is hosted than on what you pay for. Below 50 Mbps, the line is almost always the limiting factor, and the arithmetic above is a good forecast.

Where the missing 10 percent goes

The 320 second figure assumes every bit the line carries is file payload. Real transfers lose a slice to things that are not your file. Transmission control protocol headers, acknowledgements, TLS records and retransmissions take a few percent. Wi-Fi adds its own framing, and a weak signal causes retries that look like a slower line. The server on the other end may throttle you, and a busy content delivery node serves a fraction of its capacity.

The common planning allowance is 10 percent, which turns 320 seconds into 320 / 0.9 = 355.6 seconds, or 5 minutes 56 seconds. That is the number to quote when someone asks how long a gigabyte takes, because it is the one that tends to be right on a Tuesday evening.

The penalty can be worse than 10 percent in specific conditions. A 2.4 GHz Wi-Fi link in a crowded building can deliver half the plan. A VPN adds encryption and an extra hop. A store server during a launch window may serve 3 MB/s to everyone regardless of their line. In those cases the arithmetic is still correct, but the speed variable is not 25; it is whatever the slowest link in the chain delivers.

There is one overhead that does not apply: the 8 bits per byte conversion is not overhead, it is unit conversion. Keep the two ideas apart. Overhead is a fraction of the line you never see; the factor of 8 is the definition of the byte.

Decimal GB, rounded GB and the binary GiB

A gigabyte is 1,000 megabytes in the decimal system that storage makers, mobile carriers and data caps use. It is 1,024 megabytes in the rounded system many people carry in their heads. It is 1,073.741824 megabytes in the binary system Windows labels as GB, which is properly called a gibibyte, GiB.

The three versions produce three answers on a 25 Mbps line. Decimal: 8,000 megabits, 320 seconds, 5 min 20 s. Rounded: 8,192 megabits, 327.7 seconds, 5 min 28 s. Binary GiB: 8,589.93 megabits, 343.6 seconds, 5 min 44 s. The file is identical in all three cases; only the name of the unit changes.

Which one should you trust for planning? The decimal one, because that is how the download server counts the file, how your data cap counts the transfer and how the store listing describes the download. The GiB figure explains why a file described as 1 GB shows as 0.93 GB in a Windows properties dialog, and why a 1 TB drive formats to about 931 GB. Both statements are true in their own unit system.

The gap between decimal and binary is 7.4 percent, which is larger than the 10 percent overhead allowance in the other direction. That is why the two corrections do not cancel: 320 seconds becomes 343.6 with binary units, and 355.6 with overhead, and applying both gives 381.8 seconds, or 6 min 22 s.

A movie, a game update and a 20 GB backup

Worked example: a 4 GB game update on a 25 Mbps line. Four gigabytes is 4,000 MB, which is 32,000 megabits. Divide by 25 and the answer is 1,280 seconds, or 21 minutes 20 seconds. Add the 10 percent allowance and it becomes 1,422 seconds, about 23 minutes 42 seconds. That is close to the 25 minute mark people report for a mid sized patch on this kind of connection.

Worked example: a 20 GB photo backup. Twenty gigabytes is 20,000 MB and 160,000 megabits. At 25 Mbps that is 6,400 seconds, which is 106 minutes 40 seconds, or 1 hour 46 minutes 40 seconds. With overhead it stretches to 7,111 seconds, about 1 hour 58 minutes. Run it overnight rather than watching it.

The pattern is linear, which makes mental estimates easy. Double the file and you double the time; double the speed and you halve it. A 1 GB movie at 25 Mbps is 5:20, so a 2 GB movie is 10:40 and a 500 MB episode is 2:40. The only trap is mixing units halfway through, such as dividing a gigabyte count by a megabit speed without the factor of 8.

Streaming is a different calculation. A video player does not download the whole file before starting, it buffers a few seconds ahead, so what matters is whether the bitrate fits inside 25 Mbps. A 1080p stream at 5 to 8 Mbps leaves plenty of room, and two of them still fit.

Is 25 Mbps enough, and what the FCC benchmark says now

For most of the 2010s, 25 Mbps down and 3 Mbps up was the line the FCC used to define fixed broadband. That changed in March 2024, when the commission raised the benchmark to 100 Mbps down and 20 Mbps up, a fourfold increase on the download side and roughly seven times on the upload side. The same order set a long term goal of 1 Gbps down and 500 Mbps up.

So a 25 Mbps connection is now below the federal benchmark for fixed broadband, even though it was the definition of broadband for nine years. That does not make it useless. What it means is that the plan sits in the same tier as entry level DSL and fixed wireless rather than in the tier the government now treats as adequate for a household.

In practice 25 Mbps handles one 4K stream at about 15 Mbps with room to spare, or two or three 1080p streams at 5 to 8 Mbps each. It handles video calls, browsing and music at the same time. It struggles when a console downloads a 60 GB update while someone else is on a call, because the download will consume the whole line unless the router is set to prioritise.

Upload is the other half of the story. On a 25/3 plan the upload is 3 Mbps, which is 0.375 MB/s: a 1 GB file sent to cloud storage takes 2,667 seconds, or about 44 minutes. That asymmetry is the reason a 25 Mbps line feels fast for watching and slow for backing up, and it is the part of the 2024 benchmark change that matters most for anyone working from home.