Table of Contents
Your ISP promises 100 Mbps, but downloads peak at about 12 MB/s. You are not being scammed — that difference comes from bits vs bytes and real‑world overheads. This guide explains the simple math and what to expect when you hit download. You’ll learn the exact conversion (8 bits = 1 byte), a quick mental shortcut, why latency is different from bandwidth, how to test speeds properly, and what levels of Mbps you actually need for streaming, gaming, and video calls.
1Bits vs Bytes: the simple math
Most confusion starts with words: bits and bytes are not the same. A bit (b) is the smallest digital unit. A byte (B) is a group of 8 bits. Network plans use bits (Mbps = megabits per second), while many file managers and download tools show bytes per second (MB/s = megabytes per second).
What a bit and a byte are
A bit is 0 or 1. Eight bits make a byte: 8 bits = 1 byte. Abbreviations matter: lowercase b = bit, uppercase B = byte. So 1 Mbps means one million bits per second, not one million bytes.
Why 8 bits = 1 byte matters for speeds
To convert: MB/s = Mbps ÷ 8. Example: 100 Mbps ÷ 8 = 12.5 MB/s. That’s why a 100 Mbps line often shows download peaks around 12–13 MB/s in your browser or download manager.
2Mbps vs MB/s: advertised vs observed
ISPs advertise speeds in Mbps because bits gave the marketing edge when networks were slower. Your downloads are counted in bytes. The conversion is exact, but real downloads are usually a bit lower due to protocol overhead and traffic conditions.
Exact conversion and a quick trick
Formula: MB/s = Mbps ÷ 8. Mental shortcut: divide by 8 or multiply by 0.125. Reverse: MB/s × 8 = Mbps. So 25 MB/s × 8 = 200 Mbps. Keep that trick for quick checks.
Real-world example and overhead
Example: 100 Mbps theoretical = 12.5 MB/s. TCP/IP overhead, encryption, wifi loss and server limits typically shave off 5–20%. So a realistic top speed might be ~10–12 MB/s. This gap is normal. Famous unit mistakes exist too: NASA’s 1999 Mars Climate Orbiter was lost because two teams used different units — a reminder that units matter in tech.
3Latency vs bandwidth: different measurements
Bandwidth (Mbps) measures how much data can flow per second. Latency (milliseconds, ms) measures delay — how long a packet takes to travel. Both affect perceived performance but in different ways.
Latency explained and why it matters
Latency affects responsiveness. Low latency (e.g., 10–30 ms) makes interactive apps and games feel snappy. High latency (100+ ms) causes lag, even if bandwidth is high. Ping tests show latency; bandwidth tests show throughput.
When bandwidth alone won’t help
Large file downloads rely on bandwidth. Small request/response apps (like remote shells, some multiplayer games, or video conferencing) need both decent bandwidth and low latency. If a web page feels slow despite 200 Mbps, latency or DNS issues might be the cause.
4Testing and troubleshooting: get accurate numbers
Speed tests can be misleading if you don’t control variables. Test results depend on the test server, time of day, Wi‑Fi vs wired, background apps and more. Use a short checklist before you draw conclusions.
Speed test accuracy tips
1) Use a wired Ethernet connection for the most reliable result. 2) Close other apps and pause cloud syncs. 3) Test against multiple servers (local ISP server and a public one). 4) Run tests at different times. 5) Remember tests show throughput (bandwidth) and typically report both download/upload and ping.
Common sources of slowdowns
Wi‑Fi interference, an old router, overloaded home networks, or the remote server's limit. Also check for background updates, VPNs that add overhead, and poor cable quality. Rebooting the router or switching to a different DNS can sometimes help.
5What speed do you need? Practical guidance
Different tasks have different demands. Pick numbers based on concurrent users and the heaviest use case in your household or office.
Streaming, gaming and video calls (numbers)
Streaming: SD ~3–4 Mbps, HD 1080p ~5–8 Mbps, 4K ~15–25 Mbps per stream. Video calls: 1–3 Mbps for single HD, 3–6 Mbps for group HD; 4K calls need 10+ Mbps. Gaming: bandwidth is modest (3–10 Mbps) but latency under 50 ms is far more important. For households, add streams and devices: four people watching HD might need 4×8 = 32 Mbps + overhead.
Household planning and future-proofing
If you frequently stream 4K, game while streaming, or have many smart devices, aim higher (200–500 Mbps) to avoid contention. For light users, 50–100 Mbps is often plenty. Always consider upload needs if you stream or upload large files regularly.
Pro Tips
- 1Quick trick: divide Mbps by 8 to get MB/s (100 Mbps ÷ 8 = 12.5 MB/s).
- 2For best speed test results use a wired Ethernet connection and pause background uploads.
- 3If gaming feels laggy, check ping (ms) before adding more bandwidth.
- 4Plan upload speed if you do video calls or stream content — downloads aren’t everything.
Bits and bytes explain most of the surprise when advertised Mbps and observed MB/s don't match. Use the simple conversion (÷8 or ×0.125) and expect some overhead from protocols, encryption and wireless losses. Run wired tests, watch latency for interactive apps, and pick a plan based on the heaviest use in your home. Try the converters on this site to check exact numbers and plan the right package.
