Netflix keeps buffering on a fast plan. The line is almost never the problem.

Streaming video is the easiest thing your internet connection does all day. A 4K Netflix stream wants about 15 megabits per second. A 1080p stream wants 5. Most households are paying for 300 or more. And yet "the show keeps buffering" is still one of the most common complaints about home internet, and the most common response, upgrading the plan, is the one least likely to help.

This guide explains why streaming fails differently from video calls and games, which three problems account for nearly all buffering on a fast plan, how to tell them apart with five tests on this site and the diagnostics built into the apps themselves, and what to change, in order of cost. The TV gets its own attention throughout, because the TV is usually the weakest device in the house.

Why a faster plan almost never fixes it

Start with what the services actually ask for.

Add those up for a busy house. Three simultaneous 4K streams, the worst realistic case, come to about 50 megabits. Hulu notes that viewers can still stream at reduced quality on 1.5 megabits. A 300-megabit plan is not the constraint, and a 1,000-megabit plan is not the solution.

There is a second reason the plan is rarely the issue. Streaming is a download-only activity with a safety margin built in. The player keeps a buffer of video, typically 10 to 30 seconds ahead of what you are watching, and adjusts quality to whatever your connection can sustain (Mux). A brief dip in speed costs you nothing. Latency, the number that ruins video calls and games, barely matters at all, because nobody is waiting for your reply. The upload direction, the narrow lane that starves calls on cable plans, is untouched.

What does break streaming is anything that prevents the buffer from refilling for longer than it holds: a Wi-Fi link to the TV that keeps dropping, a connection that sags every evening at the same time, or a device that cannot keep up. The FCC said this plainly in its broadband measurements more than a decade ago: "consistency of speed may be more important to customers who are heavy users of applications that are both high bandwidth and sensitive to variations in actual speed, such as streaming video" (FCC, 2015). Your plan is a peak number. Buffering is about the troughs.

Two symptoms that are not the same problem

Before testing, notice which of two things is happening, because they point in different directions.

The picture gets soft but keeps playing. The player has lowered quality to stay ahead. This is the adaptive system working as designed. The cause is a sustained throughput shortfall somewhere between the service and the screen, or a device, plan, or browser limit that caps resolution regardless of speed. Steps 1, 2, and 5 below find it.

Playback stops and a spinner appears. The buffer ran dry, which means the connection fell far below the stream's bitrate for longer than the buffer could cover, or stopped entirely for a few seconds. Short, complete interruptions are the signature of Wi-Fi trouble and packet loss, not of slow plans. Steps 2 and 3 find it.

A third pattern, "it buffers on the TV but not on my laptop," is a device problem by definition, and the fastest one to confirm. Step 2 is built for it.

The three causes, and why they hide

The last thirty feet. Your plan delivers speed to the router. The TV gets whatever survives the trip across the room, through a wall, from a radio that was the cheapest component in the set. Many TVs still connect on the crowded 2.4 GHz band, and a TV's antenna sits behind a metal chassis against a wall. Netflix's own troubleshooting for buffering on smart TVs leads with moving the router and the device closer together, keeping the router off the floor, and away from other wireless devices and appliances (Netflix). Netflix also recommends a wired connection "when available" (Netflix). The service that knows the most about buffering is telling you the problem is in the room.

The evening. Cable internet is shared among neighbors on the same node, and the FCC's national measurement program defines the peak usage period as weeknights from 7 p.m. to 11 p.m., the hours it uses for its headline numbers precisely because that is when performance is under the most strain (FCC). Those are also the hours everyone streams. A connection that tests at full speed at noon and buffers at 8:30 p.m. is not inconsistent; it is a congested node, and the proof is a measurement taken at 8:30 p.m.

The device and the chain. This cause has nothing to do with your internet, which is why speed tests never find it. A 4K title will not play in 4K if your plan tier does not include it, if the TV app or browser caps resolution, if the HDMI chain lacks the right copy protection, or if the TV cannot decode the codec the service wants to send. Netflix requires its Premium plan for 4K and HDR (Netflix). Since April 10, 2026, Prime Video has restricted 4K to its paid Ultra add-on, and the Prime Video benefit included with a Prime membership tops out at HD (Amazon). If you upgraded your internet to get sharper Prime Video this year, the thing that changed was the subscription, not your line.

Packet loss deserves a special mention because it is the one network fault that does hurt streaming on a fast plan. Streaming rides on connections that must retransmit every lost packet and slow down each time one goes missing. The classic formula for this behavior says a single connection's maximum throughput falls with the square root of the loss rate; on an ordinary path, a steady 1 percent loss caps one connection at roughly 1.4 megabits (ThousandEyes). Players open several connections and modern protocols soften the effect, but the direction is the same: a connection with 2 percent loss can test at 200 megabits in a burst and still fail to keep a 15-megabit stream fed. The site's Packet Loss card flags anything above 1 percent as worth investigating. For streaming, take that seriously.

Run the streaming audit

Five steps, about twenty-five minutes of attention spread over a day, since one of them has to happen in the evening. Everything runs in a browser on a laptop or phone; the TV cannot run a web test, so the phone stands in for it in Step 2.

Step 1: the baseline, one stream at a time

Open the speed and network report on a laptop or phone sitting next to the router. In Settings, enter your plan's download and upload speeds so the cards grade against what you pay for, set Focus to "Internet speed and my ISP," and switch Speed test mode from Multi-stream to Single-stream. That last setting matters here. The multi-stream test shows what your line can carry with six connections pulling at once, which is a fair picture of the line and a flattering picture of a streaming app. A TV app behaves much more like the single-stream test. If multi-stream says 400 and single-stream says 60, the line is fine and the 60 is still ten times what Hulu wants for 4K; if single-stream reads below about 25, you have found a real constraint and the evening test in Step 3 will tell you whether it is permanent.

Read the Packet Loss card on the same run. Zero is normal. Anything above 1 percent at the router, on a quiet line, is an ISP or modem problem rather than a Wi-Fi one, and worth an Evidence Pack now.

Step 2: the phone next to the TV

This is the test that settles most cases. Take the phone to the couch, or better, hold it where the TV's back panel is. Make sure it is on the same Wi-Fi network the TV uses (if your router broadcasts separate 2.4 GHz and 5 GHz names, join the one the TV is on). Run the same report again with the same settings. Then compare the two runs: speed, Jitter, and Packet Loss.

A modest drop is normal. A large one, or any packet loss that was not there at the router, is the last thirty feet. If the TV is on 2.4 GHz and the phone at the TV's location reads well on 5 GHz but poorly on 2.4, you have the answer and the fix is free (Fix 1). If both bands are poor at the TV's spot, the fix is a cable or a closer access point (Fixes 5 and 7).

Thirty seconds more tells you whether it is the TV itself. Start the show that buffers on the TV, then start the same show on the phone from the same spot. If the phone plays cleanly while the TV stutters, the network at that location is adequate and the TV's radio, app, or processor is the bottleneck (Fix 6).

Step 3: the 8 p.m. run

Choose an evening when the problem usually appears. On a device near the TV, start the Watch monitor on the speed report for 30 minutes, give it a Spot label such as "Couch, 8 p.m.," and leave the tab open. Do the same for 30 minutes one morning with the label "Couch, 9 a.m." If the evening trace sags while the morning trace is flat, your node is congested at peak hours, and no change inside the house will fix it. Export an Evidence Pack from each run. Then use the ISP call script and say the words "peak-hour congestion on my node," which is a condition your provider's engineers recognize and can measure from their side. Two timestamped PDFs showing the same drop at the same hour on different days are more persuasive than any description.

Step 4: read the service's own numbers

The apps know exactly what they are receiving, and most will tell you.

Netflix on a TV or streaming device. From the Netflix home screen, press back to reach the menu, go to Get Help, then Check your Network. The app confirms it can reach Netflix and measures connection speed from the TV itself, which is the only number in this audit that comes from the TV's own radio (Netflix). Compare it with your phone-at-the-TV reading from Step 2. If the phone reads 150 and the TV reads 8, the TV's Wi-Fi is the problem, not the network.

Netflix resolution and bitrate, on any device. Netflix publishes a title called Test Patterns that displays the current resolution and bitrate in the top right corner while it plays (How-To Geek). Add it to your list from a browser, then open it in the TV app (TechRadar). If the 4K episode plays at 1080p on a fast connection, the cap is your plan tier, the TV, or the HDMI chain, not speed. On a computer, an undocumented overlay appears when you press Ctrl+Alt+Shift+D during playback (Control+Option+Shift+D on a Mac) and shows the playing resolution and bitrate; it is not an official feature, so treat it as a check rather than proof (Online Tech Tips).

YouTube and YouTube TV. Right-click the player on a computer, or open the player's More menu on a TV, and choose Stats for nerds. Watch two lines: Connection Speed, which is YouTube's estimate of what your network can support, and Buffer Health, the seconds of video loaded ahead (Google Support). Buffer Health that repeatedly collapses toward zero is a network problem. Dropped frames while Buffer Health stays high is a device problem.

Speed from the service's side. Netflix's fast.com measures your connection directly to Netflix's servers rather than to a neutral test host (Netflix). If this site's speed card reads well and fast.com reads poorly at the same moment, the shortfall is on the path between your provider and Netflix, which is useful ammunition for the ISP call and not something a new router can touch.

Step 5: the chain, from plan to panel

Run the browser media report on the laptop you stream with. Two cards matter. Video Codecs lists which of H.264, HEVC, VP9, and AV1 your browser can decode, using the same checks a streaming site runs before picking a stream; a browser limited to H.264 falls back to larger, lower-quality streams and may never reach the top resolution. Protected Playback shows whether a DRM system (Widevine, PlayReady, or FairPlay) is available; without one, premium titles refuse to play or play at low resolution, and the card notes that for 4K, Edge with PlayReady or Safari with FairPlay is usually required.

That matches what the services publish. On Windows, Netflix plays up to 4K in Chrome and in Edge (with HDR in Edge), but only up to 1080p in Firefox and Opera, and 4K requires a 4K 60 Hz display with an HDCP 2.2 connection and specific hardware (Netflix). On a Mac, Safari reaches 4K, Chrome stops at 1080p, and Edge at 720p (Netflix). Prime Video in any web browser tops out at HD, and on operating systems other than Windows and macOS it is restricted to standard definition (Prime Video). None of these ceilings move with a faster plan.

On the TV side, the chain is plan tier, title, app, HDMI port, cable, and any receiver or soundbar in between. Netflix states that with a streaming stick and an audio receiver, all three devices must support 4K or HDR to get it (Netflix). Finally, check your plan tier against the table above before blaming anything else. A Netflix Standard subscriber and a Prime member without Ultra are both capped at 1080p by contract, on any connection.

Fixes, in order of cost

Fix 1 (free): move the TV to the right band, or move the router

If Step 2 showed the TV on 2.4 GHz with a better 5 GHz reading at the same spot, go into the TV's network settings and join the 5 GHz network. If your router merges the bands under one name and the TV keeps choosing 2.4, most routers let you split them; give the 5 GHz network its own name and join the TV to that. If the signal is weak on both bands, apply Netflix's own advice first: shorten the distance, get the router off the floor and out of the cabinet, and move it away from other electronics (Netflix). A router moved six feet has fixed more buffering than most hardware purchases.

Fix 2 (free): stop the evening competition inside the house

Cloud backups, game downloads, and OS updates tend to schedule themselves for the evening too. A single large download sharing the line with a 4K stream will take its share, and on routers without smart queue management it will also inflate delay for everything else. Schedule backups and console downloads for overnight. If your router offers SQM, FQ_CoDel, or "Smart Queue," turn it on; the bufferbloat guide explains the setting and why the "Gaming Mode" and "Media Priority" buttons on many routers are not the same thing and can make matters worse.

Fix 3 (free): check the app's quality setting and your plan tier

Netflix lets you set data usage per profile; Auto "adjusts automatically to deliver the highest possible quality" and is what you want on home internet (Netflix). A profile set to Low to save mobile data will look soft on a 4K TV forever. Then confirm the plan tier. If you expect 4K and have Netflix Standard or Prime Video without Ultra, the fix is a subscription change or accepting 1080p, and no amount of network work will alter it.

Fix 4 (free): update, then restart in the right order

Netflix's standard sequence for a buffering TV is to turn off the TV, unplug the modem and router for 30 seconds, plug the modem back in and wait for its lights to settle, then the router, then the TV (Netflix). While you are there, update the TV's firmware and the streaming apps. Built-in TV apps lose codec and feature support as they age, which is one reason a five-year-old set plays worse each year on the same connection.

Fix 5 (one cable): wire the TV

If the phone-at-the-TV test showed a big gap and a cable can reach, run Ethernet from the router to the TV. One point of confusion is worth clearing up: most TVs have a 100-megabit Ethernet port, which looks slow next to Wi-Fi 6 and is more than six times what Netflix asks for 4K (Pocket-lint). The cable is not about speed. It is about zero packet loss and a buffer that never runs dry. If you stream high-bitrate files from a home media server, the 100-megabit port can become a limit; for Netflix, Hulu, and Prime Video, it never will.

Fix 6 (modest cost): a streaming stick or box instead of the built-in apps

If the phone played cleanly where the TV stuttered, the TV is the bottleneck. A current streaming device plugged into HDMI brings its own, usually better, Wi-Fi radio, a faster processor, current codec support, and apps that are maintained for years after the TV maker stops updating its own. This is also the fix for a TV whose built-in app will not reach 4K on a title you know is 4K. Choose a device that explicitly lists 4K and HDR support if that is what you want; check the service's own device list before buying. Our gear pages list options.

Fix 7 (modest cost): bring the network to the TV

If both bands were weak at the TV's location and no cable can reach, the answer is an access point or mesh node in or near the TV room, ideally wired back to the router. This is the only case where buying Wi-Fi hardware addresses buffering, and Step 2 is what tells you whether you are in it. A faster router in the same closet, broadcasting through the same walls, changes little.

The expensive options, honestly

A faster plan. Useful only if your Step 1 single-stream reading is genuinely below the requirements in the table, or if your household's concurrent streams exceed what you have, which at 50 megabits for three 4K streams is rare. If Step 3 showed an evening sag, a faster tier on the same congested node sags too; you are buying a higher ceiling in a room whose problem is the floor.

Switching to fiber. This one can help, for a specific reason. Fiber is not shared the way a cable node is, and in the FCC's data fiber and cable providers both show high peak-hour consistency while DSL lags, but fiber's advantage shows up in the metric that matters for streaming, consistency during the 7 to 11 p.m. window, not in the headline speed (FCC). If your evening Watch traces are the problem and fiber is available, it is a reasonable fix. If your problem is the thirty feet of air between router and TV, fiber to the house delivers the same thirty feet.

A gaming router. Streaming does not care about latency, so the one thing these routers market is the one thing you do not need. The features that help, SQM and a good radio, exist on ordinary routers. Save the money for Fix 7 if you need it.

A new TV. Justified only when Step 5 shows the chain is the limit: the set cannot decode a codec the service requires, lacks HDCP 2.2 on its HDMI inputs, or its apps are no longer updated. A streaming device solves the last of those on an otherwise good panel.

A VPN "for streaming." A VPN adds a hop and often lowers throughput, and it can route you to a server far from the service's nearest content cache. If you run one for privacy, exclude the TV or streaming device from it. If you are being sold one to "stop buffering," the pitch is wrong.

Quick reference

Sources

• Netflix, recommended internet speeds. help.netflix.com
• Netflix, how to get the best video quality. help.netflix.com
• Netflix, keeps buffering / freezes. help.netflix.com
• Netflix, loads slowly or keeps buffering. help.netflix.com
• Netflix, control how much data Netflix uses. help.netflix.com
• Netflix, supported browsers and system requirements. help.netflix.com
• Netflix, HDCP 2.2 requirement. help.netflix.com
• Hulu, internet speed recommendations. help.hulu.com
• Prime Video, system requirements for computers. primevideo.com
• Amazon, Prime Video Ultra and 4K. aboutamazon.com
• FCC, Measuring Fixed Broadband, Twelfth Report. fcc.gov
• FCC, Measuring Broadband America 2015. fcc.gov
• ThousandEyes, a very simple model for TCP throughput. thousandeyes.com
• Mux, adaptive bitrate streaming. mux.com
• Google Support, YouTube Stats for nerds. support.google.com
• How-To Geek, Netflix Test Patterns. howtogeek.com
• Pocket-lint, your TV's Ethernet port. pocket-lint.com

The guide above is enough to find and fix almost any buffering. These notes are for readers who want the mechanics behind the advice.

Advanced notes

• Why single-stream. A streaming client typically fetches 2 to 10 second chunks over a handful of HTTP connections, and its adaptive logic estimates bandwidth from how quickly those chunks arrive (Mux). A six-stream speed test masks per-connection ceilings imposed by loss and by Wi-Fi retransmission; the single-stream mode exposes them.
• Loss math. The Mathis bound, throughput at most (MSS / RTT) times (1 / square root of p), is why loss hurts far out of proportion to its percentage. With a 1,460-byte segment and a 20 ms round trip, 0.1 percent loss caps one connection near 18 Mbps, and 1 percent near 6; on longer paths the ceiling drops further (SLAC, ThousandEyes). Services increasingly use QUIC, which recovers differently, but Wi-Fi loss still stalls chunk delivery.
• Buffer-based adaptation. Modern players decide quality primarily from buffer occupancy rather than raw throughput estimates, dropping rungs preemptively as the buffer drains (Mux). That is why a soft picture precedes a stall, and why a stall means the shortfall was both deep and sustained.
• The HDCP step. 4K and HDR streams require HDCP 2.2 across every HDMI link, including through a receiver or soundbar; Netflix states this explicitly in its device requirements (Netflix). A single older device in the chain silently drops the whole chain to 1080p.
• What the Watch monitor cannot see. It measures from the laptop or phone running it, not from the TV. Pair it with Netflix's in-app Check your Network for a reading from the TV's own radio.
• Wired TVs and the 100-megabit port. Fast Ethernet on the TV is a ceiling, not a bottleneck, for compressed streaming; the win is loss-free delivery. Gigabit matters only for local high-bitrate playback (Pocket-lint).
• DRM is also a tracking surface. The Protected Playback card notes that a DRM request exposes a device signal to the service. That is the price of premium playback in a browser, and worth knowing on a privacy tool.

The full source list is at the end of the Simple version of this guide.