How Long to Download 2 GB at 100 Mbps

2 GB at 100 Mbps is 160 seconds, or 2 minutes 40 seconds

Change the units first, because that is the step people skip. A gigabyte is 1,000 megabytes and a byte is 8 bits, so 2 GB is 2,000 MB and 2,000 x 8 = 16,000 megabits. Divide by 100: 16,000 / 100 = 160 seconds, which is 2 minutes 40 seconds.

Check it the other way. One hundred megabits per second is 100 / 8 = 12.5 megabytes per second, and 160 x 12.5 = 2,000 MB, the file you started with. Both routes land on the same number.

That clean figure assumes a wired link, one job on the connection and a server that feeds you at full speed. Each of those assumptions has a price, and the sections below put a number on each one, starting with the definition of the line itself.

Ten gigabytes is five times the wait, not ten times. Doubling the file doubles the clock, and halving the file halves it, so the arithmetic scales in a straight line as long as the speed holds.

100 Mbps is the federal baseline now, not a fast line

The number in this page title stopped being aspirational in 2024. On 14 March 2024 the FCC raised its fixed broadband benchmark to 100 Mbps down and 20 Mbps up, four times the 25/3 figure it had used since 2015 (FCC 24-27). The same order set a long term goal of 1 Gbps down and 500 Mbps up.

So a 100 Mbps plan is exactly the line a regulator would call broadband in 2024 and after. It is not headroom. It is the floor, and it is the speed that makes a 2 GB file a coffee break instead of a chore.

Worked example. Take the 100 Mbps benchmark and ask what a 2 GB file costs as a share of a fixed time budget. At 100 Mbps the file uses the whole line for 160 seconds, which is 2.67 minutes out of a 60 minute hour, or 4.44 percent of that hour.

Above 100 Mbps the limit moves from the line to something else. A 500 Mbps plan does not deliver 32 second downloads in most homes, because the Wi-Fi link, the server's upload cap or the disk write speed becomes the narrow part of the pipe.

Why the clock reads closer to 2:50: about 6 percent of the bits are not the file

The 160 second figure treats every bit on the wire as file data. Real traffic carries a header on every packet, acknowledges what arrived and resends what did not. Packet headers alone are roughly 2 to 5 percent of a full size transfer, and TCP slow start adds a second or two at the front.

Worked example at 6 percent. 160 x 1.06 = 169.6 seconds, or 2 minutes 49.6 seconds. That is 9.6 seconds more than the clean figure and the number a download manager usually reports on a wired connection. At 8 percent it is 172.8 seconds, or 2 minutes 52.8 seconds.

The spread from 160 to 179.2 seconds is 19.2 seconds, about 12 percent of the job. Planning for three minutes covers all of them, and that is why a 2 minute 40 second answer and a 3 minute answer can both be right.

Small files feel this cost more. On a 20 MB file the slow start can eat half the transfer, so a 2 GB file is the smallest size where the clean arithmetic is close to what a stopwatch shows.

2 GB or 2 GiB: 160 seconds against 171.8

Windows lists file size in gibibytes, where 1 GiB is 1,024 MiB, while network speeds are sold in decimal bits. A file that Windows calls 2.00 GB is usually 2 GiB, which is bigger than the 2 GB used above. Run the chain: 2 x 1,024 = 2,048 MiB, which is 2,147,483,648 bytes, or 17,179,869,184 bits.

Divide by 100,000,000 bits per second: 17,179,869,184 / 100,000,000 = 171.79869184 seconds, or 2 minutes 51.8 seconds. That is 11.8 seconds more than the decimal answer, a gap of 7.37 percent. Add 8 percent overhead and the job reaches 185.54258719 seconds, or 3 minutes 5.5 seconds.

The same mismatch is why a 2 TB drive shows up as 1.81 TB in Windows. Drive makers sell decimal terabytes and the operating system counts binary ones, and nothing is missing from the drive. Nothing is missing from the download either, and a three minute estimate covers both readings of the same file.

Wi-Fi takes a cut before the bytes reach the disk

A 100 Mbps plan can carry 12.5 MB every second. A radio link has to deliver that rate as goodput, meaning payload after its own overhead, and the band you join decides whether that happens.

2.4 GHz is the crowded band. Bluetooth, baby monitors, garage openers, microwave ovens and every neighbour's router share it, and only three channels avoid overlapping. An older single stream radio with a 72 Mbps link rate commonly delivers 30 to 40 Mbps of goodput. At 35 Mbps the 2 GB file takes 16,000 / 35 = 457.14 seconds, or 7 minutes 37.1 seconds.

5 GHz has more channels, wider channels and less interference, and it does not travel as far. A laptop in the same room as the router usually clears 100 Mbps without effort, so the download stays at 160 seconds. Two rooms away it may fall back to 2.4 GHz and land in the 35 Mbps case.

These goodput figures are estimates, not specifications. They depend on the radio, the channel width, the number of antennas and how many neighbours are transmitting. The pattern is what matters: a wired or near 5 GHz link gets the full 160 seconds, and a crowded 2.4 GHz link can triple it.

A 1.2 TB monthly cap holds 600 files this size

A 1.2 TB data cap is 1,200 GB, so 1,200 / 2 = 600 downloads of this file before the cap is gone. On a 500 GB cap the same file fits 250 times, and on a 250 GB cap 125 times.

Worked example at the cap. Move 1,200 GB over a 100 Mbps line and the meter runs 1,200 GB x 8 = 9,600 Gb, which is 9,600,000 megabits, or 96,000 seconds, or 26.67 hours of flat out transfer. A household that downloads 2 GB a day for 30 days moves 60 GB, which is 5 percent of the big cap and 12 percent of the small one.

If the file is counted in GiB the cap holds 1,200 x 10^9 / 2,147,483,648 = 558.79 of them, not 600. That is the same 7 percent gap as before, and it is worth 41 downloads a month on a 1.2 TB cap.

Uploads count too on most plans. A backup that sends 2 GB a day uses the same 60 GB a month, and a cap can run out from a background sync nobody remembers starting.

What else is on the line: one 4K stream takes 15 Mbps

Netflix publishes the speeds it recommends on its internet speed help page, which listed 3 Mbps for 720p, 5 Mbps for 1080p and 15 Mbps for 4K when checked in November 2026. Those are recommendations for a stable picture, so treat them as a floor for each stream.

Worked example. With one 4K stream running, the download has 100 - 15 = 85 Mbps left, and 16,000 / 85 = 188.23529412 seconds, or 3 minutes 8.2 seconds. With a 1080p stream it has 95 Mbps, and 16,000 / 95 = 168.42105263 seconds, or 2 minutes 48.4 seconds.

Divide 100 by 15 and you get 6.67, so six 4K streams fit with 10 Mbps to spare. Divide by 5 and twenty 1080p streams fit, which is more televisions than most houses own.

The rates above are Netflix's recommended minimums as published in 2026, not the peak a stream can use. A 4K title with high motion can run above 15 Mbps, and a router that prioritises video will hand the download the leftovers. The arithmetic still holds: every 15 Mbps you take away adds about 28 seconds to this file.

2 GB next to a 10 GB update and a 60 GB game

Two gigabytes is a small job in 2026. Put it beside the downloads people start and the scale becomes clear.

A 10 GB console update is 80,000 megabits, so 80,000 / 100 = 800 seconds, or 13 minutes 20 seconds. A 60 GB game is 480,000 megabits, which is 4,800 seconds, or 1 hour 20 minutes. A one hour television episode at 0.6 GB is 4,800 megabits, so 48 seconds.

The game is the case where a faster plan pays for itself. At 500 Mbps the same 60 GB lands in 960 seconds, or 16 minutes. At 100 Mbps it is an hour and twenty, which is long enough that most consoles schedule it overnight.

For the 2 GB file the practical answer is short. Two minutes forty on a clean line, about two minutes fifty with headers, three minutes five if the file is 2 GiB in Windows, and seven and a half minutes if the laptop fell back to a crowded 2.4 GHz channel.