How Long to Download 2 GB at 25 Mbps

2 GB at 25 Mbps is 640 seconds, or 10 minutes 40 seconds

Start with the unit change, because that is where most guesses go wrong. A gigabyte is 1,000 megabytes and a byte is 8 bits, so 2 GB is 2 x 1,000 = 2,000 MB, and 2,000 x 8 = 16,000 megabits. Divide by the 25 megabits the line carries each second: 16,000 / 25 = 640 seconds. That is 10 minutes 40 seconds, or 640 / 60 = 10.6667 minutes in decimal.

Now check it the other way. Twenty five megabits per second is 25 / 8 = 3.125 megabytes per second, and 640 x 3.125 = 2,000 MB, which is the file you started with. When both routes give the same answer, the arithmetic is sound.

Ten minutes forty is the clean figure, the one you get on a wired connection with nothing else running. Real transfers finish a little later, and the sections below put a number on each reason: protocol overhead, the way Windows counts file size, and anything else using the line at the same time.

Why the download bar reads 3.1 MB per second

The bar in a browser or a game launcher counts megabytes, while the internet plan is sold in megabits. Same line, two units, one factor of eight. A 25 Mbps connection tops out at 3.125 MB/s, so a bar showing 2.9 or 3.1 is working exactly as sold. A bar parked at 0.9 is closer to 7 Mbps, which is a different problem.

This mix-up causes more support calls than any other part of home networking. Someone buys 25 Mbps, runs a speed test that reports 24.8 Mbps, opens a game launcher that reports 3.1 MB/s, and concludes the provider shorted them. Both readings are correct. The speed test reports bits, the launcher reports bytes, and 3.1 x 8 = 24.8.

Watch the capital letter too. MB means megabytes and Mb means megabits, and a spec sheet that writes MB/s while meaning Mbps overstates the line by eight times. When a number looks too good for the plan you pay for, check the letter before you believe it.

The bar also averages the whole transfer, handshake included. The first two seconds of a connection run at 0.4 MB/s while the session opens and the disk starts writing, and that pulls the average down for a small file. On a 2 GB download the slow start costs a few seconds, not a few minutes, so the 640 second estimate still holds.

Overhead turns 10 minutes 40 into about 11 minutes

The 640 second figure assumes every bit on the wire is file data. In practice each packet carries a header, the two ends acknowledge what arrived, and other devices in the house talk to the router while your file moves. A wired connection usually loses 2 to 5 percent to this, and Wi-Fi at the far end of a house can lose 10 percent or more to retries.

Add 2 percent and 640 x 1.02 = 652.8 seconds, or 10 minutes 52.8 seconds. Add 5 percent and 640 x 1.05 = 672 seconds, which is 11 minutes 12 seconds. A weak Wi-Fi link at 10 percent gives 640 x 1.10 = 704 seconds, or 11 minutes 44 seconds. That is the whole spread between a wired desktop and a laptop two rooms from the router: about a minute on a 2 GB file.

Plan for 11 minutes. If the file has to be done by a deadline, start it on the wire, because Wi-Fi retries are unpredictable and a microwave or a neighbour's network can push the loss above 10 percent for a stretch.

If the file is 2 GiB, the clock shows 10 minutes 55

Windows lists file size in gibibytes, where 1 GiB is 1,024 MiB, while network speeds are quoted in decimal units. A file that Windows calls 2.00 GB is usually 2 GiB, which is larger than the 2 GB used above. Run the same chain: 2 x 1,024 = 2,048 MiB, 2,048 x 8 = 16,384 megabits, and 16,384 / 25 = 655.36 seconds, or 10 minutes 55.36 seconds.

That is 655.36 - 640 = 15.36 seconds more than the decimal figure, a gap of about 2.4 percent. Small enough that planning for 11 minutes covers both cases. The gap grows with the file: a 50 GiB game download is 51.2 GB, so the estimate drifts by more than a minute.

The same mismatch explains why a 2 TB external drive shows up as 1.81 TB in Windows. Drive makers sell decimal terabytes, the operating system counts binary ones, and 2,000 / 1,024 = 1.953 TiB before formatting takes its share. Nothing is missing from the drive, and nothing is missing from your download.

25 Mbps was the US broadband line until 2024

Twenty five megabits down is a meaningful number in American policy, not just on your bill. The FCC used 25 Mbps down and 3 Mbps up as its fixed broadband benchmark from 2015 through 2023, the line that decided whether an address counted as served. In 2024 the commission raised the benchmark to 100 Mbps down and 20 Mbps up, and its 2026 Section 706 report, released in August 2026, kept that 100/20 figure.

So a 25 Mbps line now runs at a quarter of the federal yardstick. That does not make it useless. It streams 1080p, handles video calls and downloads a 2 GB file in under eleven minutes. It is no longer the speed a regulator would call advanced, and it will struggle with two 4K streams at once.

For scale, the same 2 GB file on a 100 Mbps line takes 16,000 / 100 = 160 seconds, or 2 minutes 40 seconds, and 640 / 160 = 4, so the upgrade buys a four fold cut in waiting. On a 1 Gbps fiber line it takes 16,000 / 1,000 = 16 seconds, and at that point the server on the other end and the write speed of your drive become the limit.

What else is on the line: Netflix and YouTube bitrates

A download does not get the whole connection when someone in the house is watching something. Netflix publishes its own requirements: 3 Mbps for 720p, 5 Mbps for 1080p and 15 Mbps for 4K, per stream, on its recommended internet speeds page. YouTube lists 2.5 Mbps for 720p, 5 Mbps for 1080p, 20 Mbps for 4K and 0.7 Mbps for 360p on its system requirements page.

Those figures are floors for smooth playback, not the average a stream pulls. Still, they are the numbers the services stand behind, so they are the right ones to subtract. With one 1080p Netflix stream running, the download has 25 - 5 = 20 Mbps left, and 16,000 / 20 = 800 seconds, or 13 minutes 20 seconds. A 4K Netflix stream at 15 Mbps leaves 10 Mbps and pushes the file to 16,000 / 10 = 1,600 seconds, or 26 minutes 40 seconds.

YouTube in 4K is the harshest case, because it asks for 20 Mbps. That leaves 5 Mbps for everything else, and 16,000 / 5 = 3,200 seconds, or 53 minutes 20 seconds. On a 25 Mbps line, a 4K video and a 2 GB download do not fit together in any comfortable way.

Hotspot caps and throttling: the slow end of 25 Mbps

A phone hotspot is where this file size bites hardest, because 2 GB is often the whole high speed allowance rather than one download. On a 5 GB hotspot plan the file eats 2 / 5 = 40 percent of the month in eleven minutes. On a 2 GB plan it uses all of it.

After the cap, carriers commonly drop the hotspot to 128 kbps, which is 0.128 Mbps. The same file then needs 16,000 / 0.128 = 125,000 seconds, or 34 hours 43 minutes 20 seconds. That is not a typo and it is not a reason to try. Wait for Wi-Fi, or buy the file somewhere with a real connection.

Throttling mid download looks different from a slow line. The bar drops from 3.1 MB/s to 0.016 MB/s in a second and stays there while the connection still tests as fine, because the cap applies to the hotspot, not the phone's own data. If a download stalls at exactly the moment a plan limit should hit, check the carrier app before you reboot the router.

Below about 5 Mbps the arithmetic still works, it just stops being useful. A 2 GB file at 5 Mbps is 16,000 / 5 = 3,200 seconds, the same 53 minutes 20 seconds you get when a 4K video takes 20 Mbps of the line. At 1 Mbps it is 16,000 / 1 = 16,000 seconds, or 4 hours 26 minutes 40 seconds. Those are the numbers to quote when someone asks whether a hotel connection can handle a game patch tonight.