How long to download 5 GB at 200 Mbps

Five gigabytes at 200 Mbps is 200 seconds, or 3 minutes 20 seconds

One division, after the bits are counted

Five decimal gigabytes hold 5,000,000,000 bytes. Eight bits make a byte, so the file is 40,000,000,000 bits, or 40,000 megabits. A 200 Mbps line carries 200,000,000 bits every second, and 40,000 / 200 = 200 seconds. That is 3 minutes 20 seconds.

The transfer window will not show 200. It counts bytes, so it reads 200 / 8 = 25 MB/s, and one minute of transfer moves 25 x 60 = 1,500 MB, or 1.5 GB. The byte side gives the same answer: 5,000 MB / 25 MB/s = 200 seconds.

At that rate an hour of full speed carries 90 GB. The tier fits a household that downloads games and streams 4K video, and it comes up short for anyone who moves a terabyte a month.

Wire overhead and the binary reading add 12 and 15 seconds

Two corrections that point in the same direction

A raw division assumes every bit on the wire is file data. It is not. TCP and IP headers, Ethernet framing, PPPoE on some fiber lines and Wi-Fi management traffic all take a cut. Six percent is a common planning figure for a wired connection, and it turns 200 seconds into 200 x 1.06 = 212 seconds, or 3 minutes 32 seconds.

The second correction is the unit Windows reports. A file labeled 5 GB in File Explorer is usually 5 GiB, because Windows divides by 1,073,741,824. That is 7.37 percent more data, so the same line needs 200 x 1.073741824 = 214.7483648 seconds, which rounds to 3 minutes 35 seconds. The binary reading adds 14.75 seconds, so it is the smaller of the two corrections.

Stack them and 5 GiB with 6 percent overhead needs 214.7483648 x 1.06 = 227.63 seconds, or 3 minutes 48 seconds. The tidy 200 seconds is a floor, not a promise.

The corrections stack, so a promise built on 200 seconds is optimistic by up to 28 seconds:

Two hundred megabits is double the federal floor and half the US median

Where the tier sits in 2026

On 14 March 2024 the FCC raised the fixed broadband benchmark from 25 Mbps down and 3 Mbps up to 100 Mbps down and 20 Mbps up in its Section 706 report, FCC 24-27. The same order set a long-term goal of 1 Gbps down and 500 Mbps up. A 200 Mbps plan is double the floor and one fifth of the gigabit goal.

Market data puts it below the middle. The Speedtest Global Index for the United States, published by Ookla, reported a median fixed download speed of 403.42 Mbps and a median upload of 216.70 Mbps in September 2026, with 22 ms latency. Two hundred megabits is 200 / 403.42 = 49.6 percent of that median, a gap of 203.42 Mbps.

That does not make the line slow. It makes it an entry tier: legal broadband, roughly half of what the typical US fixed connection measures, and enough for the workloads below.

The package name matters less than two numbers on the invoice: the upstream rate and the data terms. A 200 Mbps package may arrive bundled with a gateway rental, a promo that expires after a year and an autopay discount, none of which changes the bit rate. Ask the installer what the modem negotiates, and read the contract for an overage charge. Those terms outlast any speed test.

Four 4K streams and the same download share one budget

Streams are subtracted before the file gets its turn

The FCC Broadband Speed Guide, last reviewed on 18 July 2022, lists 25 Mbps as the minimum for one 4K stream, 5 to 8 Mbps for HD, 6 Mbps for an HD video conference and 4 Mbps for online multiplayer. Those are per-activity floors, and they assume one activity at a time.

Give four 4K streams 25 Mbps each and 100 Mbps is gone. The file then needs 40,000 / 100 = 400 seconds, or 6 minutes 40 seconds, double the empty-line clock. A single 4K stream leaves 175 Mbps, and the file lands in 228.6 seconds, or 3 minutes 49 seconds.

Split the line evenly across four devices instead and each one gets 50 Mbps, so the same 5 GB file takes 40,000 / 50 = 800 seconds, or 13 minutes 20 seconds, on every device at once.

A 1 TB allowance holds 200 copies and 11 hours of transfer

The cap is a limit on hours, not on speed

A 1 TB monthly allowance is 1,000 GB, so 1,000 / 5 = 200 copies of this file before the meter stops. Each copy at 200 seconds adds up to 200 x 200 = 40,000 seconds, or 11 hours 6 minutes 40 seconds of continuous transfer.

A four person household that also streams HD video and works from home often lands near 2 TB a month. At 90 GB per hour that is 2,000 / 90 = 22.2 hours of full rate transfer, spread across 720 hours in the month. The allowance is roomy for browsing and tight for a family that reinstalls three games a month.

Count the overhead and each copy costs 5.3 GB on the wire, which drops the count to 1,000 / 5.3 = 188.68. The hourly rate is the useful number for planning: 90 GB per hour, 2,160 GB per day, or 2.16 TB if the line never idles. A household that streams and browses will never approach that, while one that reinstalls games can spend half the allowance in a weekend.

A 60 GB game, a 20 GB patch and a 100 GB backup

Bigger files scale in a straight line

Convert each file to megabits, then divide by 200. The pattern is linear, because every 5 GB costs 200 seconds at this rate.

• A 350 MB episode: 2,800 megabits / 200 = 14 seconds.
• A 20 GB patch: 160,000 / 200 = 800 seconds, or 13 minutes 20 seconds.
• A 60 GB game: 480,000 / 200 = 2,400 seconds, or 40 minutes.
• A 100 GB backup set: 800,000 / 200 = 4,000 seconds, or 1 hour 6 minutes 40 seconds.

The same arithmetic covers a system image. A 250 GB drive cloned over the network is 2,000,000 megabits, so 2,000,000 / 200 = 10,000 seconds, or 2 hours 46 minutes 40 seconds. Backups of that size are the point where a 200 Mbps line starts to feel like an overnight job.

One gigabyte costs 40 seconds and 10 GB costs 400 seconds. Only the numerator changes; the line does not speed up for large files, and it does not slow down for small ones.

The same rate covers any payload, because 200 Mbps means 40 seconds per gigabyte:

Where the 200 leaks: Wi-Fi, one socket and a 100 Mbps port

Three local limits that stretch the clock

Wi-Fi. A laptop on 5 GHz that negotiates 60 percent of the advertised rate sees 120 Mbps, and the file takes 40,000 / 120 = 333.3 seconds, or 5 minutes 33 seconds. On 2.4 GHz, where a 20 MHz channel often yields 70 to 90 Mbps in practice, the same file runs 444 to 571 seconds.

Channel width matters as much as the label. A 5 GHz radio at 80 MHz has more room than one at 40 MHz, and a mesh node that dedicates a second radio to backhaul keeps that traffic off the air the laptop uses. Plaster walls, a brick chimney and a metal duct attenuate the signal more than drywall, so the same router can be strong in one room and weak two walls away. A channel scan, a fixed channel and a wired backhaul where possible cost less than a faster plan.

One socket. A single server connection capped at 80 Mbps gives 40,000 / 80 = 500 seconds, or 8 minutes 20 seconds, however fast the line is. Browsers and download managers open several connections for this reason.

Measure the path rather than the plan. Run iperf3 between two wired laptops, or copy the same file from a local server, and read the adapter's negotiated link speed. A duplex mismatch, a failing cable, a loose keystone jack or an old Cat5e run to the patch panel shows up as retransmits and a rate below the port speed. Update the network driver and the router firmware, then repeat the test. If the local copy is fast and the internet copy is slow, the problem is upstream; if both are slow, it is the cable, the port or the driver.

The port. A 100 Mbps Ethernet port on an older router or a cheap switch caps the transfer at 400 seconds, exactly the clock of a 100 Mbps plan. Check the link speed in the adapter settings before blaming the ISP.

Powerline kits and coax adapters: the wiring inside the wall

When moving the router is not an option

A rental with no ceiling access leaves two wired options that are not Ethernet: a powerline kit that carries data over the electrical circuit, and a MoCA adapter pair that uses the coax already in the wall.

Both have a real ceiling below the label. A kit marketed at 1,200 Mbps often negotiates a fraction of that, and a run that crosses the breaker panel can end up slower than the broadband line it was bought to extend. MoCA adapters on old coax behave the same way: one house sustains 400 Mbps, the next manages 150.

Placement decides more than the spec sheet. An adapter in a socket beside a dimmer, a phone charger or a lamp with a switching supply picks up electrical noise, and one on a different circuit phase may not pair at all. The coax path has its own traps: an old splitter, a corroded connector or an amplifier feeding the set-top box can cut the rate. Move the adapter, swap the splitter and test again before concluding the kit is bad.

Run the arithmetic before buying. At 400 Mbps the file takes 40,000 / 400 = 100 seconds. At 160 Mbps it takes 250 seconds, or 4 minutes 10 seconds, which is worse than a clean 5 GHz link. Test with one transfer on the far adapter, compare it with the same file over Wi-Fi, and keep the faster path.