Your connection has a number on the bill and a different number in practice
A video stream doesn't behave like a downloaded file — there's no waiting a little longer if the connection dips. It needs a continuous, uninterrupted flow of data for the entire runtime, and even a brief drop below that floor shows up on screen immediately as a stall or a frozen frame. Understanding what actually causes that gap matters more than memorizing a single speed number.
How much a stream actually needs
| Resolution | Sustained bandwidth needed |
|---|---|
| Standard definition | From roughly 3 Mbps |
| HD (1080p) | Roughly 5–10 Mbps |
| 4K (Ultra HD) | At least 25 Mbps |
Treat these as a floor rather than a fixed rule — actual usage shifts with compression and the specific stream.
Why the number on your bill is misleading on its own
An internet plan's advertised speed is measured under ideal lab-like conditions: one device, nothing else running, tested for a few seconds. None of those conditions describe an ordinary evening at home. The number that actually matters is what one device gets to keep after everything else on the network has already taken its share — and that number is usually smaller, and far less steady, than the one on the bill.
Four things that quietly take bandwidth without announcing it
A phone or laptop mid-download
Automatic app updates and cloud backups run in the background without asking first.
Another screen streaming at the same time
Two 4K streams at once roughly doubles the floor either one needs on its own.
A router several years old
Older hardware sometimes can't push its rated speed to more than a couple of devices at once.
Wi-Fi distance and walls
Signal strength drops faster than most people expect once a device is two rooms from the router.
Testing it the way that actually matters
A speed test run from a laptop sitting next to the router, in the middle of the afternoon, measures a best-case scenario nobody actually watches under. Run the test instead from the exact device that'll be streaming, at the time of day you'd normally be watching, with whatever else usually runs in the background left running. That single adjustment is the difference between a marketing number and a number you can actually plan around.
Telling a bandwidth problem apart from something else
| What you're actually seeing | Most likely cause |
|---|---|
| Plays cleanly at first, then degrades over time | The connection running out of headroom mid-stream |
| Nothing plays from the very first attempt | A login or activation problem, unrelated to speed |
| One app crashes repeatedly but another plays fine | That specific app, not the connection |
A well-built player app responds to a shrinking connection by quietly stepping resolution down, or pausing briefly to refill its buffer, rather than crashing outright — that's the app adapting, not a sign anything is broken. If what you're seeing matches the second or third row above instead, the Setup Guide covers that territory.
Skipping the guesswork entirely
Every number above is still an estimate until it's tested on your own setup. The 24-hour trial puts the real catalog on your actual connection for a dollar — run it at the time you'd normally be watching, and the real answer replaces the estimate.
Related questions
A speed test says I have plenty of bandwidth — so why does it still stutter sometimes?
Because a speed test captures one instant. If someone else in the house starts a download or a video call five minutes later, that available headroom disappears without the number on your bill changing at all.
Does a bigger catalog need a faster connection to stream than a smaller one?
No. Bandwidth demand comes entirely from the resolution of whichever single stream is playing — a 40,000-channel catalog and a 4,000-channel one place an identical load on your connection for the same resolution.