How Long to Download 5 GB at 10 Mbps

Five gigabytes at 10 Mbps is 4,000 seconds, or 1 hour 6 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 5 GB is 5,000 MB and 5,000 x 8 = 40,000 megabits. Divide by 10: 40,000 / 10 = 4,000 seconds, which is 1 hour 6 minutes 40 seconds.

Check it the other way. Ten megabits per second is 10 / 8 = 1.25 megabytes per second, and 5,000 MB / 1.25 = 4,000 seconds. The download bar will read 1.25 MB/s when the line is running flat out, and that number times 4,000 puts you back on 5,000 MB.

Break the 4,000 seconds apart and it reads better on a clock: 3,600 seconds is an hour, 400 seconds is 6 minutes 40 seconds, so the whole job is 1:06:40. In minutes that is 66.67, which is the figure most download managers use when they guess at a finish time.

The table scales in a straight line while the speed holds. Two gigabytes is 1,600 seconds and five is 4,000, which is 2.5 times the wait for 2.5 times the data. Ten gigabytes is 8,000 seconds, or 2 hours 13 minutes 20 seconds, and that is the point where most people start a download overnight instead of watching it.

Ten megabits per second is 1.25 MB per second, and the FCC floor is ten times higher

Ten megabits per second is a slow line in 2026. The FCC raised its fixed broadband benchmark to 100 Mbps down and 20 Mbps up in the Section 706 report adopted on 14 March 2024, four times the 25/3 standard it had used since 2015. Against that yardstick, 10 Mbps is 10 percent of the download floor and half the upload floor.

Where you still meet 10 Mbps: an older DSL line, hotel and dorm Wi-Fi that throttles per room, a phone hotspot after the high speed allowance runs out, and some fixed wireless plans in rural areas. The FCC consumer guide to home broadband describes the "up to" wording providers use, and notes that an old router, peak hour congestion or a slow device can all pull a connection below the advertised number.

At 1.25 MB/s, a 5 MB photo arrives in 4 seconds and a 700 MB television episode takes 9 minutes 20 seconds. Browsing feels fine. A 5 GB file is where the line stops being invisible and starts being an appointment on your calendar.

Worked example: the same 5 GB on a 100 Mbps line is 40,000 / 100 = 400 seconds, which is 6 minutes 40 seconds. The file does not get smaller, the line just moves 10 times the data per second.

Headers and retries: 6 percent puts the clock at 4,240 seconds

The 4,000 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 costs a second or two at the front of the job.

Worked example at 6 percent: 4,000 x 1.06 = 4,240 seconds, which is 1 hour 10 minutes 40 seconds. That is 4 minutes more than the clean figure and close to what a download manager reports on a wired link. At 2 percent it is 4,080 seconds, or 1 hour 8 minutes. At 12 percent, which is a weak Wi-Fi signal with retries, it reaches 4,480 seconds, or 1 hour 14 minutes 40 seconds.

The spread from 4,000 to 4,480 seconds is 480 seconds, or 8 minutes. On a 5 GB file that is small enough to ignore, and on a 60 GB game the same 12 percent adds 1 hour 36 minutes, which is why game consoles show a range rather than a single finish time.

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

Five gigabytes or five GiB: 4,294.967296 seconds

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 5.00 GB is usually 5 GiB, which is bigger than the 5 GB used above. Run the chain: 5 x 1,073,741,824 = 5,368,709,120 bytes, which is 42,949,672,960 bits.

Divide by 10,000,000 bits per second: 42,949,672,960 / 10,000,000 = 4,294.967296 seconds, or 1 hour 11 minutes 35 seconds. That is 295 seconds more than the decimal answer, a gap of 7.37 percent. The NIST page on binary prefixes lists both readings, and the 7.37 percent is just 1.024 cubed.

Add 6 percent overhead to the binary figure and the job reaches 4,552.67 seconds, or 1 hour 15 minutes 52 seconds. That is the worst case in this page, and it is still under 1 hour 20 minutes, which is where a sensible estimate lands.

The same mismatch is why a 2 TB drive shows up as 1.81 TB in File Explorer. Drive makers sell decimal terabytes and the operating system counts binary ones. Nothing is missing from the drive and nothing is missing from the download, but a page that quotes one reading and a download bar that shows the other will always look 7 percent wrong.

The same file at other line speeds, from 11 hours to 40 seconds

Speed is the lever with the most travel. Double the line and the clock halves, because 40,000 megabits divided by a bigger number is a smaller number. That relationship holds until something else in the chain becomes the narrow part.

Worked example: 25 Mbps is 3.125 MB per second, so 5,000 / 3.125 = 1,600 seconds, or 26 minutes 40 seconds. At 50 Mbps it is 800 seconds, or 13 minutes 20 seconds. At 1 Gbps it is 40 seconds, and at that point the line is no longer the slow part of the job.

Above roughly 200 Mbps the limit moves off the line. A 1 Gbps plan does not deliver 40 second downloads in most homes, because the Wi-Fi link, the server upload cap, or the write speed of the drive becomes the narrow part. Steam and console stores are the usual place to see this: the reported speed climbs, then flattens while the CPU unpacks.

The 1 Mbps row is worth reading twice. It is 40,000 seconds, or 11 hours 6 minutes 40 seconds, which is longer than a working day. A line that slow turns a 5 GB file into a decision about whether to start it at all.

One 1080p stream sharing a 10 Mbps line doubles the wait

A 10 Mbps line has no spare room. One 1080p stream at 5 Mbps takes half of it, which leaves 5 Mbps and doubles the wait to 8,000 seconds, or 2 hours 13 minutes 20 seconds. A video call at 3 Mbps leaves 7 Mbps and stretches the job to 5,714.3 seconds, or 1 hour 35 minutes 14 seconds.

A 4K stream does not fit at all. The 15 Mbps a 4K title asks for is more than the whole line, so the player and the download fight and both stutter. On a 10 Mbps connection the honest choice is to pause the download while the television is on.

Evening congestion is the other half of this. A line tested at 10 Mbps at 2 in the afternoon can measure 6 or 7 Mbps between 8 and 10 at night, when the block is streaming. That does not change the arithmetic, it changes the number you put into it: 40,000 / 7 = 5,714 seconds, which is the same 1 hour 35 minutes as the video call case.

Wi-Fi adds its own cut. A laptop two rooms from the router on a crowded 2.4 GHz channel often gets 3 to 5 Mbps of goodput from a 10 Mbps line, and the download stretches past three hours. Plugging in an Ethernet cable is the cheapest fix on this page.

Caps, hotspots and real jobs: 240 files in 1.2 TB

A 1.2 TB data cap is 1,200 GB, so 1,200 / 5 = 240 downloads of this file before the cap is gone. On a 500 GB cap the same file fits 100 times, and on a 250 GB cap 50 times. Count the overhead and the numbers move: 5 GB of file is 5.3 GB on the wire, so a 1.2 TB cap holds 226.4 of them, not 240.

Move the whole cap over a 10 Mbps line and the meter runs 1,200 GB x 8 = 9,600 Gb, which is 9,600,000 megabits, or 960,000 seconds, or 266.67 hours. That is 11.1 days of flat out transfer, so a 1.2 TB cap is not a limit a 10 Mbps line can reach by accident.

Put the file next to the jobs people start. A 60 GB game is 480,000 megabits, which is 48,000 seconds, or 13 hours 20 minutes at 10 Mbps. A 20 GB console update is 16,000 seconds, or 4 hours 26 minutes 40 seconds. A 700 MB episode is 560 seconds, or 9 minutes 20 seconds.

Storage is faster than the line by a wide margin. A USB 2.0 drive that writes 35 MB per second copies 5,000 MB in 142.9 seconds, or 2 minutes 23 seconds. The disk is never the reason a 5 GB download takes an hour, and that is worth knowing before you buy a faster drive to fix a slow connection.

For planning, 1 hour 15 minutes covers the decimal file with overhead and the binary file on its own. Add 20 minutes when the house is awake, and start the job before dinner rather than after.