Internet speeds are advertised in bits per second; file sizes are measured in bytes. Confusing the two is one of the most common — and most consequential — mistakes people make when judging how long a download will actually take. This tool converts between them.
The most fundamental unit in computing, and the group of eight built on top of it
A bit — a contraction of "binary digit," a term popularized by mathematician and information theorist Claude Shannon in his foundational 1948 paper on information theory — is the smallest possible unit of digital information: a single 0 or 1. Early computer architects settled on grouping bits into sets of eight, called a "byte" (a deliberately altered spelling of "bite," changed to avoid confusion with "bit," reportedly coined by IBM engineer Werner Buchholz in 1956), because eight bits was enough to represent a single character of text in early character encoding standards while remaining a convenient, hardware-friendly power of two.
The conversion — and why it trips people up
1 byte = 8 bits exactly, a fixed, universal relationship with no historical ambiguity, unlike the kilo/mega/giga binary-versus-decimal disputes elsewhere in computing. The confusion instead comes from notation: internet and network speeds are conventionally measured in bits per second (Mbps, with a lowercase "b"), while file sizes are measured in bytes (MB, with an uppercase "B") — meaning a "100 Mbps" internet connection actually downloads at roughly 12.5 megabytes per second, not 100, since you divide by 8 to convert bits to bytes.
Where this distinction has real consequences
- Estimating download times — correctly converting your internet plan's advertised bit-based speed into byte-based throughput is the single most common source of "why is my download so much slower than my internet speed?" confusion.
- Networking and IT work — network engineers routinely convert between bits (used for bandwidth and data transmission rates) and bytes (used for file and storage sizes) when diagnosing performance or planning capacity.
- Reading data plan and streaming quality specs — video streaming bitrates are given in bits per second (like a 5 Mbps stream), which needs converting to bytes to estimate actual data usage against a byte-denominated data cap.
- Comparing storage device transfer speeds — USB and drive interface speeds are sometimes marketed in bits per second (like "USB 3.0: 5 Gbps") while the files being transferred are measured in bytes, requiring conversion to estimate real-world transfer time.
Frequently asked questions
Why do ISPs advertise speed in bits instead of bytes? Largely marketing convention rooted in telecommunications history — bits-per-second has been the standard unit for describing raw data transmission rates since early modem and networking technology, and using it produces a numerically larger, more impressive-looking figure than the equivalent byte-based number.
How do I quickly estimate byte speed from a bit speed? Divide by 8 — a "50 Mbps" connection gives roughly 6.25 MB/s of actual byte throughput, a rule of thumb worth remembering whenever you're trying to estimate a realistic download time.
Is the lowercase/uppercase "b" distinction really meaningful? Yes, and it's one of the most easily overlooked details in technical writing — "Mb" (megabit) and "MB" (megabyte) differ by a factor of 8, and mixing them up in a spec sheet or comparison produces a genuinely wrong conclusion.
Further reading
Wikipedia — Bit — Claude Shannon's foundational role in defining the bit as the basic unit of information.