Why does Netflix buffer only on my smart TV when the same account streams normally on other devices? I’ve restarted both the TV and router, signed out of Netflix, and reinstalled the TV app. The TV’s network test reports 73 Mbps, and buffering happens on both Wi-Fi and Ethernet, usually within 7 minutes.
Other streaming apps on the TV appear stable. Is there a TV-specific Netflix setting, cache issue, or diagnostic step I should check next?
73 Mbps doesn’t rule out a TV-side problem. That test may hit a nearby server, while Netflix uses a different route and video decoder. Run an internet speed test in the TV’s browser during the slowdown, but focus on large speed swings or packet loss rather than the headline number.
Do a real cold restart next: disable the TV’s Quick Start/Instant On feature, unplug it for two minutes, then check for TV firmware updates and verify its date and time are automatic. In Netflix, open Get Help and run Check Your Network if that menu is available.
The quickest isolation test is connecting the TV to a phone hotspot for 10 minutes. If Netflix still buffers around the same point, the TV’s Netflix app, firmware, decoder, or DRM stack is the likely culprit. If it works normally on the hotspot, try changing the router’s DNS or disabling IPv6 temporarily. As a practical workaround, an external streaming stick may be easier than fighting an aging built-in TV app.
The Netflix account isn’t the likely cause; the TV may be stuck on crowded 2.4 GHz Wi-Fi while your other devices use 5 GHz. Check the router’s connected-device list, then move the TV to 5 GHz or test with Ethernet if possible.
Connect the TV to a phone hotspot for a few minutes and try Netflix. If it still buffers, the problem is likely the TV’s app, firmware, or limited hardware rather than your home Wi-Fi. @binaryotter’s band suggestion is plausible, but this test isolates it faster. Speedtest by Ookla in the TV browser can help too, though TV browser results aren’t always very accurate.
The hidden catch is that the TV may be requesting a much heavier stream than your other devices. A phone or laptop might be playing 1080p, while the TV automatically selects 4K, HDR, or a higher bitrate. Same account, same router, very different workload.
Try this in order:
Play the exact same Netflix title on the TV and another device. Pick something that is available in 4K on the TV.
From Netflix in a computer or phone browser, change that profile’s playback data usage from Auto/High to Medium.
Wait a few minutes, restart the TV app, and test again.
Then try an older HD-only title. If HD plays cleanly but 4K content buffers, you have narrowed it to sustained bandwidth, Wi-Fi stability, or the TV struggling with the higher-quality stream.
This is why I would not put too much weight on the reported 73 Mbps. That is enough on paper, but a short speed test can look fine while the connection has brief dropouts. Netflix fills a buffer and then drains it, so even small interruptions can produce repeated pauses. If the TV has an Ethernet jack, a temporary cable across the room is a useful test. It does not need to become the permanent setup.
If lowering playback quality changes nothing, check the TV’s free storage and remove a couple of unused apps. Some smart TVs behave badly when internal storage is nearly full, and reinstalling Netflix may not clear every cached system component. Avoid a factory reset until last because it wipes logins, picture settings, channel setup, and other configuration.
The hotspot test suggested earlier still makes sense, but run it with the same title and playback-quality setting. Otherwise you may accidentally compare a lower-quality cellular stream with a 4K home Wi-Fi stream. If it buffers on the hotspot even at Medium quality, the built-in app or TV hardware becomes the strongest suspect. At that point, an external streamer is usually the least frustrating fix rather than repeatedly resetting a TV that otherwise works.
Don’t factory-reset the TV or replace it with a streaming stick yet. First check whether the router sees that TV as more than one device. Smart TVs sometimes keep separate entries for wired, 2.4 GHz, and 5 GHz connections, and an old entry can retain a bandwidth limit, guest-network rule, or low-priority QoS setting.
If you use a mesh system or “Smart Connect” band steering, watch the router’s device list while Netflix is buffering. A stationary TV can still bounce between access points or bands because its Wi-Fi antenna is stuck behind a large screen and close to the wall. Lock it to the nearest mesh node if your router allows that. Otherwise, temporarily split the Wi-Fi bands into separate names and connect the TV manually. Use 5 GHz when the router is nearby, but try 2.4 GHz if several walls are involved. A weak 5 GHz connection can test fast for a few seconds and then fall apart during sustained playback.
I’d also remove the TV’s saved network completely, reboot the router, and reconnect it from scratch. That forces a fresh DHCP lease and clears odd settings that survive reinstalling Netflix. If you test Ethernet, forget or disable Wi-Fi on the TV during the test so there is no doubt which connection it is actually using.
The hotspot suggestion is useful, but passing that test does not automatically prove the home internet route is bad. A phone sitting next to the television may simply provide a much cleaner radio signal, and Netflix may choose a lower bitrate over cellular. It is still a worthwhile isolation test, just not a perfect verdict.
Finally, play a high-quality stream in another app on the same TV for 20 minutes. If that buffers too, concentrate on the TV’s network connection, mesh assignment, or router rules. If other apps hold 4K without a problem and only Netflix stalls, then the built-in Netflix client or the TV’s system software becomes the more likely fault. At that point an external streamer is a reasonable workaround, but it should come after ruling out a per-device router setting.
Don’t lean on the TV’s built-in network test for anything. That check usually just confirms it can reach Netflix, not whether it can hold a steady stream, so a passing result tells you almost nothing here.
@fusionthinker2129 nailed the part everyone else circled around: the TV is probably pulling a much heavier stream than your phone or laptop. That’s the first thing I’d verify before touching bands, DNS, or DHCP leases. Drop the profile’s playback quality to Medium from a browser, give it a few minutes, and see if the buffering stops. If it does, you’ve got your answer without unplugging anything.
The speed test tool that came up earlier is fine for spotting packet loss or wild swings, but the number itself won’t explain a 4K stall. Same with the hotspot test, it’s useful but cellular often quietly serves you a lower bitrate, so passing it isn’t proof your home line is clean. I’d exhaust the quality-cap route first since it costs nothing and takes two minutes.
You may not get a single smoking-gun result from that 73 Mbps reading. Before changing more network settings, make sure this is actual buffering. A loading spinner or a percentage counter points to the connection or Netflix app. Choppy motion, repeated frames, or a frozen picture while audio continues is more likely a decoding or TV processing problem, even though it can look like buffering.
The quality-limit test suggested above is useful, but compare an ordinary HD title with a 4K HDR title and note exactly what happens. If only HDR or Dolby Vision content fails, try disabling the TV’s motion smoothing, noise reduction, and other heavy picture processing for that input/app. If every title shows a loading spinner, then Ethernet or the hotspot test is the cleaner next step.
I would avoid a factory reset until you have made that distinction. A reset will not fix weak Wi-Fi, and it may do nothing for a decoder limitation. If Netflix alone produces real loading pauses on both Ethernet and a hotspot while other TV apps stream normally, the built-in Netflix client is the likely dead end.
Whether this happens on every title matters. If it stalls at the same timestamp in one episode, skip ahead or try another title since that points to a TV-app/encode glitch; random pauses across everything point back to the TV’s connection or hardware.