What internet speed do you need for IPTV?

Allow 10 Mbps per 1080p stream and 25 Mbps per 4K stream, add up the streams that genuinely run at the same time, and compare that to your plan. A household watching one 4K feed while someone else watches 1080p and a third person is on a video call wants somewhere north of 45 Mbps, and almost every modern plan clears that on paper.

Which is exactly why the sum rarely explains the problem. Most people asking this question are already on 100 Mbps or better and still watching a match stutter, and being told to add up streams does not help them. The rest of this page is about the half that does.

A standard speed test opens several connections to a nearby server and reports the fastest few seconds. Live television does close to the opposite: one continuous connection to a distant server, held open for two hours, needing a modest amount of data to arrive without interruption. A line can be excellent at the first and mediocre at the second.

This is why a result of 300 Mbps sits so oddly next to a channel that keeps freezing, and why upgrading the plan so often changes nothing. The test answered a question you were not asking. What you want to know is whether the connection is steady, not whether it is fast.

The measurements that predict live streaming quality are jitter and packet loss. Jitter is the variation in how long packets take to arrive: when it rises, data that was sent evenly arrives in clumps, the player drains its buffer waiting for the gap to fill, and you get the freeze-then-catch-up behaviour familiar to anyone who watches live sport. Packet loss is data that never arrives at all, which produces blocking and audio dropouts rather than pausing.

Both can be bad on a fast line and fine on a slow one. A stable 40 Mbps connection will carry live television more reliably than an erratic 300 Mbps one, which is the single most counterintuitive fact in this whole subject and the reason speed alone is a poor predictor. Most speed tests report jitter somewhere in the results; it is worth finding, and single-digit milliseconds is what you want.

Three changes make a speed test meaningful for this purpose. Run it at the hour that fails, which for most households is between eight and eleven in the evening, because a line that is clean at noon and congested at nine tells you the problem is contention rather than capacity. Run it from the device you watch on rather than from a laptop next to the router, because that is the path the stream takes. And run something long rather than something quick.

That last one matters most. A test lasting eight seconds says almost nothing about a two-hour broadcast. If your speed test offers an extended or continuous mode, use it; if not, streaming a long video at high quality and watching whether it holds is a rougher but more honest proxy. What you are looking for is not a peak figure but whether the line dips.

Before blaming the line, establish whether the line is the problem at all. The most common cause of an inadequate connection is a good one degraded on the way to the television: an older Wi-Fi standard, a 2.4 GHz band shared with every neighbour, distance through two walls, or a streaming stick with a weak aerial. A 500 Mbps plan delivering 12 Mbps at the TV is an ordinary result, not an unusual one.

The test that settles it takes two minutes: run the speed test on a phone standing next to the router, then again in the room with the television. If the second number collapses, the problem is your home network, and a network cable to the main television is the single largest improvement available. Nothing else on this page produces a change of that size.

For one household watching live television, 50 Mbps is comfortable for a couple of simultaneous 1080p streams and 100 Mbps is comfortable for a mixed household with 4K in it. Beyond that, extra headroom buys very little for this purpose, because live streams are modest consumers and the constraints that break them are not capacity.

If you are already above those figures, the answer to a stuttering picture is not a bigger plan. Spend the money on a wired connection to the television or a better access point instead, and if the line is genuinely steady and the problem persists at peak hours, the constraint has moved to the provider rather than to you.

Three patterns rule out bandwidth entirely. If one channel fails while others on the same lineup are perfect, that is a single feed, not your line. If everything is fine until nine in the evening and then degrades on schedule, that is congestion somewhere upstream, and your own capacity is not the variable. And if it fails identically on cellular data with the Wi-Fi off, your home connection has been eliminated as a cause.

That third test is the most useful ten seconds in this whole diagnosis, because it cleanly separates your network from everything beyond it. If the symptom follows you onto a completely different connection, no amount of money spent on your line will address it, and the buffering guide on this site covers what to do next.