Why Twitch buffers when your internet is fine

# The two comparisons that name the cause

Both comparisons are things you can do while the stream is still buffering, and neither changes any setting you would have to undo. Run them in this order.

1. Open a second channel, and pick a big one. A top-directory channel with thousands of viewers almost certainly has a full set of quality options and is being served from well-provisioned capacity. Watch it for three or four minutes in another tab. If it is smooth while the original channel stutters, that is the single most informative result you can get: the same machine, the same browser, the same connection and the same Twitch account just played video without a problem.
2. Take the player off Auto. Click the gear in the bottom-right of the player, open Quality, and choose a fixed rung below the top one - 720p is a good first pick. Auto is the player exercising its own judgement about what your connection can carry, and it re-makes that judgement continuously. Pinning the quality removes that variable entirely. If the buffering stops, the problem was the switching, not the connection.
3. Note what the quality menu contained. If the only entries were Source and Audio Only, that channel is publishing a single video quality and comparison two was never available to you. That is a finding, not a failure - see the fourth row of the table below.

# Why your speed test says the line is fine

The speed test is not lying and it is not broken. It is answering a question you did not mean to ask. It opens several connections at once to a server picked for proximity, pushes as hard as it can for roughly ten seconds, and reports the peak it managed. That number describes the best short burst your line can produce under ideal conditions.

Live video needs something close to the opposite. It needs a modest rate - a 1080p60 Twitch stream is a single-digit number of megabits - delivered without interruption for hours, from one specific source that the speed test never touched. Twitch describes those sources as Points of Presence: "a small-to-medium deployment of servers in a co-location facility, normally at a major internet exchange point."^[4] Your speed test server and the Twitch PoP serving your channel are different machines on different networks reached by different routes. A congested hop on the second route does not appear in the first measurement at all.

This is why the symptom is so often described as random. It is not random; it is intermittent, and intermittent is what a ten-second test is structurally unable to see. A line that delivers 300 Mbps on average while pausing for 400 milliseconds twice a minute will pass every speed test you run and stall every live stream you watch. Peak throughput and delivery steadiness are separate properties, and only one of them is on the test result.

# What to read in the player instead

The Twitch player keeps its own diagnostics, and they are more relevant than anything a general network tool will tell you because they describe the actual session that is failing. Open the gear in the player, go to Advanced, and switch Video Stats on. Our Twitch low latency guide walks through opening the same panel to read Latency To Broadcaster; here we are after different fields.

The distinction in the first two rows is the one that decides half of the fixes on the internet. A buffer that empties before each stall means the bytes are not arriving fast enough or steadily enough - a network story. A buffer that stays comfortably full while the picture still hitches means the bytes arrived and your computer could not turn them into frames in time - a decode story. They look identical on screen and have almost nothing in common as problems. Every generic fix list treats them as one thing.

# When it is the broadcaster, not you

This possibility is absent from essentially every page competing for this query, and the reason is structural rather than accidental: several of those pages exist to sell video repair utilities, driver updaters or connection-bonding subscriptions, and none of those products can be sold to someone whose answer is "nothing is wrong with your computer".

If the person broadcasting has an unstable upload, every viewer sees stalls at every quality simultaneously. Twitch delivers what it received; a gap in the incoming stream becomes a gap in the outgoing one. The HLS specification is explicit that malformed or over-long segments on the server side "can trigger playback stalls and other errors",^[3] which is the protocol-level description of what a struggling encoder produces.

• Read chat. The cheapest test there is. If several people are typing about lag or buffering in the same minute you are seeing it, the cause is upstream of all of you and no setting on your computer will change it.
• Check whether it survives a quality change. A broadcaster-side gap appears at every rung, because every rung is derived from the same incoming stream. A viewer-side problem usually improves at a lower rung.
• Check whether it survives a different channel in the same category. This separates one struggling broadcaster from a wider Twitch incident.
• If you are the broadcaster being asked about this, the diagnosis moves to the sending side entirely: broadcast health shows what Twitch actually received, and OBS disconnects covers the case where the stream is dropping outright rather than wobbling.

There is a fourth actor worth naming, because it produces a symptom that looks like a personal fault and is not one. Twitch's serving capacity is finite and regional. During a very large simultaneous event, a PoP can be under enough load that delivery to some viewers degrades while the same viewers' connections test perfectly. You will not get a notification about it. The tell is timing: buffering that begins and ends on a schedule matching a major broadcast, affects several channels at once, and disappears afterwards without you having changed anything.

# Fixes, in the order the triage points to

Apply the one your two comparisons pointed at. Applying all of them in sequence is how people end up with a working stream and no idea why, which is the same position they were in before, only with more changed settings to undo later.

1. Auto is switching too much - pin the quality. Gear, Quality, pick a fixed rung one or two below the top. This is the correct fix for a variance-limited line and it costs you some sharpness and nothing else. It is also the only fix on this page that is instant and fully reversible, which is why it goes first.
2. The buffer empties before each stall - work on steadiness, not speed. A cable instead of Wi-Fi is the single largest improvement available to most people, and the reason is variance rather than throughput: Wi-Fi shares airtime with neighbours, microwaves and every other device in the home, and that contention is exactly the property that live video cannot absorb. Upgrading to a faster plan, by contrast, changes the number that was already fine.
3. Skipped Frames climb while the buffer stays full - this is your machine. Here, and only here, the standard advice earns its place. Toggle hardware acceleration in your browser and test both states rather than assuming one is correct: on some machines the GPU decode path is the problem and on others it is the fix. Close other GPU-heavy applications. Our supported browsers page covers which builds Twitch actually targets.
4. Only one channel is affected and it has no quality menu. There is no fix on your side. Watch at a time when your path to Twitch is less congested, or accept that this particular broadcaster's Source bitrate is above what your connection reliably sustains. The mechanism, and what the broadcaster can do about it, is in why Twitch quality options go missing.
5. Everything buffers and the comparisons did not separate anything. Now test the route rather than the machine. A VPN is a diagnostic instrument here, not a fix: if a VPN makes Twitch smooth, the problem is a specific path between your provider and the Twitch PoP, which is information you can take to your provider. If it changes nothing, the path was never the issue and you have ruled out a whole category.

# Advice from the top results that does not apply

None of the following is invented; all of it appears repeatedly on pages currently ranking for this query. The problem is that each is offered unconditionally, to a reader whose cause has not been identified.

• Video repair software. Several of the highest-ranking results for this query are published by companies selling file-repair tools. A live stream is not a file on your disk. There is nothing for such a tool to repair, and the presence of this advice is a reliable signal that the page was written to rank rather than to help.
• Upgrade your internet plan. The premise of the query is that the plan is already fast. Paying for a higher peak does not change delivery steadiness, which is the property that was failing.
• Change your DNS. DNS resolves a hostname to an address once, at the start. It can plausibly affect how long a channel takes to begin playing. It cannot cause a stall forty minutes into a stream, because no lookup is happening then.
• Clear your cache and cookies. Harmless, occasionally fixes an unrelated player fault, and unrelated to a network delivery problem. Worth trying only after the triage has pointed at your own machine.
• Disable hardware acceleration. Genuinely useful in one of the four boxes - Skipped Frames climbing while Buffer Size holds - and irrelevant in the other three. Test both states rather than treating off as the correct answer.
• Install a browser extension to fix buffering. Extensions that claim to stop buffering generally work by pinning quality, which you can do yourself in the player's gear menu in two clicks with nothing installed and nothing granted access to your browsing.

# The bottom line

Buffering on a fast connection is not a malfunction that needs a list of remedies applied until one sticks. It is a question with four possible answers, and two comparisons costing under a minute eliminate three of them. Open a second large channel; move the quality off Auto. What happens next tells you whether you are looking at your machine, your route, the channel's quality ladder, or the person broadcasting.

The reason this matters more than the specific fix is that two of the four answers are not yours. A reader who never runs the comparisons will keep changing settings on a computer that was working correctly the whole time, which is the outcome most of the pages competing for this query quietly depend on. Knowing that a channel with a single variant stream gives your player nothing to switch down to^[2] is worth more than any amount of cache clearing, because it converts an infuriating mystery into a known limitation with a known workaround.

If you are on the other side of this - a broadcaster hearing about buffering from your own viewers - the diagnosis inverts, and the relevant questions are what Twitch actually received from you and whether your stream was given a quality ladder at all. Both are covered in the guides linked below.