Almost every bandwidth question contains the same hidden trap: confusing bits with bytes. Get that one conversion right and the rest of the arithmetic is easy — but the gap between the arithmetic answer and the real world is where the actual surprise lives.
The factor of eight
Bandwidth is quoted in bits per second (Mbps, Gbps) and file sizes are quoted in bytes (MB, GB). There are 8 bits in a byte, so:
MB/s = Mbps ÷ 8
100 Mbps is 12.5 MB/s. Not 100. This single conversion changes most people's expectations: a 1 GB file at 12.5 MB/s takes 80 seconds, and at "100 MB/s" that people imagine, it would take 10.
Worked example, 4K film at 20 GB: at 100 Mbps (12.5 MB/s) it takes 20,000 MB ÷ 12.5 = 1,600 seconds ≈ 27 minutes. On a 1 Gbps line (125 MB/s) it takes 2.7 minutes. A tenfold line improvement is a tenfold time improvement — but the absolute numbers only become believable once the factor of 8 is applied.
Why the real number is always lower
Advertised speed is the theoretical link rate. What you get is that number multiplied by several factors, each below 1:
- Protocol overhead, 5-15%. Every packet carries addresses, checksums, retransmission logic and framing. That overhead is part of the pipe and is not carrying your data.
- Contention. A "100 Mbps" line is usually 100 Mbps up to a node shared with other customers. At peak hours this is the dominant loss.
- Wi-Fi, if you are on it. A 1200 Mbps access point rarely sustains more than 400-600 Mbps on a single client, and the gap widens with distance, walls and interference.
- The far end. Beyond a certain speed, the server or your own disk is the bottleneck. Downloading from a fast CDN to a slow drive is limited by the drive.
The practical planning figure is 70-80% of rated speed for a wired single-user transfer, and less for anything shared. The download time calculator applies an overhead factor for exactly this reason.
What each activity actually needs
- 720p video call: 1.2 Mbps per participant
- 1080p video call: 2.5 Mbps per participant
- 1080p streaming: about 3 Mbps, with peaks higher
- 4K streaming: about 7 Mbps, peaks to 15
- Cloud backup of 1 TB/month: only 3 Mbps on average — but it competes with everything else if it runs during working hours
- Video upload of a 4 GB file: dominated entirely by upload speed, which is often 10-20x lower than download
Peak matters more than average. A connection that comfortably supports three 1080p calls at average load may fail the moment a fourth person joins, because the three existing streams are near their nominal rate and the fourth needs its own allocation on top.
Asymmetric connections, and why it bites
Most consumer connections are asymmetric — 1000/50 means a gigabit down and 50 Mbps up. The asymmetry is architectural, not a throttling decision: the upstream path was provisioned for a small share of the traffic because historically downloading dominated.
The consequence shows up exactly when it is most annoying. A 4 GB video upload at 50 Mbps (6.25 MB/s) takes 4,096 MB ÷ 6.25 = 655 seconds ≈ 11 minutes, versus about 32 seconds on the 1 Gbps download side. A video call needs only 2.5 Mbps up, so ten simultaneous calls would saturate a 50 Mbps upload while leaving gigabit download idle.
Planning for a household
Multiply the per-person requirement by the number of concurrent users, then add headroom:
plan = peak concurrent demand ÷ target utilisation (0.7-0.8)
A household of four where two people work remotely with calls (2 × 2.5 = 5 Mbps), one is streaming 4K (7 Mbps) and someone is backing up (3 Mbps) has a peak of 15 Mbps. At 75% utilisation you need 20 Mbps, so a 25-50 Mbps line gives genuine headroom. A 100 Mbps line is comfortable; the 1 Gbps tier is rarely needed for a home unless there is local content or several simultaneous 4K streams.
Upload, and the number that decides whether video calls work
Most households never look at the upload figure until something fails, and the failure is always sudden: a call that was fine starts dropping frames, or a large file that should take a minute takes an hour.
The arithmetic is asymmetric in a way that surprises. On a 1000/50 Mbps line — a gigabit down, 50 Mbps up — the download side is 125 MB/s and the upload side is 6.25 MB/s, a ratio of 20 to 1. Uploading a 4 GB video takes 4,096 ÷ 6.25 = 655 seconds, about 11 minutes, while downloading 4 GB would take 33 seconds. The same file, the same connection, a factor of 20.
For calls, upstream is the constraint. A 1080p call needs about 2.5 Mbps per participant, so a 50 Mbps upload supports roughly 20 participants on paper and, with overhead and contention, about 8-10 in practice. The gigabit download is irrelevant to that calculation entirely.
How long a transfer really takes, step by step
The download time calculator applies a 5-15% overhead factor. Worked example, 700 MB at 100 Mbps nominal:
- Theoretical: 700 MB ÷ 12.5 MB/s = 56 seconds
- With 8% overhead: 56 ÷ 0.92 = 60.9 seconds
- On a busy evening with two other devices: maybe 75-90 seconds
The step people forget is the third one. Overhead is a fixed, predictable loss; contention is variable and depends on everyone else. This is why a speed test run at 3am is not a useful predictor of 8pm.
Latency is a different number from bandwidth
Bandwidth is how much per second; latency is how long for the first byte. They are independent, and a link can have excellent bandwidth and unusable latency — which is what satellite internet has been for years, and what makes a remote terminal feel wrong even on a fast connection.
- Good for calls and gaming: under 50 ms
- Noticeable lag in conversation: 100-200 ms — people start talking over each other because the natural turn-taking window assumes under 200 ms
- Unusable for anything interactive: above 400 ms
Latency is dominated by physical distance at a rate of about 20 ms per 1,000 km of fibre, plus a fixed 5-20 ms for the routing equipment at each end. This is why a server in another continent can never be made to feel local, and why content delivery networks exist.
What actually determines the plan you need
Add the peak concurrent demand and divide by a target utilisation of 0.7-0.8:
required = peak demand ÷ 0.75
A household with two remote workers on 1080p calls (2 × 2.5 = 5 Mbps), one person streaming 4K (7 Mbps) and a nightly backup running (3 Mbps) peaks at 15 Mbps. Dividing by 0.75 gives 20 Mbps, so a 25-50 Mbps line is a genuine fit. Going to 100 Mbps buys headroom for guests and a future; going to 1 Gbps is rarely justified for a home unless there is local media or several simultaneous 4K streams.
Where the money actually goes
For most households the bill is driven by one of three things, and it is worth identifying which before comparing plans:
- Upload-heavy households — working from home with large file transfers, cloud backups, video calls. Look at the upload figure first, since it is usually the constrained side.
- Many simultaneous streams — 4K on several TVs. This is a bandwidth problem with a clear ceiling.
- The price tier itself — providers price tiers well above the technical requirement, so the jump from 100 to 500 Mbps often costs more than it delivers. The bandwidth calculator will tell you which side of that line you are on.
Frequently asked questions
How do I convert Mbps to MB/s?
Divide by 8. 100 Mbps is 12.5 MB/s, 1 Gbps is 125 MB/s. The conversion is the source of most internet-speed confusion, because download tools show MB/s while providers advertise Mbps.
Why is my internet slower than the speed I pay for?
Protocol overhead takes 5-15%, contention with other devices and the ISP's shared capacity takes more, and Wi-Fi loses a further 50%. Measuring on a wired connection at 3am is the only way to see the line's real capability.
Is latency or bandwidth more important for video calls?
Latency. A call needs only about 2.5 Mbps but needs under 50 ms of latency, and the two are unrelated — satellite broadband has high bandwidth and 600 ms latency, which is why video conversation on it is awkward.
How much bandwidth does a household of four need?
Add the peak concurrent demand and divide by 0.75 for headroom. Two video calls (5 Mbps) plus a 4K stream (7 Mbps) plus a backup (3 Mbps) peaks at 15 Mbps, so 20 Mbps is the requirement and a 25-50 Mbps plan is the sensible fit.
Frequently asked questions
Is 100 Mbps the same as 100 MB/s?
No. 100 Mbps is 100 megabits per second, which is 12.5 megabytes per second. The factor of 8 exists because a byte is 8 bits, and it is the single most common confusion in internet speed. A 100 Mbps line downloads a 1 GB file in about 80 seconds, not 10.
Why is my actual download speed lower than the advertised speed?
Several things: protocol overhead of 5-15%, contention from other devices and applications, the ISP's own capacity being shared, and for very high speeds the storage or server on the other end becoming the bottleneck. A connection rarely sustains more than 80-90% of its rated speed.
How much bandwidth does video streaming need?
About 3 Mbps for 1080p, 7 Mbps for 4K, and 1.2 Mbps for a 720p video call. Plan at roughly 70% of your capacity so the connection holds up when everyone is using it at once — peak contention is what makes a plan feel inadequate.
Why is upload speed so much slower than download?
Most connections are asymmetric by design, often by a factor of ten or more, because the upstream path was provisioned for a much smaller share of the traffic. This is why a fast download line can still fail at a video call or a large cloud backup.