Bandwidth is one of the most advertised and least understood numbers in consumer technology. Your ISP promises 200 Mbps, your download manager shows 18 MB/s, and your video call still freezes. Understanding the difference between rated bandwidth and real-world throughput — and knowing how latency, overhead, and connection type each play a role — helps you choose the right plan, diagnose slowdowns, and set realistic expectations for every device in your home.

Why Your Download Is Slower Than Advertised

The most common source of frustration with internet speeds is the gap between advertised and real-world performance. A 100 Mbps plan rarely delivers 100 Mbps at your device, and there are several compounding reasons why. The first is the bits-to-bytes conversion: 100 Mbps theoretically downloads at 12.5 MB/s, not 100 MB/s, which surprises users who read ISP speeds in Mbps but see download managers report in MB/s. The second is TCP protocol overhead, which consumes roughly 3–10% of raw bandwidth on every connection to handle packet acknowledgment and error correction.

Wi-Fi introduces additional losses that vary dramatically by environment. Even a router positioned in the same room on an uncrowded 5 GHz band may deliver only 70–80% of its wired throughput; on a crowded 2.4 GHz band shared with neighbors, you might see 40–60%. Walls, floors, and appliances attenuate the signal further. Finally, the server you are downloading from has its own upload capacity and may throttle connections to manage load. For practical planning, assume 70–85% efficiency on a home broadband connection on Ethernet, and 50–70% on Wi-Fi — which is what the efficiency slider in this calculator lets you calibrate.

Choosing the Right ISP Plan

The FCC defines broadband as 25 Mbps down and 3 Mbps up — a threshold appropriate in 2015 that feels cramped in households with multiple simultaneous users today. For a single person doing light browsing and HD streaming, 25–50 Mbps is genuinely sufficient. For a household of four to five people streaming 4K video, gaming online, and working from home simultaneously, 200–500 Mbps is more realistic. The key insight is that bandwidth needs are roughly additive for simultaneous activity: if everyone is doing something at the same time, you need the sum of all individual requirements plus a buffer for background device traffic.

When comparing plans, pay close attention to upload speed, which asymmetric cable and DSL plans often limit to 10–20 Mbps even at high download tiers. If your household has anyone working from home, making frequent video calls, backing up to cloud storage, or sharing large files, the upload limit can be a more painful bottleneck than the download speed. Fiber plans — typically symmetric with equal upload and download speeds — are worth the premium for upload-intensive households even if the download speed is comparable to a cable alternative.

Bandwidth vs. Latency: Two Different Problems

Bandwidth and latency are frequently confused but describe completely different qualities of a network connection. Bandwidth is capacity — how much data can flow per second, like the width of a highway. Latency is delay — how long it takes for a single packet to make a round trip between your device and a server, measured in milliseconds. A high-bandwidth connection with high latency feels sluggish for interactive tasks even when file downloads are fast.

Satellite internet illustrates this contrast clearly. A modern low-Earth-orbit satellite service like Starlink delivers 100–200 Mbps of bandwidth — adequate for most households — but with latency around 20–40 ms, which is reasonable. Older geostationary satellite services had 20–50 Mbps bandwidth but 600 ms or more of latency, making video calls and online gaming nearly unusable despite adequate download speeds. For streaming and bulk downloads, bandwidth is the dominant factor. For gaming, VoIP, video conferencing, and any application where you send a command and wait for a response, latency below 50 ms is the critical requirement — and no amount of additional bandwidth compensates for high latency in those use cases.

Upload Speed: The Forgotten Half of Your Connection

Most consumers focus exclusively on download speed when choosing an internet plan, but upload speed has become equally important for a large share of users. Video conferencing sends your camera feed upstream at 1.5–4 Mbps per call in HD, and 4K calls require even more. Cloud storage services like iCloud, Google Drive, and Dropbox continuously upload new and modified files in the background. Content creators uploading video to YouTube or Vimeo routinely push files of 5–50 GB. Remote work over VPN involves constant two-way data exchange. In all of these cases, a plan with 200 Mbps download but only 10 Mbps upload creates a real-world bottleneck that no amount of download headroom can fix.

Cable internet uses DOCSIS technology that is fundamentally asymmetric — the physical channel allocation reserves much more capacity for downstream traffic than upstream. This is a deliberate engineering choice made when cable plants were designed for a consumption-first internet, and it cannot be fully overcome with a software upgrade. Fiber-optic connections, by contrast, use symmetric capacity by default. If your household frequently saturates upload speed, switching to a fiber plan or a business-grade cable tier with higher upload allocations will produce more tangible improvement than doubling your download speed.

Bits, Bytes, and the Units Confusion

The most common source of bandwidth confusion — and one that regularly causes people to think their ISP is cheating them — is the distinction between bits and bytes. ISPs advertise in megabits per second (Mbps) because the numbers are eight times larger than megabytes per second (MB/s), and larger numbers look more impressive in marketing. Download managers, file explorers, and cloud services typically report in MB/s because file sizes are measured in bytes. A 100 Mbps connection downloads at a maximum of 12.5 MB/s — divide the Mbps figure by 8 to convert.

A second layer of confusion comes from the difference between decimal and binary prefixes. Network equipment and ISPs use decimal: 1 Mbps = 1,000,000 bits per second, and 1 GB = 1,000,000,000 bytes. Operating systems historically used binary: 1 MB = 1,048,576 bytes and 1 GB = 1,073,741,824 bytes. Windows Explorer and macOS both report file sizes in binary gigabytes. This means a file that Windows reports as 4.7 GB actually contains 4.7 × 1,073,741,824 = 5.05 billion bytes, and dividing by your decimal Mbps speed gives a slightly longer transfer time than a naive calculation would suggest. This calculator handles the conversion correctly using binary file sizes and decimal network speeds.