Short answer: buffering has five common causes, and they produce different symptoms. Work through them in order — local Wi-Fi, device capability, network path, the source itself, then player configuration — because fixing the wrong one wastes money. Most people blame their internet speed, and most of the time raw speed isn't the problem.
First, rule out the cheap explanation
Netflix publishes its recommended speeds: 3 Mbps for 720p, 5 Mbps for 1080p, and 15 Mbps for 4K. Those are per stream. If you're paying for 300 Mbps and buffering on 1080p, bandwidth is not your constraint and upgrading your plan will change nothing.
What matters more than peak speed:
- Consistency. A connection averaging 100 Mbps that drops to 3 Mbps for two seconds will stall a stream. Average speed hides this entirely.
- Latency and jitter. Variable delay disrupts segment delivery even when throughput looks fine.
- Congestion timing. If buffering clusters around 8–11pm, you're seeing contention — either in your home or at your ISP's local node.
Run a speed test — Fast.com is run by Netflix and measures against its own servers — while the stream is buffering, not afterwards. A test run on an idle connection tells you almost nothing about conditions during playback.
Symptom-to-cause table
| What you see | Most likely cause | What to check |
|---|---|---|
| Buffers every few minutes, all content | Wi-Fi signal or interference | Signal strength at the device; try ethernet |
| Only 4K buffers, HD is fine | Bandwidth or device decode limit | Force a lower quality; check codec support |
| Fine for 20 min, then stalls | Device thermal throttling or memory | Touch the device; restart and retime it |
| Only at peak evening hours | ISP congestion or source overload | Test the same content at 3am |
| One channel or title only | Source-side problem | Nothing on your end will fix it |
| Audio continues, video freezes | Decode failure, not network | Check codec compatibility |
That last row is worth internalising. If audio keeps playing while video stops, data is still arriving — the problem is your device's ability to decode it, not the connection.
Wi-Fi is the usual culprit
In most homes the weakest link sits between the router and the device, not between the house and the internet.
Get the device onto ethernet, even temporarily with a long cable across the floor. If buffering disappears, you've found it, and everything else is a distraction. Streaming boxes and smart TVs frequently have poor antennas — a device two rooms from the router may be running at a fraction of the rate a phone gets standing beside it.
If ethernet isn't an option: use 5 GHz rather than 2.4 GHz where the distance allows, since 2.4 GHz is congested by microwaves, baby monitors, Bluetooth and every neighbouring network. Move the router off the floor and out of cabinets. And check how many devices are active — a household backing up phones to cloud storage during the evening is competing with your stream.
Device limits people miss
Codec support is binary. A device either decodes a codec in hardware or it doesn't. Software decode on an older device produces stutter that looks exactly like a network problem. If content encoded in AV1 or HEVC stutters while H.264 content plays perfectly, that's the answer — no network fix will help. (More on why services are moving to AV1, and why H.264 isn't going away, in IPTV in 2027.)
Thermal throttling has a signature. Works fine for 20 minutes, degrades, then recovers after a rest. Small streaming sticks tucked behind a TV, in still air, are the usual victims. Move it where air circulates or add an extension so it hangs free.
Cheap devices run out of memory. Background apps on a budget Android box leave little headroom for buffering. Restarting before a long watch is a crude fix that works more often than it should.
When the problem isn't yours
Some buffering originates at the source, and no amount of local troubleshooting touches it.
Signs it's upstream: the same content buffers on a different device on a different network; it's confined to specific channels or titles while everything else is fine; it clusters at predictable high-demand times like a major live event; other people report it simultaneously.
The tell-tale one is a stream that fails only during popular live events. That's a source without the capacity — or the CDN arrangement — to serve everyone at once. Live delivery is genuinely hard, and unicast economics get worst precisely when demand peaks.
Test it cleanly: play the same content over mobile data with Wi-Fi off. If it still buffers, the problem is not in your home.
Player settings worth changing
Turn off adaptive quality temporarily. Locking to a fixed lower bitrate tells you whether the player is thrashing between renditions. Constant quality switching looks like buffering and is often mistaken for it.
Increase the buffer if the option exists. Many players let you trade latency for stability. On anything that isn't live, a larger buffer is almost always the right trade — a few seconds of delay costs nothing when nobody's racing a live broadcast.
Try a different player on the same device. Players vary widely in buffer handling and codec support. If one stutters and another doesn't on identical content, the player was the problem.
A sensible order of attack
- Play the same content on a phone over mobile data. Still bad? The source is the issue and you can stop.
- Plug the device into ethernet. Fixed? It's Wi-Fi.
- Drop to a lower quality. Fixed? Bandwidth or decode capability.
- Try a different player. Fixed? Player configuration.
- Restart the device and watch whether it degrades again after 20 minutes. Recurring? Thermal or memory.
Each step eliminates a category. Stop at the first one that changes the behaviour.
What not to bother with
Upgrading your internet plan before establishing that bandwidth is the limit. It's the most expensive guess available and rarely the right one.
Wi-Fi extenders, without checking first whether signal strength is actually low. A badly placed extender halves throughput by repeating traffic on the same channel.
VPNs marketed as buffering fixes. A VPN adds a hop and usually reduces throughput. It can occasionally help if your ISP is throttling specific traffic, but that's a narrow case worth verifying rather than assuming.
"Optimizer" apps on streaming devices. Clearing cache is the one thing they do that matters, and you can do that in settings.
Quick answers
Does more internet speed stop buffering? Only if bandwidth is the constraint, which it usually isn't above about 50 Mbps for a single 4K stream.
Why does it only buffer in the evening? Congestion, either at your ISP's local node or at the source. Test the same content overnight to tell which.
Why does audio keep going when video freezes? Data is still arriving, so it's a decode problem, not a network one.
Is ethernet really that much better? For a fixed device, yes — it removes the most common failure point entirely.