Quick answer
Buffering does not mean “slow internet”. It means the player has run out of already-downloaded segments and is waiting for the next ones. There are three possible causes, and they should be ruled out in this order:
- The local network, meaning the Wi-Fi between router and device. It is the most frequent cause and the easiest to check.
- The device, when it cannot decode the stream or runs out of memory.
- The source, when the server is saturated or too far away. There is nothing you can do about this one.
The headline speed of your line is nearly always beside the point: a steady 30 Mbit connection works better than a gigabit one with weak Wi-Fi.
How much bandwidth you actually need
Far less than people assume. The typical orders of magnitude for a live channel:
| Quality | Indicative bandwidth required | Notes |
|---|---|---|
| SD (standard definition) | 2–4 Mbit/s | Enough on any recent line |
| HD 720p | 4–6 Mbit/s | The most common quality in live broadcasts |
| Full HD 1080p | 6–10 Mbit/s | Depends heavily on the bitrate the source chooses |
| 4K | 20–30 Mbit/s | Rare in live broadcasting |
These are indicative figures: the real bitrate is set by whoever is transmitting. The important point is that almost no Italian line in service today is too slow for HD IPTV. If you are having trouble on a 100 Mbit line, the bottleneck is somewhere else.
The diagnostic procedure
- Connect the device by cable, if only as a test. If the problem disappears, Wi-Fi was the cause and the diagnosis ends here. This is the most frequent outcome.
- Try the same source on another device, ideally on the same wired network. If it works there, the problem is the first device — memory or codecs.
- Try another channel from the same list. If the others run, the problem is that one stream, not your network.
- Try the same source at a different time of day. If the stalls cluster in the evening or during sporting events, the server is saturated: no setting of yours can make up for it.
- Reduce the load on the app: fewer days of programme guide, unwanted channel groups hidden, background apps closed.
By the end of those five steps the cause is nearly always identified, and it is rarely the one suspected at the start.
Wi-Fi, the usual culprit
Wi-Fi is unstable by nature: the bandwidth is shared, walls attenuate the signal, and radio channels interfere with the neighbours'. Continuous streaming is the load that suffers most from these variations, because it tolerates no interruptions.
What makes a difference, in order of effectiveness:
An Ethernet cable. It solves the problem rather than easing it. If the device has no port, many support a USB adapter. On televisions the port is nearly always there and nearly always ignored.
The 5 GHz band. Less crowded than 2.4 GHz and faster, in exchange for shorter range. For a television in the same room as the router it is the right choice.
Where the router sits. A router inside a closed cabinet, behind a television or two walls away loses a great deal. Moving it costs nothing.
Powerline. Where a cable cannot be run, adapters over the mains are a better compromise than weak Wi-Fi, provided they are on the same circuit.
When the device is the problem
You can recognise it from specific signals: the app closes on its own, the device gets hot, the picture stutters regularly instead of stopping outright, or the problem affects only the high-definition channels while the others run.
There are two causes. Insufficient memory for long playlists and an extensive programme guide — dealt with by reducing the load, as described in the EPG guide. And software decoding, when the stream's format is not handled by the chip: in that case the processor does the work, heats up and falls behind. No setting fixes it; a different device is needed, and the criteria are on the page about boxes and set-top boxes.
When the source is the problem
If every check on your side comes back clean and the stalls cluster at particular times, the limit is upstream. A server handling more connections than it can carry degrades for everybody at the same moment — typically in prime time and during sporting events.
It is also the characteristic behaviour of unauthorised services, which besides being frequently undersized are cut off by blocking orders during live broadcasts specifically. If the interruptions coincide systematically with events, the explanation is not technical: it is the one described in the guide to legal IPTV.
Frequently asked questions
How do I improve IPTV picture quality?
You cannot: quality is decided by the source. All you can do is stop the player dropping to a lower quality for want of bandwidth, by keeping the connection steady.
Why does IPTV only stall in the evening?
Because at peak times the load on your network, on your provider's network and on the source's server all add up. Coinciding with sporting events nearly always points to the third.
Does increasing the player's cache help?
A margin of a few seconds absorbs micro-interruptions and is worth having. Very high values simply lengthen the initial wait and consume memory.
Does mesh Wi-Fi fix it?
It improves coverage, which helps if the problem is distance from the router. It adds no bandwidth and does not remove the inherent instability of Wi-Fi.
How fast does my line need to be for IPTV?
A few stable megabits are enough for high definition. Steadiness counts for more than peak speed.