How Data Transfer Speeds Work: Mbps, MB/s and Download Times

Connection speed is the amount of data a link carries each second, usually stated in megabits per second. Divide by eight to get megabytes per second, the figure your download window shows.

From megabits to megabytes

MB/s = Mbps ÷ 8

Connection speedMaximum download rateTime for a 1 GB file
10 Mbps1.25 MB/s13 min 20 s
50 Mbps6.25 MB/s2 min 40 s
100 Mbps12.5 MB/s1 min 20 s
500 Mbps62.5 MB/s16 s
1 Gbps125 MB/s8 s

Estimating download time

time (seconds) = file size (MB) × 8 ÷ speed (Mbps)

A 4.7 GB file is 4,700 MB. On a 60 Mbps connection it takes 4,700 × 8 ÷ 60 = 627 seconds, about ten and a half minutes.

Why real speeds are lower

  • Protocol overhead. Addressing, error checking and encryption use a few percent of the capacity.
  • Shared capacity. Other devices and other households share the same link at busy times.
  • Wi-Fi. Signal strength, interference and older standards often limit speed well below the line rate.
  • The other end. A server can only send as fast as its own connection and load allow.
  • Storage. A slow drive or memory card can be the bottleneck on very fast links.

Download, upload and latency

Most home connections are asymmetric, with upload much slower than download. Upload matters for video calls, cloud backup and sending large files. Latency, measured in milliseconds, is the delay before data starts to arrive. It is separate from speed: a satellite link can be fast yet feel sluggish because every request takes longer to make the round trip.

Bandwidth and frequency

The word bandwidth originally described a range of radio frequencies, in hertz. A wider band of frequencies can carry more data per second, which is why the term came to mean data capacity. The two meanings are related but not the same unit.

What speed do you need?

As rough figures, streaming services recommend about 5 Mbps for HD video and 15 to 25 Mbps for 4K. A video call uses 1 to 4 Mbps in each direction. Add the needs of everyone using the connection at once.

Frequently asked questions

How many MB/s is 100 Mbps?

12.5 megabytes per second.

Why does my speed test show less than I pay for?

Advertised speeds are usually maximums. Wi-Fi, network congestion, your device and the test server all reduce the measured figure. Test over a cable for the fairest comparison.

What is a 'rule of 10' shortcut for estimating MB/s from Mbps?

Instead of dividing Mbps by 8 (300 ÷ 8 = 37.5 MB/s) and then subtracting ~10% protocol overhead, simply **divide Mbps by 10** (300 Mbps ÷ 10 ≈ 30–35 MB/s) for a realistic real-world download speed estimate.

Why does my speed test show 250 Mbps while a file download from a small site crawls at 4 MB/s (32 Mbps)?

A speed test opens 8 to 16 parallel TCP streams to a nearby edge server on your ISP's own network. A single-stream download from a distant web server is limited by that server's outbound bandwidth cap and TCP round-trip latency (BDP window).

Does lowering ping (latency) make a large file download faster?

Once a TCP connection ramps up its congestion window, a 50 GB download over a 20 ms link and a 60 ms link run at the same steady-state bandwidth. Low latency matters most for thousands of tiny web requests, gaming, and video calls.

Worked example: How long it really takes to download a 65 GB game over a 300 Mbps fiber connection

Suppose you are downloading a **65 GB** (65,000 MB decimal, or 69.79 billion bytes) game update over a **300 Mbps** (300 megabits per second) home fiber line:

  • Step 1 — Convert line rate from megabits/s to megabytes/s (÷ 8): Because there are 8 bits in 1 byte, the theoretical raw byte rate is 300 Mbps ÷ 8 = 37.5 MB/s.
  • Step 2 — Account for TCP/IP + TLS + Ethernet framing overhead (~6%): Every 1,500-byte Ethernet packet carries 20 bytes of IPv4 header, 20–32 bytes of TCP header, TLS record framing, and Ethernet preamble/CRC, leaving roughly **94% usable application goodput**: 37.5 MB/s × 0.94 = 35.25 MB/s.
  • Step 3 — Calculate download duration:
    • If the 65 GB figure is decimal (65,000 MB): 65,000 MB ÷ 35.25 MB/s = 1,844 seconds = 30 minutes 44 seconds.
    • If Steam/Windows reports 65 binary GiB (69,793 MB decimal): 69,793 MB ÷ 35.25 MB/s = 1,980 seconds = 33 minutes 00 seconds.

Limits and why real-world speeds vary

  • Wi-Fi half-duplex airtime overhead: Even if a Wi-Fi 6 router advertises a 1,200 Mbps physical link rate, Wi-Fi is half-duplex (only one device transmits at a time with ACK frames and contention gaps), so real TCP throughput over Wi-Fi is typically 50% to 65% of the PHY link rate.
  • Disk decompression bottleneck on fast gigabit lines: Game installers (Steam, Epic) download compressed chunks and decompress them on the fly. On a 1 Gbps (118 MB/s) fiber line, a slow CPU or SATA drive can bottleneck the install speed even when the network has spare capacity.