How to Download Twitch VODs on Mac and Windows (Free, In Your Browser)

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

To download a Twitch VOD on Mac or Windows, open the Twitch Downloader web app in any desktop browser, paste the Twitch VOD, clip, or stream URL, choose your quality, and save the MP4 to your computer. It runs entirely in the browser, so there is nothing to install on either operating system.

Can you download Twitch VODs on both Mac and Windows?

Yes. The Twitch Downloader is a browser-based web app, so the exact same steps work on macOS and Windows with no software to install. If you can open a Twitch page, you can download from it.

It runs in any modern desktop browser, including Chrome, Edge, Firefox, and Safari. Because all the work happens inside your browser, you do not need a separate Twitch downloader PC program, a Mac app, or a command-line tool. Open the page, paste a link, and save the file.

The same approach works for VODs (past broadcasts), Clips, and live streams, so you can save Twitch content on your computer whether it is on-demand or currently airing.

How to download a Twitch VOD on Mac

On a Mac, copy the VOD URL from Twitch, open the Twitch Downloader web app in Safari, Chrome, Edge, or Firefox, and paste the link. Pick the resolution you want and start the download. The video saves as a standard MP4 that plays in QuickTime, the Photos app, or any player.

To download a Twitch VOD on Mac, you do not need to grant any special permissions or install an extension. The web app handles the whole process in the browser tab.

If you use Chrome or Edge on your Mac, you also get a streaming-to-disk advantage for very large VODs (see the section below).

How to download a Twitch video on Windows

The Windows steps are identical. Copy the Twitch link, open the Twitch Downloader web app, paste the URL, choose a quality, and click download. The MP4 lands in your Downloads folder unless you have set Windows to ask where to save each file.

To download a Twitch video on Windows, Chromium-based browsers like Chrome and Edge are the smoothest choice because they can write long broadcasts straight to disk instead of holding the whole file in memory.

Firefox works too and is a solid fallback if you prefer it as your default browser on Windows.

Where do downloaded Twitch files go on your computer?

By default, your browser sends the file to its standard download location: the Downloads folder on both Mac (under your user account) and Windows. You can find it instantly by opening the browser's download list, usually with Cmd+Shift+J on Mac or Ctrl+J on Windows.

If your browser is set to prompt for a save location, you will see a Save dialog and can choose any folder, an external drive, or a cloud-synced folder before the download starts.

Saved Twitch downloads are regular MP4 files, so you can move, rename, back up, or import them into a video editor like you would any other video.

Downloading large VODs and long live streams

Multi-hour Twitch broadcasts can be several gigabytes. In Chromium browsers (Chrome and Edge), the Twitch Downloader can stream very large VODs straight to disk as they download, which keeps memory use low and lets you grab full-length past broadcasts reliably.

For live streams, you can start saving the broadcast on your computer while it is still going. The web app captures the stream into an MP4 the same way it handles a finished VOD.

Tip: keep the browser tab open and your Mac or PC awake until the download finishes, since closing the tab cancels an in-progress save.

Is it OK to download Twitch VODs?

Download responsibly. Saving your own VODs, clips, and streams for backups, editing, or re-uploading is a common and reasonable use, and many people save other creators' content for personal, offline viewing.

Respect Twitch's Terms of Service and the original creator's rights. Get permission before redistributing, monetizing, or re-publishing someone else's content, and always credit the source where appropriate.

When in doubt, keep downloads for personal use only. The web app gives you the file; using it ethically is up to you.

What actually changes between Chrome, Edge, Safari and Firefox

The real difference on Mac and Windows is not the operating system, it is which browser you open, and it comes down to a single API: showSaveFilePicker, part of the File System Access API. Chrome and Edge expose it on both macOS and Windows. Safari and Firefox do not. When it is available, the app opens the system save dialog before the first byte is fetched and writes each segment straight into the file you chose. When it is not, every segment is held in memory and handed to the browser as one finished file at the end.

That has a consequence people find confusing on Chrome and Edge: your video will not appear in the browser's download list. Cmd+Shift+J or Ctrl+J will not show it, because the browser never performed a download; the page wrote the file itself into the folder you picked. Look there, not in Downloads. If you press Escape or Cancel at that save dialog the job ends with "Cancelled", and if the picker fails for any other reason the log prints "Could not stream to disk — buffering in memory" and quietly falls back to the memory route.

On Safari and Firefox, buffering means RAM, and the app warns you first. If a VOD's estimated size passes roughly 700 MB it asks you to confirm, stating that your browser will buffer it in memory and suggesting Chrome or Edge, or a trimmed section. That is a prompt, not a ceiling: accept it and the download proceeds. Chrome and Edge users never see this particular prompt because they stream to disk. Since Safari is the default on a Mac, this is the most common first surprise there.

Clips are the exception in every browser. A clip is fetched in one piece and handed to the browser as an ordinary download, so it does land in your Downloads folder and does show up in the download list, on Safari and Chrome alike. Neither the save dialog nor the memory warning applies to it. Everything above is specific to VODs and live recordings, which are assembled from hundreds of separate segments.

MP4, TS, and when the Format switch is ignored

The Format switch starts on MP4 and only ever applies to finished VODs. The condition in the code is useMux = (!isLive) && (curFmt === 'mp4') && !!window.muxjs, and each of its three terms is a case worth knowing. A live recording is always written as .ts, because the MP4 converter is never loaded for a live capture. A clip always saves as .mp4 through a separate code path that ignores the switch entirely. And the converter is a script fetched on demand, so if it fails to load you get .ts even with MP4 selected. Choosing an audio-only quality hides the switch altogether and produces .m4a, or .aac if the converter did not load. Nothing here ever produces an .mp3.

When a file ends in .ts or .aac the log adds "Plays in VLC; for MP4 choose Format → MP4." Take that literally: QuickTime Player on macOS and the stock Windows media player will not open an MPEG transport stream, while VLC opens it on either system. If you need MP4 afterwards, remux rather than re-encode: ffmpeg -i input.ts -c copy output.mp4 finishes in seconds and touches neither the video nor the audio. The command is identical on macOS and Windows apart from the paths.

MP4 conversion runs inside the tab and the converted output accumulates in memory until the conversion finishes, which is why streaming to disk does not rescue it even in Chrome. Above roughly 1.5 GB estimated, the app asks you to confirm and points you at TS or a trimmed section instead. For a long broadcast at source quality that estimate runs to many gigabytes and MP4 is a poor bet on either OS. If the converter breaks part-way you get "MP4 conversion failed — choose Format → TS and retry.", or "MP4 converter failed to start — choose Format → TS." if it never initialised.

Long broadcasts: a VOD download is all or nothing

Settle this before you start a multi-hour save: a VOD download cannot be paused or resumed, and it has no Stop button — Stop only appears while a live stream is being recorded. The file you chose in the save dialog is committed when the job closes it, and that happens only on completion. So if a segment fails part-way, or you close the tab, the file that was created sits at zero bytes and the work is gone; on Safari or Firefox, where it was buffering in memory, nothing is saved at all. The practical answer is trimming: take a six-hour broadcast in two or three passes, so each finished piece is safe on disk before the next one starts.

All of the work happens in that one tab, so the machine has to stay awake for it to keep making progress. On macOS, running caffeinate -i in Terminal for the duration prevents idle sleep, though closing the lid still sleeps the Mac unless an external display is attached. On Windows, raise or disable the sleep timer under Settings, System, Power. Note that the screen timeout and the sleep timer are separate settings: keeping the display on does not keep the machine awake.

Ordinary network noise is already absorbed. Each range request — 32 MB at a time through the media proxy — gets up to four attempts, with the pause between them growing from 300 ms to 1.2 seconds, before the job gives up with "Segment failed". Segments are fetched six at a time rather than one after another, so a single slow segment does not stall the queue. A live recording re-reads the playlist on the stream's own segment interval and only concludes "Stream ended or unreachable." after eight consecutive polls return nothing new, so a brief blip will not end a recording.

Live capture is the one job with a hard limit: after three hours it stops itself, logs that it did so, and tells you to start it again for another three hours. Plan for the seams — a seven-hour marathon is three files, not one, and how much you miss depends on how quickly you restart. Because live output is always TS, the parts join without re-encoding: ffmpeg -i "concat:part1.ts|part2.ts|part3.ts" -c copy full.mp4. Pressing Stop on a live recording is safe, unlike an interrupted VOD, because Stop closes the file properly and what you have already captured is kept.

What each error message actually means

"VOD unavailable (deleted, private or sub-only)" means Twitch refused to issue a playback token: the past broadcast has aged out (7 days by default, 14 for Affiliates, 60 for Partners (and for Prime or Turbo channels)), was deleted by the streamer, or is subscriber-only. There is no login step in this app and no user token, which is exactly why subscriber-only content cannot be fetched at all. "Usher 403 (sub-only/expired)" is the same wall one step further along, where the token was issued but the playlist request was refused.

"Enter a Twitch URL" means the box was empty. "Invalid URL" and "Unrecognized Twitch URL" both come from the parser, before anything touches the network; the second means the link parsed but carried no usable path. The input takes more than a full VOD link: a clips.twitch.tv slug, a twitch.tv/<channel>/clip/<slug> link, a bare numeric video ID with or without a leading v, or just a channel name all work. If you copied a link out of a chat client that appended tracking text, paste the plain twitch.tv address instead. "No qualities available" means the master playlist came back with nothing usable and is worth one retry, while "Playlist HTTP 403" or "GraphQL HTTP 500" point at the connection path rather than at the video itself.

One message you will effectively never see is "Channel offline or not found". Paste a channel name whose stream is not live and, instead of an error, the app falls back to browsing that channel: its 24 most recent past broadcasts with a load-more button, plus its top clips filtered by today, this week, this month or all time. Archives approaching Twitch's retention cut-off are badged with the days they have left, which is the quickest way to see what is about to disappear. Only a channel name that does not exist at all reports a failure.

"No segments in range" is a trimming problem, but not the obvious one: if the end time is at or before the start time the app silently resets the end to the full length rather than erroring, so the message really means the start time you typed is at or past the end of the VOD. Trimming also keeps whole segments, and the cut expands outward to the nearest segment boundary at both ends, so expect a second or two extra on each side; do the rough cut here to keep the file small and trim precisely in your editor afterwards. The page reads its own query string too: open it with ?url=<twitch link>&t=1h02m03s and the box is pre-filled with a 60-second trim window opening at that timestamp, and &go=1 starts the analysis without a click.

File names, size estimates, and the limits nothing works around

Leave the filename box empty and the name is built for you from the broadcaster, the date, the title and the quality label, joined with underscores; the generated name appears as placeholder text in the box, so you can read it before you start. Whatever ends up there, yours or the generated one, is sanitised the same way: backslash, forward slash, colon, asterisk, question mark, double quote, angle brackets and pipe all become underscores, runs of whitespace collapse to single spaces, and the name is cut to 120 characters before the extension is appended. That is precisely the Windows-reserved character set, so a file named on a Mac stays valid when it later lands on a Windows drive or a shared network folder.

The size shown beside a quality is an estimate, not a measurement: it is the bitrate the playlist advertises multiplied by the duration you have selected, so it moves as you change the trim range. Clips and live streams show no estimate at all. The quality list itself is sorted with source first, marked with a star, then by descending bitrate, which puts audio-only at the bottom, and an entry only carries a Mbit/s figure when the master playlist reports one.

Several limits belong to Twitch rather than to any downloader. Subscriber-only VODs need an account token and there is no sign-in here. Some streams gate quality above 720p60 behind an authenticated token, so the list can top out below what the Twitch player showed you, whatever tool you use. Sections muted for copyrighted music are muted in the stream Twitch actually serves, so every downloader gets the muted audio.

What a web page does give you on both systems: nothing is installed, so there is no Gatekeeper warning to click past on macOS, no SmartScreen prompt on Windows, and nothing to uninstall afterwards. Media is relayed through a stateless proxy purely to satisfy the browser's CORS rules; the file is assembled in your browser, not on a server. The only thing kept between visits is a list of the last eight file names in your browser's local storage — the names, never the files. The page carries standard, clearly marked ads, with no pop-ups and no fake download buttons.

How to download a Twitch video

1. 1

   Copy the Twitch link

   On Twitch, open the VOD, clip, or live stream you want and copy its URL from the address bar (or use the Share button to copy the link).

2. 2

   Open the Twitch Downloader web app

   In any desktop browser on your Mac or Windows PC (Chrome, Edge, Firefox, or Safari), go to the Twitch Downloader web app. Nothing to install.

3. 3

   Paste the URL

   Paste the copied Twitch link into the input field. The web app detects whether it is a VOD, clip, or live stream and loads the available options.

4. 4

   Choose your quality

   Select the resolution you want, such as 1080p, 720p, or source quality. Higher quality means a larger MP4 file.

5. 5

   Start the download

   Click download. The video is saved as an MP4. In Chrome or Edge, very large VODs stream straight to disk so long broadcasts download reliably.

6. 6

   Find your file

   Open your browser's downloads list (Cmd+Shift+J on Mac, Ctrl+J on Windows). The MP4 is in your Downloads folder, or wherever you chose to save it.

Frequently asked questions

Ready to download? Use the free Twitch Downloader for Mac.

← Back to the Twitch Downloader