Twitch Chat LogExport the full chat replay of any Twitch VOD as a timestamped text file.

Every line follows the same shape: an offset in square brackets, the chatter's display name, a colon and a space, then the message text. The clock is measured from the start of the VOD rather than the time of day, so [07:42] means seven minutes forty-two seconds into the broadcast. Minutes and seconds are always two digits; the hour appears only once the recording passes 1:00:00 and is not zero-padded, so a long stream produces lines like [3:07:42].

What the log deliberately does not carry is everything around the words. Only the display name and the message text are read, so there are no badges, no subscriber tiers, no name colours, no user IDs and no message IDs. Where Twitch no longer returns an account for a message, the name is written as a single question mark, so those lines still parse. Emotes survive as the text that was typed, because only each message fragment's text is kept: a Kappa in chat becomes the word Kappa in the file, and links stay as plain text. That is the trade that makes the file small, portable and searchable.

Because it is one message per line with a fixed left-hand field, ordinary text tools do the analysis. grep -n pulls every mention of a word together with its line number, and stripping the bracketed offset and the name field before piping through sort | uniq -c ranks the most active chatters of the broadcast. For a message count, use grep -c '' rather than wc -l: the file ends without a trailing newline, so wc -l reports one fewer than the log actually contains. If you import the file into a spreadsheet, split on the first '] ' and the first ': ' only — messages themselves contain colons.

Two things matter if you are keeping the log as a record rather than a curiosity. The file is named after the VOD's numeric ID, so the filename carries its own provenance: 2412345678_chat.txt belongs to that one past broadcast and nothing else. And the offsets line up with a full download of the same VOD, but not with a trimmed one. A trimmed download keeps whole segments, so it begins at the segment boundary at or just before your start point, and every timestamp in the log then runs ahead of the matching frame by roughly the amount you cut.

The export walks the chat replay in pages of 100 messages and stops when Twitch reports no further page, or after 3,000 pages — about 300,000 messages, which is far beyond what a single broadcast produces. Messages are written oldest first, in the order they are fetched.