How to Save a Twitch VOD Without OBS (No Install, Browser Only)

Updated: 2026-07-06 · Written by the vodfetch founder

You do not need OBS, a desktop app, or any technical setup to save a Twitch VOD. This is the fastest, no-install way: paste the link into a free browser tool and download the past broadcast as an MP4 in seconds — no account, no configuration.

Do you actually need OBS to save a Twitch VOD?

No. OBS Studio is broadcasting software built to record live video from your own screen in real time — it's a great tool for streamers, but it's the wrong tool for saving a VOD that already exists on Twitch. You'd have to re-play the whole stream and re-record it live, which is slow, huge, and unnecessary.

A past broadcast is already sitting on Twitch's servers. To keep it, you just need to download it — and that takes a browser, not a install-and-configure production suite.

Why OBS is overkill for saving a VOD

Using OBS to "save" an existing VOD means opening the VOD, hitting record, and sitting through the entire playback in real time while OBS re-encodes it — a three-hour VOD takes three hours. It also uses your CPU/GPU the whole time and produces a fresh, often lower-quality re-encode rather than the original file.

There's no reason to do that. The VOD's actual video is available directly; a downloader fetches it in a fraction of the time, at source quality, with zero setup.

The no-install, browser-only way

A free tool like vodfetch runs entirely in your browser. You paste the VOD's link, it reads Twitch's public playback data, and it saves the video straight to your device as a standard MP4 — no download to install, no account to create, no settings to configure, and no watermark added.

It works the same on Windows, macOS, Linux, Android and iOS, because there's nothing platform-specific to install. If you can open a web page and paste a link, you can save the VOD. The full steps are below.

Keeping full quality (and the chat)

Because you're saving the original file rather than re-recording it, you keep the real quality — choose Source to get the full 1080p60 where the streamer broadcast it, instead of the re-encoded copy an OBS recording would give you.

You can also grab extras OBS wouldn't: trim to just the section you want before downloading, or export the VOD's chat replay as a timestamped text file. All without installing anything.

What about saving a live stream?

If the stream is happening right now and you want to capture it as it airs, that's the one case where recording (with OBS, or with a downloader's live-record mode) makes sense. But for a stream that has already ended and become a VOD, downloading is faster, lighter and higher quality than any recording approach — no OBS required.

Where OBS still wins: the cases a downloader cannot cover

There is one honest limit worth stating plainly. vodfetch talks to Twitch's public GraphQL endpoint with Twitch's own web Client-ID and no user token — there is no login step anywhere in the flow, so the tool sees exactly what a logged-out visitor sees. Ask it for a subscriber-only or private past broadcast and it stops at the token request with "VOD unavailable (deleted, private or sub-only)". A screen recorder capturing your own logged-in session is the only route to that content, and that is a genuine point in OBS's favour.

The second gap is content that never becomes a VOD at all. Twitch deletes past broadcasts after 7 days, 14 for Affiliates, and 60 for Partners (and for channels with Prime or Turbo), and plenty of channels leave archiving switched off entirely, so nothing is ever stored. Once that window closes the file is gone from Twitch's servers and no downloader retrieves it. If a stream matters to you and it is airing right now, capturing it live is the only guarantee; planning to download it later is not.

Third, quality. Some streams hand out anything above 720p60 only to an authenticated player token, whatever software is asking. When that applies the quality list you get is genuinely shorter: the dropdown is built from the renditions the master playlist actually returns, sorted source first and then by descending bitrate, and it cannot invent one Twitch did not serve. A recording made from your own logged-in player can capture the higher rendition; the cost is that it runs in real time and re-encodes as it goes.

Muted audio is not one of these cases. When Twitch flags a VOD section for copyrighted music, the muting is baked into the segments Twitch serves, so a download and an OBS re-recording of the same VOD are equally silent there. Only a capture made while the broadcast was still live, before the audio scan ran, has the original sound. If you are saving an existing VOD, those silent stretches are the source material, not a fault in the tool.

Long VODs in a browser: MP4 or TS, and what each costs in memory

The Format switch is the single most consequential setting on a multi-hour VOD. In MP4 mode every segment is pushed through the mux.js transmuxer and the converted output is held in memory until the last segment has been fetched; only then does the log read "Converting to MP4…", and only after that step finishes does anything get written out. Above an estimated 1.5 GB the tool asks for confirmation first and suggests Format → TS or a shorter trim. That is a prompt you can accept, not a hard cap — but on a six-hour source-quality broadcast, accepting it is how tabs run out of memory.

TS mode works the other way round: each batch of six segments is written out as soon as it arrives, so peak memory stays near the size of one batch rather than the whole file. That only holds if the browser can stream to disk, which is the next question. A live recording always takes the TS path, because the transmuxer only runs when the source is not live — which is why a live capture lands as .ts however the Format switch is set, or .aac if you picked the audio-only rendition.

Whether TS writes to disk or to RAM depends on the browser. The tool checks for window.showSaveFilePicker: where it exists you choose the destination up front and bytes stream into that file. Where it does not — Firefox, Safari, and mobile browsers generally — everything buffers in memory, and above an estimated 700 MB the tool warns and suggests Chrome or Edge, or trimming a section. On a phone that ceiling, not the tool, is the real limit on what you can save.

Two footnotes on those prompts. The size estimate is the rendition's advertised bandwidth divided by eight, multiplied by the selected duration, and it is only computed for a VOD whose master playlist reports BANDWIDTH; with no bitrate reported the estimate is zero and neither confirmation ever fires, whatever the finished file turns out to weigh. And a finished .ts is not a broken file. The tool says so directly with "Plays in VLC; for MP4 choose Format → MP4." VLC and mpv open it as-is, and ffmpeg rewraps it to MP4 by stream copy without re-encoding.

What replaces the OBS recording indicator

There is no recording window, no scene collection and no encoder settings — the progress card is the entire interface. Segments are fetched six at a time in parallel, each pulled with HTTP Range requests in 32 MB chunks through a media relay that exists purely to satisfy the browser's CORS rules. The two counters under the bar are the part worth watching: the left one reads segments done over total plus bytes transferred, the right one reads throughput and an ETA extrapolated from the average time per completed segment, so it is noise for the first few seconds and settles once a batch or two has landed.

On the MP4 path the bar climbs to 92% during the transfer, then jumps to 97% while the conversion runs. A stall at 97% on a long VOD is the transmuxer working through the file, not a hang, and it can take a while. On the TS path the bar tracks segments straight through to 100%, because there is no conversion step to wait on.

Each range request gets up to four attempts, with pauses of 300, 600 and 900 milliseconds between them, before the run gives up with "Segment failed". There is no resume: a failed download starts over from the first segment. The playback token the tool exchanges for the playlist is short-lived, so on a page that has been open for an hour the right recovery is to analyze the VOD again — that re-runs the token request and rebuilds the segment list — and then start the download from the freshly loaded page.

Filenames are built for you from the streamer, date, title and quality label joined with underscores, stripped of the characters Windows rejects and cut to 120 characters; type your own in the filename box to override it. After a job finishes, the last eight filenames are listed on the page from your browser's local storage. That list holds names and dates only — it is a record of what you saved, not a second copy of it.

If it fails, the message names the step that broke

Errors arrive as a single line in the log, and each one points at a specific stage. "Enter a Twitch URL", "Invalid URL" and "Unrecognized Twitch URL" all come from parsing, before any network request is made: the box takes twitch.tv/videos/… and clips.twitch.tv links, a bare numeric VOD id, a clip slug, or a plain channel name. Pasting a channel is not an error even when nobody is live — if the live lookup fails, the tool falls through to a browsable list of that channel's 24 most recent past broadcasts with a load-more button, so an offline channel hands you a VOD picker instead of a message.

"VOD unavailable (deleted, private or sub-only)" means Twitch returned no playback token for that id. Deletion, privacy and subscriber gating look identical from outside, so open the link in a logged-out private window to find out which one applies. "Usher 403 (sub-only/expired)" comes one step later, when the signed token is refused at the playlist server. That one is worth exactly one retry from a freshly analyzed page, because a token can expire while a tab sits open — but if a re-analyze produces it again, the VOD really is gated and no downloader gets past it.

"No qualities available" sits between those two: the token worked and the playlist server answered, but the master playlist listed no usable renditions. "Playlist HTTP <code>" comes later still, when the tool opens the variant playlist for the quality you picked, and "Segment failed" appears during the transfer itself. For all of these the fix is the same, and it is not a different tool: analyze again so the whole chain is rebuilt from a fresh token, then download on that page.

The MP4 converter has its own failure modes, and the most common one is silent. If the transmuxer script never loads — a script blocker, an extension or a corporate proxy is the usual cause — nothing is raised at all; the tool quietly falls back to TS, and the only symptom is that you asked for MP4 and got a .ts. "MP4 converter failed to start — choose Format → TS." means the script did load but the transmuxer would not initialise, and "MP4 conversion failed — choose Format → TS and retry." means it choked partway through the stream. All of them end the same way: the TS path needs no converter. (The related "MP4 converter unavailable" belongs to the GIF export, which builds an MP4 of the selection first.)

Two more are worth recognising. "No segments in range" means the trim window does not overlap the VOD, which in practice means a start time past the end of the broadcast — a mistyped hour is the usual cause. An end time longer than the VOD cannot trigger it, because the end is clamped to the real length. And if you dismiss the browser's save dialog with Escape, or decline one of the size prompts, the run stops with "Cancelled" before a single segment is fetched. That is your own cancellation rather than a failure, and pressing download again simply reopens the dialog.

The parts of the job OBS was never going to do

Trimming happens before the transfer, so a twenty-minute cut from a seven-hour VOD moves twenty minutes of data rather than the whole thing. The filter keeps every segment that overlaps your window, which means the cut expands outward to segment boundaries at both ends: the file begins at the start of the segment containing your start time and ends at the end of the segment containing your end time. The readout under the fields shows the range you asked for, not the expanded one, so the saved file can run a few seconds longer than the duration displayed.

Chat replay is a separate button and it exists only for VODs. It pages through Twitch's comment data a hundred messages at a time and writes a plain text file called <id>_chat.txt, one line per message in the form [timestamp] name: message. The timestamps are offsets into the broadcast — h:mm:ss once it passes an hour, mm:ss before that — so the file lines up with the video you just saved. No player, no JSON parsing, no post-processing.

If the streamer set chapter markers, a second button writes <id>_chapters.txt in the same bracketed format, one line per marker. That button only appears when the VOD actually has markers, so its absence answers the question for you. Searching the chat file for a phrase, or the chapter file for a game name, is usually a faster way to find the moment you came for than scrubbing a multi-hour timeline.

The page also reads its own URL. Adding ?url= (or ?u=) prefills the input, and ?go= or ?autostart= runs the analysis on load, so a bookmark can drop you on a filled-in, already-analyzed page. On a VOD, ?t=1h23m45s — the same parameter Twitch puts in a share link — opens the advanced panel, switches trimming on, and pre-sets a one-minute window starting at that timestamp. GIF export is the one extra that is not VOD-only: it is offered for any clip, and for a VOD only while trimming is on and the selection is about fifteen seconds or shorter.

How to download a Twitch video

1. 1

   Copy the Twitch VOD link

   Open the past broadcast on Twitch and copy the URL from the address bar (twitch.tv/videos/…). Do it before the VOD's retention window closes.

2. 2

   Open vodfetch in your browser

   Go to the free tool — there's nothing to install and no account to create. It works on any device with a browser.

3. 3

   Paste the link and analyze

   Paste the VOD URL into the box. It reads the video right in your browser via Twitch's public playback data.

4. 4

   Pick quality and download the MP4

   Choose Source for full 1080p60, optionally trim to just the part you want, and download. The VOD is now a permanent local file — no OBS, no re-encode.

Frequently asked questions

Ready to download? Use the free Twitch VOD Downloader.

← Back to the Twitch Downloader