The video plays fine. The chat column beside it stays empty, or spins forever, or shows nine messages and quits.
Chat replay breaks in several unrelated ways, and the fixes have nothing in common. Reloading fixes exactly one of them. Work through these in order, because the first check settles a large share of cases in about five seconds, and no amount of troubleshooting helps if that is the one you hit.
Check one: is the video a past broadcast, and is it still in its window
Chat replay is not stored separately from the video. It rides along with the past broadcast, and when Twitch deletes the broadcast on its retention timer, the chat goes at the same moment.
The timers are 7 days for a regular account, 14 for Affiliates, and 60 for Partners, Prime and Turbo. I wrote those up with the sources in how long Twitch keeps VODs, chat replay and clips.
So if you arrived from a link that is more than two weeks old, the likely answer is that there is nothing left to load. The player will often still render, because the URL resolves to a page, and the empty chat column looks identical to a bug. It is not a bug. The data is gone.
The tell: if the video itself also fails to load, the broadcast expired. If the video plays and only chat is empty, keep reading.
Highlights, uploads and clips are different objects from past broadcasts, and Twitch has never documented their chat replay behaviour in one place. If your link points at a highlight or a clip rather than a past broadcast, an empty chat column there tells you nothing about whether the original broadcast's chat existed. Find the original past broadcast and check that instead.
Check two: sub-only and deleted content
Two things get stripped from replay rather than failing to load.
- Messages removed by a moderator during the stream do not come back in replay. If the moment you are looking for was a pile-on that mods cleared, replay is the wrong tool.
- Sub-only VODs need an active subscription on the account you are logged into. Being logged in is not enough. Chat and video both gate together.
Check three: your extensions, which is the boring answer
BetterTTV, FrankerFaceZ and 7TV all rewrite the chat container. When Twitch changes its frontend, those extensions break against it, and the visible symptom is usually chat replay specifically, because replay uses a different render path from live chat.
Test it properly rather than guessing. Open the same VOD in a private window with extensions disabled. If chat appears there, an extension is your answer, and updating it or turning off its emote features one at a time will find which.
This is worth doing early because it costs thirty seconds and it accounts for a lot of reports that get blamed on Twitch.
Check four: blockers and cookie settings
Chat replay loads over a separate request from the video. Strict tracking protection, aggressive ad blockers and third-party cookie blocking can kill that request while leaving playback intact, which produces exactly the video-works-chat-does-not symptom.
Firefox strict mode and Safari's default settings are the common culprits. Allow
twitch.tv in the blocker, or test in a browser you have not hardened, before concluding
anything else.
Check five: seeking, and the thirty second problem
If you jump around the timeline, replay sometimes never catches up, and sometimes lands out of sync with the video. Sync drift between a clip and its rendered chat is a known and long-running complaint, discussed at length in TwitchDownloader issue 1285.
Reload the page at the timestamp you want rather than seeking to it. That is the one case where reloading genuinely is the fix.
Check six: it is Twitch
Sometimes replay is simply down. Before spending an hour on your own setup, open a popular channel's most recent VOD in a private window. If chat replay is empty there too, the problem is not yours, and there is nothing to do but wait.
What none of this fixes
Every check above assumes the chat still exists somewhere. If the broadcast aged out, it does not. Twitch holds chat messages internally for its own moderation purposes, but the only public surface for reading them was the replay attached to a broadcast that no longer exists.
That is the part I find genuinely annoying about this problem. The messages were delivered to thousands of people in real time. They were public when they were sent. They stop being readable on a timer that has nothing to do with whether anyone still wants them.
Reading chat after the replay is gone
We record chat as it happens and keep it after Twitch drops the VOD. If the stream was on a channel we already cover, the chat you are trying to replay is likely sitting in the archive.
Search the archive for a phrase you remember, or browse the channels we record and open the broadcast.
If the channel is not on that list, recording it takes one click and starts within a few minutes. Add a channel. It only helps from that point forward, which is exactly why it is worth doing before the next stream rather than after.