How long to download 20 GB at 500 Mbps

Five minutes twenty seconds, one division at a time

Twenty gigabytes is 160,000 megabits

Twenty gigabytes is 20,000 megabytes, and a byte is 8 bits, so the file holds 160,000 megabits. Divide that by 500 megabits per second and 320 seconds falls out, which is 5 minutes 20 seconds. The byte reading of the same line is 500 / 8 = 62.5 MB/s, and 20,000 / 62.5 confirms the 320 seconds.

The number worth memorizing is the per gigabyte cost: 16 seconds. A 5 GB game patch is 80 seconds, a 10 GB update is 160 seconds, and the 20 GB file on this page is 320.

One trap sits in the file manager. A folder that reads 20 GB in some tools means 20 GiB, which is 21.47 billion bytes. NIST's page on binary prefixes records the fix: the IEC approved GiB and its relatives in 1998 so a power of two would stop borrowing a decimal name. Take the file as 21.47 GB and the clock is 343.6 seconds, or 5 minutes 44 seconds, a 24 second gap.

Where a 500 Mbps line sits against the federal benchmark

Five times the 2024 floor, half the long term goal

The FCC raised the fixed broadband benchmark to 100/20 Mbps in the report it adopted on March 14, 2024, a four fold jump from the 25/3 standard set in 2015. The same order set a long term goal of 1,000 Mbps down and 500 Mbps up. The full text is FCC 24-27, the 2024 Section 706 report.

Read those two figures against a 500 Mbps plan and the shape of the tier appears. The download side is five times the benchmark and half of the long term goal. The upload side of a 500/20 plan is exactly the benchmark number, with no margin, because cable plant built for television spends most of its capacity in one direction.

The FCC Broadband Speed Guide lists 10 Mbps as the minimum for file downloading and 25 Mbps for streaming 4K video. Five hundred is fifty times the download minimum, which is why the 20 GB file here is a coffee break and why the rows further down the table are the ones worth planning a day around.

Doubling from 250 to 500 saves 5 minutes 20 seconds on this file. Doubling again to a gigabit saves another 2 minutes 40 seconds. The returns flatten fast on small files, which is the whole argument for buying this tier only when the big rows matter.

The radio takes a fifth to a third of the line

Cable, 5 GHz, 2.4 GHz

The FCC's Home Network Tips page states the trade in a paragraph: 2.4 GHz offers broader coverage but processes data less quickly, 5 GHz is faster over a shorter range, and a direct Ethernet cable gives the highest speed of all. The shares below are planning figures for a normal house, not a reading from your rooms.

The top three rows sit inside the 60 to 80 percent band most home wireless delivers to a laptop that is not behind three walls. A device that manages 60 percent sees 300 Mbps, and the file takes 533 seconds, or 8 minutes 53 seconds.

Read the table from the bottom up. Even the worst row moves the file in 21 minutes, which is faster than the full plan most households had a few years ago. That is the quiet benefit of a 500 Mbps tier: a weak link stops being a disaster and becomes an ordinary wait.

The other half of the FCC advice is easier to act on. If a speed test in the room where you download reads 300 Mbps on a 500 Mbps plan, no upgrade will change that. Move the router to a central spot, or run a cable to the machine doing the work.

Six percent of the line is bookkeeping, not file

Headers, acknowledgements and framing

Every transfer carries packet headers, acknowledgements and framing that never land in the file. A 6 percent allowance covers that on a normal TCP connection, and 320 seconds becomes 339 seconds, or 5 minutes 39 seconds. Ten percent gives 352 seconds, or 5 minutes 52 seconds.

A percentage hides how the cost scales. Six percent of a 320 second job is 19 seconds, easy to dismiss. Six percent of a 500 GB transfer is 480 seconds, or 8 minutes, because the base is 8,000 seconds. The allowance is the same; the bill is not.

This is the smallest correction on the page, and the one people skip. Add it to any figure you quote to a client, because the advertised rate and the delivered file always differ by a few percent.

The upload half is where the plan shows its age

Twenty five times the wait in the other direction

Send the same 20 GB upstream on a 500/20 plan and the sum is 160,000 / 20 = 8,000 seconds, or 2 hours 13 minutes 20 seconds. The download took 5 minutes 20 seconds. Same file, same wire, 25 times the wait.

A symmetric 500/500 plan makes the two directions equal again. Between those two products sits most of what a household does with upload: a phone backup before a factory reset, a 20 GB video to a client, a disk image to cloud storage. On the 20 Mbps uplink each of those is an afternoon. On fiber it is a coffee break.

Upload also leans on download. Cloud sync and video calls spend upstream bandwidth, and the acknowledgements that keep a download moving travel that way too. A backup running at full uplink can pull the file's speed well below the rated figure with nothing wrong at the provider's end.

If the plan is 500/20 and the work is mostly upload, the download number is decoration. Ask the provider for the upload figure before signing, and ask whether a fiber product is available at the address.

What caps the job once the line stops being the limit

Ports, disks and the server at the other end

At 500 Mbps the connection is rarely the slowest part of a 20 GB job. The limits move indoors and to the far end of the transfer.

Two rows are slower than the line and both are local. A USB 2 stick writes at around 30 MB/s, so the file spends 667 seconds being written even though the bits arrived in 320. The disk becomes the clock, and no plan fixes it.

The far end matters just as much. Large game stores and operating system updates run content networks that will fill a 500 Mbps line. A small club site on one shared server serves at a few megabytes a second and cannot. When a download crawls on a fast plan, check the port on the router, the cable, and the disk before calling the provider.

An hour of this line is 225 GB

Throughput per minute, hour and day

At 62.5 MB/s the line moves 3,750 MB a minute, which is 225 GB an hour. In one hour the progress bar crosses the 20 GB file 11.25 times. In a 24 hour day the line would move 5,400 GB, or 5.4 TB, if anything upstream could feed it that fast.

Those figures explain why data caps stop mattering for most homes and start mattering for a few. Twenty gigabytes a week is 80 GB a month, well inside any cap. A 1.2 TB allowance spent at full rate lasts 5 hours 20 minutes, so a household that clones drives or edits video can reach the cap in one evening.

The per minute figure is the useful one in practice. Eighteen percent of the file lands in the first minute, so a progress bar that reads 20 percent after 60 seconds is running at the rated speed, not stalling.