How long to download 20 GB at 100 Mbps

Twenty gigabytes at 100 Mbps is 1,600 seconds, or 26 minutes 40 seconds

The division, done once

Twenty gigabytes is 20,000 megabytes, and eight bits to a byte makes that 160,000 megabits. Divide by 100 Mbps and the answer is 1,600 seconds, which is 26 minutes 40 seconds. Every figure on this page comes out of that one division.

The byte view is easier to watch on a progress bar. One hundred megabits a second is 100 / 8 = 12.5 MB/s, and 20,000 / 12.5 = 1,600. At that pace a minute adds 750 MB, an hour adds 45 GB, and one gigabyte costs 80 seconds.

Six percent for packet headers and retransmission turns 1,600 into 1,696 seconds, or 28 minutes 16 seconds. Ten percent gives 1,760 seconds, or 29 minutes 20 seconds. A client that holds 12.5 MB/s is not paying that tax, which is why the number on screen and the clock on the wall rarely agree.

One hundred megabits is the federal broadband line, not a fast tier

What the 2024 benchmark does to the arithmetic

In March 2024 the FCC raised its fixed broadband benchmark from 25/3 Mbps to 100/20 Mbps, and set a long term goal of 1 Gbps down and 500 Mbps up. The order is FCC 24-27, the 2024 Section 706 report. A 100 Mbps plan is that line exactly, with nothing to spare.

The upload half is the part that surprises people. At 20 Mbps, the same 20 GB sent the other way takes 160,000 / 20 = 8,000 seconds, which is 2 hours 13 minutes 20 seconds. Five times the wait for the same file, on the connection the government calls adequate.

Plans above this line are common, and the extra money buys real time: 200 Mbps finishes the same file in 13 minutes 20 seconds. At 100 Mbps you are at the minimum standard for a household in 2026, not at the fast end of it.

One 4K stream takes a quarter of the line and adds 8 minutes 53 seconds

The FCC's own activity numbers, applied

The FCC's Broadband Speed Guide lists 25 Mbps for Ultra HD 4K video, 5 to 8 Mbps for high definition, 6 Mbps for an HD video conference, and 4 Mbps for online multiplayer. Those are minimums for one activity at a time.

Take one 4K stream at 25 Mbps out of 100 and 75 Mbps remain. The file then needs 160,000 / 75 = 2,133 seconds, or 35 minutes 33 seconds, which is 8 minutes 53 seconds longer than an empty line. A high definition stream at 8 Mbps leaves 92 and costs 2 minutes 19 seconds. The full set is in the table.

Two 4K streams double the clock. One television in another room is survivable, two televisions plus a download is a scheduling problem.

Three devices at once leave 61 megabits and push the file to 43:43

A queue, not a fair split

A house with a 4K television at 25 Mbps, a high definition stream at 8 Mbps, and a video call at 6 Mbps is asking for 39 Mbps. The file gets the remaining 61, and 160,000 / 61 = 2,623 seconds, or 43 minutes 43 seconds. Nobody chose that outcome, and every device still looks fine.

The FCC's Home Network Tips says several wireless devices on one network affect performance, and that a cable gives the highest speed. It does not say how the leftover bandwidth gets divided. The router hands it out in whatever order packets arrive, so the file and the television share the loss.

Two moves help. Run the transfer after 11 pm, when peak household use is over, or cap the download client at 70 Mbps so the house keeps 30. A capped transfer takes 38:06 and the evening stays usable.

The bar covers 225 percent of the file in an hour

Checkpoints instead of a remaining time estimate

An hour is 3,600 seconds, and 3,600 / 1,600 = 2.25. The bar crosses the file twice and a quarter every hour, so an eight hour night would move 18 copies at this rate. The download is not an evening event. It is a coffee break plus a phone call.

Quarter marks land at 400, 800, 1,200 and 1,600 seconds. Start at 8:00 pm and the file is a quarter done at 8:06:40, half at 8:13:20, three quarters at 8:20:00, and finished at 8:26:40.

Use those marks rather than the remaining time display. Browsers compute that estimate from the last few seconds, so a brief stall makes it jump by ten minutes. A byte count at the start of a minute and again at the end is more trustworthy.

Fifty, one hundred, two hundred: the clock halves at every step

What the upgrade buys

Doubling the rate halves the clock. On a 50 Mbps line the same 20 GB takes 3,200 seconds, or 53 minutes 20 seconds. Moving to 100 Mbps saves 26 minutes 40 seconds. Moving again to 200 Mbps saves another 13 minutes 20 seconds.

The savings shrink as the line gets faster, and that is the point. Going from 100 to 200 Mbps turns half an hour into a quarter of an hour, which matters only if you do it often. Above 200 Mbps the disk and the server usually decide the clock.

Wi-Fi hands you 60 to 80 percent of the wire

Where the 26 minutes turns into 44

A laptop on Wi-Fi rarely sees the full 100 Mbps. A 5 GHz link in the same room as the router typically carries 60 to 80 percent of the wired rate. One wall drops it to 40 to 60 percent, and 2.4 GHz, which reaches further, often lands between 25 and 40 percent. Those are planning ranges, not a measurement of your house, so check the speed on the device before blaming the provider.

A cable removes the whole question and costs less than a month of service. Where a cable is not practical, 5 GHz near the router beats 2.4 GHz at the far end of the house. The radio, not the plan, is the narrow part.

Half an hour of download still needs 20 GB of free disk

The parts of the job that are not the network

Twenty gigabytes has to land somewhere. A hard drive writing at 120 MB/s needs 167 seconds, and a solid state drive at 500 MB/s needs 40, so storage is not the limit. Free space is. A machine with 12 GB left fails at the 60 percent mark, and some installers unpack the archive beside it, which doubles the requirement.

Data allowances matter more than they used to. Twenty gigabytes is one sixtieth of a 1.2 TB monthly cap, and a household that does this once a week spends 80 GB a month on it. That is comfortable on a cable plan and expensive on a metered hotspot.

The last step is the checksum. A file assembled from a transfer that dropped and resumed can be corrupt if one segment came from a different build, and finding out after 26 minutes of downloading and ten minutes of installing is a bad trade. The published hash takes under a minute to check.

A 20 GB download at 100 Mbps is a short errand. Start it, watch the quarter marks, and let the rest of the house keep its bandwidth.