How Long to Download 1 GB at 100 Mbps

1 GB at 100 Mbps takes 1 minute 20 seconds

A decimal gigabyte is 1,000 megabytes, and each byte carries 8 bits, so a 1 GB file is 8,000 megabits of payload. A 100 Mbps line delivers 100 megabits every second, and 8,000 / 100 = 80 seconds, which is 1 minute 20 seconds.

That is exactly half the 160 seconds the same file needs at 50 Mbps and double the 40 seconds it needs at 200 Mbps. The line moves 12.5 MB in each second, so a browser download shelf shows about 12.4 to 12.5 MB/s on a healthy connection and never the number 100.

Eighty seconds is the floor, not a forecast. It assumes every bit on the line belongs to the file, which only happens on a quiet connection talking to a fast server. The gap between 1:20 and the clock in your window is the subject of the rest of this page, and at this speed the gap is usually set by the server or the Wi-Fi link rather than the plan.

100 Mbps is 12.5 megabytes per second, and the FCC benchmark

Internet plans are sold in megabits, while download windows, file managers and cloud sync clients report megabytes. One byte is 8 bits, so 100 Mbps / 8 = 12.5 MB/s. Skip that division and a 1,000 MB file looks like a 10 second download; the real figure is 80 seconds, eight times longer than the naive answer.

The number also has a regulatory meaning. In March 2024 the FCC raised the fixed broadband benchmark to 100 Mbps down and 20 Mbps up, replacing a 25/3 standard that had stood since 2015. A 100 Mbps plan now sits exactly on the line, which makes it the smallest connection the federal government still counts as broadband.

The prefixes are decimal by definition. NIST's table of SI prefixes puts mega at 10 to the sixth, so 100 Mbps is 100,000,000 bits and 12,500,000 bytes every second. Binary prefixes are a separate family: a mebibyte is 1,048,576 bytes and a gibibyte is 1,073,741,824 bytes, and Windows still prints those binary counts under the decimal names, which is why the GiB figure appears further down.

The same gigabyte at 25, 50, 200, 500 and 1,000 Mbps

Speed and time trade off in a straight line while the line is the bottleneck, so 80 seconds at 100 Mbps becomes 320 at 25 Mbps, 160 at 50, 40 at 200, 16 at 500 and 8 at a gigabit. Every row counts a decimal gigabyte, so 8,000 megabits of file data, and assumes the rated speed arrives intact.

Two things stand out. The first is where the curve stops paying. Moving from 25 to 100 Mbps saves 4 minutes on a gigabyte, which is the difference between a coffee break and a blink. Moving from 100 to 500 Mbps saves 64 seconds, and moving from 500 Mbps to a gigabit saves 8 seconds, which is less time than it takes to open the folder where the file landed.

The second is that a single download at 100 Mbps is often limited by the sender, not the plan. A content delivery node that serves 4 MB/s to everyone in a neighborhood leaves two thirds of a 100 Mbps line idle. Below 100 Mbps the line is usually the constraint, so the arithmetic above is a fair forecast; above it, the server and the route start to decide.

Decimal GB, rounded GB and the binary GiB: 1:20, 1:22 and 1:26

Store pages, carriers and data caps count a gigabyte as 1,000 megabytes. Plenty of people round that to 1,024. A gibibyte is 1,073.741824 megabytes, and Windows labels it GB even though the correct name is GiB. The file on disk is the same in all three cases; only the unit's name changes.

The spread is 5.9 seconds, small enough to ignore for a single file and large enough to matter when a backup tool reports a set in gibibytes. One hundred gibibytes is 107,374.18 megabytes, which at 100 Mbps is 858,993.4 megabits, 8,589.9 seconds or 2 hours 23 minutes 10 seconds. Counted as 100 decimal gigabytes, the same set would take 8,000 seconds, so the binary label adds about 9 minutes 50 seconds.

Which figure belongs in a plan? The decimal one, because the bytes counted against a cap and the size printed on a store page both use it. The GiB number explains why a file sold as 1 GB shows as 0.93 GB in a Windows properties box and why a 1 TB drive formats to about 931 GB. Neither label is wrong, but mixing them in one estimate produces errors of 7 percent.

Where the extra 9 seconds go

The 80 second figure counts file payload only. A real transfer also carries TCP headers, acknowledgement packets, TLS records and the occasional retransmission. Wi-Fi frames every packet again, and a weak signal turns into retries that look exactly like a slower plan. The server may cap your share, and a busy delivery node serves a fraction of its capacity.

The usual planning allowance is 10 percent: 80 / 0.9 = 88.9 seconds, or 1 min 29 s. A wired connection to a fast server loses closer to 5 percent, which gives 84.2 seconds or 1 min 24 s. Crowded 2.4 GHz Wi-Fi can lose 15 percent, which gives 94.1 seconds or 1 min 34 s.

Some losses are worse than any row in that table. A VPN adds encryption and an extra hop. A game store on launch day can hand out 2 MB/s whether the customer bought 100 Mbps or 1 Gbps. The formula still holds in those cases, but the speed variable is whatever the slowest link in the chain delivers, not the number on the bill.

One correction is not overhead at all. The factor of 8 between bits and bytes is unit conversion, not loss, so keep the two ideas apart: overhead is a slice of the line you never see, and the factor of 8 is the definition of a byte.

One hour at 100 Mbps moves 45 GB

A 100 Mbps line left wide open moves 45 GB in an hour, because 100 Mbps for 3,600 seconds is 360,000 megabits. That single number answers most capacity questions. A 1.2 TB monthly cap allows 1,200 / 45 = 26.7 hours of saturated downloading, and almost nobody saturates a line for 26 hours.

Worked example: a 100 GB game. One hundred gigabytes is 800,000 megabits, which at 100 Mbps is 8,000 seconds or 2 hours 13 minutes 20 seconds. With 10 percent overhead it becomes 8,888.9 seconds, about 2 hours 28 minutes, so a game install fits in an evening and leaves the rest of the night free.

Worked example: a 4 GB patch. That is 32,000 megabits, 320 seconds or 5 min 20 s at the full rate, and 355.6 seconds or about 5 min 56 s with overhead. A 20 GB backup is 160,000 megabits, 1,600 seconds or 26 min 40 s, and about 29 min 38 s once overhead is counted.

Streaming works differently because a player buffers a few seconds ahead instead of fetching the whole file. A 4K stream runs at roughly 15 Mbps, so six streams use 90 Mbps of a 100 Mbps line and leave 10 Mbps for phones and a video call. A seventh stream pushes the line past its capacity, and every stream starts to stutter together, which is the signature of a saturated link rather than a weak Wi-Fi signal.

Upload, Wi-Fi and whether a gigabit is worth it

Download is only half of a plan. Cable packages built around 100 Mbps download often pair it with 10 or 20 Mbps upload, and the federal benchmark asks for 20 Mbps up. At 20 Mbps, sending a 1 GB file takes 8,000 / 20 = 400 seconds, or 6 min 40 s. At 10 Mbps it takes 800 seconds, or 13 min 20 s, which is why a cloud backup can make a video call stutter for a quarter of an hour.

Wi-Fi is the other place a 100 disappears. A 2.4 GHz link in an apartment building with a dozen neighboring networks can deliver a third of the plan, and a laptop two rooms from the router may see 30 Mbps while a wired desktop sees the full 100. Before blaming the provider, run a speed test beside the router and again where the slow device sits. If the second number is far below the first, the fix is a channel change or a mesh node, not a bigger plan.

Then there is the upgrade question. A gigabit line downloads the same gigabyte in 8 seconds instead of 80, which saves 72 seconds per file. For a household that pulls down a 100 GB game once a month, the saving is about 2 hours a month, and only if the store serves data fast enough to fill the line. For a household that streams and browses, 100 Mbps already covers six 4K streams, and the extra speed sits idle. Buy the gigabit for uploads and for many devices, not for the headline download figure.