Developer ToolsBits vs bytes

Bandwidth Calculator

Almost every mistake in this area comes from one place: connections are sold in bits per second and files are measured in bytes. A 100 Mbps line does not move 100 MB per second — it moves about 12. This keeps the two apart.

Transfer

Note the units carefully — Mb is megabits, MB is megabytes.

TCP/IP headers, retries — 5–10% is typical
%
DOWNLOAD TIME
6m 49s
Usable throughput after overhead11.5 MB/s (92 Mbps)
Speed expressed in MB/s12.5 MB/s nominal
Time at the theoretical maximum6m 16s
Per-stream sharesingle stream — full line
Data used if repeated daily for a month141 GB per month if repeated daily
4.7 GB is 4.700 GB (37,600 megabits). At 100 Mbps with 8% overhead, that takes 6m 49s — against 6m 16s at the theoretical maximum. Note the factor of eight: 100 Mbps is 12.5 MB/s, not 100 MB/s. Connections are sold in bits, files are measured in bytes. You chose an SI unit (10⁶ bytes per MB), which is what drive and network vendors quote — an operating system would display this file as about 4,482.27 "MB", because it counts in mebibytes. Real transfers are also limited by the server, by congestion, and on Wi-Fi by shared airtime, which often costs far more than the protocol overhead entered here.

Bits, bytes, and why your download looks slow

Network speeds are quoted in bits per second; storage and files are measured in bytes. There are eight bits in a byte, so a 100 Mbps connection tops out at 12.5 MB/s before any overhead. This single factor of eight is responsible for most "my internet is slower than advertised" complaints. A lower-case b means bits, an upper-case B means bytes — Mbps and MB/s differ by a factor of eight even though they look almost identical in a browser tab.

The second unit trap: MB versus MiB

There are two conventions for the prefixes themselves. In the SI convention used by network and drive manufacturers, one megabyte is 106 = 1,000,000 bytes. In the binary convention used by most operating systems when reporting file sizes, what is displayed as one megabyte is really a mebibyte: 220 = 1,048,576 bytes. The gap is 4.9% at mega and grows to 10% at tera — which is why a "1 TB" drive shows up as about 931 GB in a file manager. Nothing has been lost; the two systems are counting differently. This calculator offers both so you can match whichever source your number came from.

Overhead is real and unavoidable

Raw link speed is not usable throughput. TCP/IP headers, acknowledgements, retransmissions, encryption and framing all consume capacity, and a typical figure is 5 to 10% on a wired connection. Wi-Fi is far worse — shared airtime, collisions and protocol overhead often leave only half of the nominal rate available in practice, which is why a 300 Mbps Wi-Fi label rarely delivers more than 150 Mbps of real data. Server limits, congestion at peak times and the distance to the source can all constrain the transfer further.

Sharing one line between streams

Bandwidth divides among everything using the connection. Four people streaming at once each get roughly a quarter of the line, assuming nothing prioritizes one flow over another. The per-stream figure above is that simple division. In practice, real-time traffic such as video calls suffers far more from latency and jitter than from raw bandwidth — a call needs only a few megabits, but it needs them consistently, which is why a large download in the background can ruin a call on a line that is nominally fast enough for both.

Reading a data cap

Monthly caps are quoted in bytes, usually gigabytes. The last output line multiplies the transfer by 30 so you can see what a daily habit costs against a cap. Streaming video is the dominant consumer for most households: standard definition is roughly 1 GB per hour, high definition around 3 GB, and 4K can exceed 7 GB per hour, so a single evening of 4K viewing can consume more than a week of ordinary browsing.

Frequently Asked Questions

Why is my 100 Mbps connection only downloading at 12 MB/s?
It is not slow — it is the unit. There are eight bits in a byte, so 100 megabits per second is 12.5 megabytes per second at best, before protocol overhead.
Why does my 1 TB drive show as 931 GB?
The manufacturer counts a terabyte as 10 to the 12 bytes; the operating system displays binary units where a "GB" is really a gibibyte of 2 to the 30 bytes. The difference is about 9%. No capacity is missing.
What overhead figure should I use?
Five to ten percent is reasonable for a wired connection. On Wi-Fi, expect to lose considerably more — often close to half the nominal link rate once airtime sharing is accounted for.
How much bandwidth does a video call need?
Only a few megabits, but consistently. Calls are far more sensitive to latency and jitter than to raw speed, so a background download can disrupt a call on a connection with bandwidth to spare.
Where these numbers come from

Sources

Official publications only. Links open the original document in a new tab.