Freezing, Buffering or Pixelation: What Each Symptom Actually Means
Three symptoms that look similar and have completely different causes. How to tell them apart in under a minute, and what each one is telling you about your setup.
People report all three as 'buffering' and they are not the same problem. Each one points at a different part of the chain, and knowing which is which skips most of the guesswork.
Troubleshooting · 2026-09-09 · 5 min read
The three symptoms are not interchangeable
Almost every support message in this category says 'buffering', and most of them describe something else. The distinction matters because each symptom points at a different link in the chain, and treating one as another sends you troubleshooting the wrong thing entirely.
- Buffering — the picture stops, a spinner appears, playback resumes. Data is not arriving fast enough.
- Freezing — the picture stops with no spinner, audio may continue, and it does not recover on its own. The player has lost the stream.
- Pixelation — playback continues but the image breaks into blocks. Data is arriving damaged or incomplete.
Buffering means throughput
A spinner is the player telling you it has run out of buffered content and is waiting. That is a bandwidth or congestion problem between the source and your device, and the great majority of it is inside your own home or on your neighbourhood segment.
Test it by watching the same channel at midday. If midday is clean and 8pm is not, you have found it: peak congestion, not a fault. Nothing about the service will change that, and a wired connection to the television is the single most effective fix available to you.
Freezing means the connection dropped
A frozen frame with no spinner usually means the player's connection to the stream ended and it has not noticed yet. Audio continuing for a few seconds after the picture stops is the classic signature.
This is more often the player or the device than the network. Try the same channel in a different app on the same device — if the second app plays it, you have a client problem, and either changing player or clearing its cache will fix it. If both freeze at the same point, it is upstream.
Pixelation means damaged data
Blocky artefacts during motion, or a picture that dissolves into squares and reassembles, means packets are arriving corrupted or out of order. On Wi-Fi this is interference; on cable it can be a genuine line fault, and on fixed wireless it is often weather.
The useful test is to compare a wired device with a wireless one at the same moment. Pixelation that disappears over Ethernet was interference. Pixelation that persists on Ethernet is a line problem worth raising with your ISP, because it will be affecting more than streaming.
One symptom that is not a fault at all
If films and dramas are perfect and fast-moving sport falls apart, nothing is broken. Rapid motion needs two to three times the bitrate to encode cleanly, so a connection with just enough headroom for a drama runs out during a fast break.
The fix is the same as for buffering — reduce jitter, wire the device — but the diagnosis is different, and it is worth knowing before you conclude a service cannot carry sport.
Questions
Why does it only happen on one channel?
A single misbehaving channel is not a systemic problem and no amount of network work will fix it. Report the specific channel name and time — that is something a provider can actually act on, unlike a general report of buffering.
Does restarting the router really help?
More often than it should, and it is worth doing properly: power off for a full two minutes so the connection renegotiates rather than resuming. Restart the router first, the streaming device second.