Twitch Download 2026: Any VOD in 12 Steps, 20 Min

Type "twitch download" into a search box and you get three different tasks wearing the same two words. Some people want the app that plays the streams. Some people want the file underneath a stream — the VOD, the clip, the thing that quietly expires in seven days. A smaller and more determined group wants to record a broadcast live, before Twitch's copyright robots reach into the recording and tear the audio out. All three get filed under "downloading Twitch." None of them are the same job, and the tooling barely overlaps.

So we will do all three, in the order a working adult actually needs them: install the client, survive the mirror ecosystem that has metastasized around it, and then — the part you came for — pull the actual media off Twitch's edge servers with tools that respect your disk and your time. The Machine will also tell you where the law sits at each step, because "I didn't know" has never once worked as a defense and it is not going to start working with you.

What "Twitch Download" Actually Means

Before you install anything, disambiguate. The word "download" is doing an enormous amount of unpaid labor in this search term, and the wrong interpretation sends you to the wrong tool, the wrong file format, and occasionally the wrong side of a copyright notice.

Five tasks hiding behind one query

There are, in practice, five distinct things people mean:

• Install the client. Get the Twitch app on Android, iOS, Windows, or macOS so you can watch and chat. This is a straightforward app-store transaction that only gets interesting when you go off-store.
• Save a past broadcast (VOD). Pull down the recorded stream — twitch.tv/videos/<id> — as an MP4 you keep. This is the load-bearing use case and the one Twitch is least enthusiastic about.
• Save a clip or highlight. Grab a short curated segment. Different URL shape, different retention rules, mostly easier than a full VOD.
• Record a live stream. Capture the broadcast as it airs, in real time, because you do not trust it to survive as a VOD — or because the channel disables VODs entirely.
• Export chat. Download the chat log as structured JSON, optionally rendered back into a video overlay. Streamers and archivists want this more than anyone admits.

Each of those needs a different answer, and this guide gives all five. If you only remember one distinction, make it VOD versus clip versus live: the URL you paste decides which extractor path fires and which tool is even capable of the job.

Why Twitch makes the file hard to reach

Twitch does not want you to have the file, and this is not paranoia — it is the business model. A stream is delivered as HLS: an .m3u8 playlist pointing at a few hundred short .ts fragments on a CDN. There is no single "download" button because there is no single file; the "video" is a manifest and a pile of two-to-ten-second chunks that a player stitches on the fly. On top of that, Twitch runs server-side ad insertion (SSAI), which splices advertising segments directly into the same manifest, so a naive downloader can end up with ad breaks welded into the middle of your capture. This architecture is a cousin of every other adaptive-streaming service, and if you have ever wrestled a stream off a remote-play session you already know the shape of the problem — see our Chiaki-ng remote-play walkthrough for the same HLS-and-latency headaches in a different jacket.

The one distinction that keeps you out of trouble

Here is the law, compressed. Downloading your own broadcasts for archival is fine and Twitch even provides an official button for it. Downloading someone else's VOD for personal, offline, private viewing sits in a grey zone that Twitch's Terms of Service technically disallows (accessing content "through any means other than the interfaces Twitch provides") but that nobody has ever been sued over. Downloading someone else's content and re-uploading, monetizing, or redistributing it is straightforward copyright infringement, and that is the line that generates lawyers. The tools in this article do not care which of those you are doing. You should. Archiving is not the crime; rehosting is.

Prerequisites: Versions and Hardware

You do not need a workstation to download a Twitch VOD. You need enough disk, a current toolchain, and the discipline to update the toolchain more often than feels reasonable. Twitch changes its private GraphQL API on no announced schedule, and when it does, every downloader breaks at once until maintainers ship a patch. Old binaries are the single most common reason a download fails in 2026.

Software you must have

• yt-dlp — the actively maintained fork of youtube-dl and the default answer for VODs and clips. It ships date-stamped releases (the 2025/2026 line) and a nightly channel; you want whichever is newer when the extractor breaks. Repo: github.com/yt-dlp/yt-dlp.
• FFmpeg — non-negotiable. yt-dlp downloads HLS fragments and hands them to FFmpeg for muxing; without it you get a pile of chunks and no MP4. Get a recent build from ffmpeg.org (any 6.x or 7.x release is fine).
• TwitchDownloader — the specialist. lay295's tool is the best option for chat logs, chat rendering, and sub-only VODs, and it has a Windows GUI and a cross-platform CLI. Repo: github.com/lay295/TwitchDownloader.
• Streamlink — for live capture. It pipes a live channel to a player or a file. Repo: github.com/streamlink/streamlink.
• Python 3.9+ if you install yt-dlp via pip rather than the standalone binary. The standalone binary bundles its own interpreter and is the lower-maintenance choice.

Hardware and disk reality

The bottleneck is storage and network, not CPU. A source-quality ("chunked") 1080p60 VOD runs roughly 6,000 kbps, which is about 2.6 GB per hour. An eight-hour marathon broadcast is therefore a 20 GB file before you have rendered any chat. Muxing is a stream copy, not a re-encode, so even a low-power ARM box handles it; the work is I/O. Budget accordingly, keep an SSD as the scratch target so fragment reassembly does not thrash a spinning disk, and expect a full download to be network-bound at whatever your line sustains. If you archive at scale, the discipline is identical to hoarding ROM sets — checksums, sidecar metadata, and a folder convention you will not hate in two years, the same regime we push in the Miyoo Mini Plus archival piece.

Installing the toolchain

Pick your platform and run one of these. The pip route gets you the fastest updates; the package-manager route gets you FFmpeg alongside it.

# macOS (Homebrew) — gets yt-dlp, ffmpeg, streamlink in one shot
brew install yt-dlp ffmpeg streamlink

# Debian / Ubuntu — apt ffmpeg, pip for the fast-moving parts
sudo apt update && sudo apt install -y ffmpeg python3-pip
python3 -m pip install --upgrade yt-dlp streamlink

# Windows (winget)
winget install yt-dlp.yt-dlp
winget install Gyan.FFmpeg
winget install Streamlink.Streamlink

# Verify everything answers
yt-dlp --version
ffmpeg -version | head -n1
streamlink --version

Expected output confirms all three are live and current:

$ yt-dlp --version
2026.08.10
$ ffmpeg -version | head -n1
ffmpeg version 7.1 Copyright (c) 2000-2026 the FFmpeg developers
$ streamlink --version
streamlink 7.x

If yt-dlp --version reports something months old, stop and update before you do anything else. Ninety percent of "the download won't start" reports are a stale binary hitting a changed API.

The Official App, Every Platform

Watching, not saving, is what the official app is for. It is also the only distribution channel Twitch actually controls, so it is the baseline against which every sketchy mirror should be measured. The company behind the listings is Twitch Interactive, Inc., and if you ever need to document a distribution change for a story or a support ticket, the named support contact on the Android listing is android@twitch.tv, with a corporate address of 350 Bush St Fl 2, San Francisco, CA 94104.

Android via Google Play

The canonical Android source is the Google Play listing for package tv.twitch.android.app, which was last refreshed on 2026-08-15. Note what Play does not prominently show you: a version number. Google deliberately buried the version string years ago, which is exactly why the third-party mirror ecosystem exists and why those mirrors disagree with each other (more on that below). Install from Play, let it auto-update, and you never have to think about version numbers at all. That is the entire pitch, and for 95% of users it is the correct one.

iOS via the App Store

On Apple's side the app is listed as "Twitch: Live Streaming", marked Free with In-App Purchases — the IAP being Bits and gift subscriptions, not a paywall on the app itself. Apple's listing carries an original date of 2024-05-14 and a most-recent update of 2026-08-14. iOS gives you no sideloading escape hatch worth the trouble, so the App Store is the whole story here. There is no legitimate "download the IPA" path for a normal user, and anyone selling you one is selling you a problem.

Windows and macOS desktop

The desktop "Twitch App" is a separate animal from the website and is aimed at streamers as much as viewers. Software directories such as TechSpot's Twitch download page mirror it — their listing tagged it "Twitch App Download Free - 27.1.0" for Windows, macOS, and Android at 134 MB, dated 2026-04-03, with a download counter reading 110,270. Treat those third-party numbers as directional, not gospel; the authoritative desktop installer is the one linked from Twitch's own site. For pure viewing on a desktop, the browser is better than the app anyway, because the browser is where every VOD-downloading extension and userscript actually runs.

Third-Party APK Mirrors: A Version-Number Circus

The moment you leave Google Play, you enter a world where nobody agrees what version Twitch even is, and where a plausible-looking APK can be anything. This section is a warning wrapped in a how-to, because sometimes you genuinely need a sideloaded build — an older release, a device without Play Services, a region lockout — and if you are going to do it, do it with the verification steps, not on vibes.

The mirrors do not agree, and that is the lesson

Look at what the trackers reported across 2025 and 2026 and the incoherence is immediate. One Android mirror listed Twitch 27.9.1 on 2026-01-27 at 103.37 MB, with older builds 27.8.2 (2026-01-21) and 27.7.1 (2026-01-12) — a genuinely rapid cadence. A different mirror had Twitch at 30.7.2 on 2026-08-13 at 87.93 MB, claiming parity with the published Play version, plus 30.7.0 and 30.6.0 both on 2026-08-11, 30.5.0 on 2026-07-28, and 30.3.0 on 2026-07-15. APKPure listed 29.2.2 on 2026-04-27 at 93.4 MB. And a separate archive tracked a "18.x" lineage as though it were current — 18.3.5 in September 2025, 18.4 through 18.4.5 monthly into March 2026, and 18.5.0 billed as "latest" in April 2026 — while other mirrors were showing 29.x the same month. Three different "latest" version numbers for the same app in the same quarter. The file size wanders too: 87.93 MB, 93.4 MB, 103.37 MB, 134 MB. The takeaway is not "which mirror is right." It is that the version number on a mirror is not authoritative, and you must verify the binary yourself rather than trust the label.

Verify before you install — package name and signature

Two checks separate a real Twitch APK from a repackaged impostor. First, the package name must be exactly tv.twitch.android.app. Second, and more important, the signing certificate must match the one Twitch actually uses. A malware author can spoof the package name trivially; they cannot forge Twitch's private signing key. Use the Android SDK's aapt and apksigner:

# 1) Confirm the package identity and claimed version
$ aapt dump badging twitch-30.7.2.apk | grep -E "package|versionName"
package: name='tv.twitch.android.app' versionCode='30702' versionName='30.7.2'

# 2) Print the signer certificate — this is the real check
$ apksigner verify --print-certs twitch-30.7.2.apk
Signer #1 certificate DN: CN=Twitch Interactive Inc
Signer #1 certificate SHA-256 digest: <64-hex-string>
Signer #1 certificate SHA-1 digest:   <40-hex-string>
Verified using v2 scheme (APK Signature Scheme v2): true

The SHA-256 digest is the fingerprint that matters. Record it from a copy you know is clean — one installed from Google Play, extracted with adb — and compare every sideloaded APK against it. If the digest differs by a single character, the APK was re-signed by someone who is not Twitch, and it goes in the bin. "Verified: true" alone is not enough; a self-signed malware APK also verifies against its own key. You are checking whose key.

When sideloading is actually justified

Reach for a mirror like Uptodown or APKMirror only for specific, defensible reasons: pinning an older build because a new one broke a feature you rely on, installing on a de-Googled device without Play Services, or grabbing an APK for an emulator. For everyday updates, the Play Store's auto-update is safer and less work than any mirror will ever be. Sideloading is a tool for edge cases, not a lifestyle.

Exporting Your Own VODs — The Official Path

Before you touch a single third-party downloader, know that if the content is yours, Twitch hands you the file directly. This is the cleanest, most legitimate download path in the entire ecosystem, and an astonishing number of streamers do not know it exists.

Where the download button lives

Open the Creator Dashboard, go to Content → Video Producer, find the past broadcast or upload you want, open the ... (more) menu on that row, and choose Download. Twitch prepares an MP4 and streams it to your browser. Large VODs take a while to package on their end, and the download itself is a plain HTTP transfer with no HLS gymnastics — you get one clean file, source quality, no fragment stitching, no ad segments. This works for Past Broadcasts and Uploads. It does not work for Highlights or Clips, which are derived objects; to archive those as their creator you download the underlying source instead.

The seven-day clock you are racing

This is the part that costs people their footage. Twitch retains past broadcasts for a limited window and then deletes them automatically: roughly 7 days for standard accounts, and about 14 days for Partners, Affiliates, and users with Prime or Turbo. Highlights and uploads persist until you delete them, but the raw past broadcast is on a timer from the second you stop streaming. If you intend to archive your own content, either turn on the setting that auto-publishes broadcasts as VODs and download them promptly, or accept that a broadcast you did not save within two weeks is simply gone. The official export button is worthless if the VOD has already expired.

Why bother with third-party tools at all, then?

Because the official button only exports your content, and because it does not give you chat, rendered chat overlays, or the ability to grab a specific timestamp range without downloading the whole eight-hour file. The moment your needs go past "save my own full VOD," you are back to the command line — which is the next section, and the reason you are here.

Downloading a VOD in 12 Steps

This is the core walkthrough: pulling any accessible VOD to a clean, verified MP4 with yt-dlp as the primary tool and FFmpeg doing the muxing. Each step has a reason, because a step without a reason is a superstition. Budget about 20 minutes the first time — most of it is one-time setup — and a few minutes per VOD after that, plus however long the transfer itself takes.

1. Confirm you have the right to the file. Is it your VOD, a personal-archive copy, or something you intend to redistribute? The first two are defensible; the third is a copyright problem no tool will absolve. Decide this before you spend disk on it. Rationale: the legal posture is the one part of this that a patch cannot fix later.
2. Install and confirm the toolchain. yt-dlp plus FFmpeg, verified with --version as in the prerequisites. Rationale: yt-dlp without FFmpeg downloads fragments it cannot mux, and you end up with nothing playable.
3. Update yt-dlp to the current release. Run yt-dlp -U (standalone) or pip install -U yt-dlp. Rationale: Twitch rotates its private GraphQL surface without notice; a binary that worked last month may 403 today, and the fix is almost always "update."
4. Grab the correct URL. A full VOD is twitch.tv/videos/<id>. A clip is clips.twitch.tv/<slug> or twitch.tv/<channel>/clip/<slug>. Rationale: the URL shape selects the extractor path; paste a clip URL expecting a VOD and you get the wrong object.
5. List the available formats first. Run yt-dlp -F <url> and read the table. Rationale: you want to choose quality deliberately, and "chunked" is Twitch's source rendition — the one you want for archival.
6. Do a metadata dry run. Add --skip-download --write-info-json to confirm access and capture title, uploader, and duration before committing gigabytes. Rationale: a failed auth or a deleted VOD surfaces here in one second instead of after a partial 3 GB transfer.
7. Authenticate if the VOD is gated. For sub-only VODs you have legitimate access to, pass your browser session with --cookies-from-browser firefox (or chrome). Rationale: sub-only content is invisible to an anonymous request; your cookie is what proves you are allowed in.
8. Download with a sane output template and parallel fragments. Use -o for naming and --concurrent-fragments 8 for speed. Rationale: Twitch VODs are hundreds of small fragments; downloading them serially wastes your bandwidth, and a good filename template saves you a rename later.
9. Watch for ad and discontinuity warnings. If yt-dlp logs discontinuities, SSAI ad segments may have been interleaved. Rationale: ad splicing is the classic cause of a VOD that plays fine for ten minutes then desyncs or jumps.
10. Verify the muxed file with ffprobe. Confirm there is exactly one video and one audio stream, at the resolution and codec you expected. Rationale: this catches the two silent failure modes — missing audio and A/V desync — before you delete the source.
11. Remux or repair if needed. If timestamps are broken, run it back through FFmpeg with -c copy -fflags +genpts. Rationale: a stream copy fixes container-level damage without a lossy re-encode.
12. Archive with a checksum and metadata sidecar. Keep the .info.json and a .sha256 next to the MP4. Rationale: in two years you will not remember where a file came from; the sidecar is its provenance, and the checksum proves it did not rot on disk.

Reading the format table (Step 5)

Running yt-dlp -F on a VOD looks like this. The row you almost always want is chunked — the source rendition Twitch keeps at full quality:

$ yt-dlp -F https://www.twitch.tv/videos/2100000000
[twitch:vod] Extracting URL: https://www.twitch.tv/videos/2100000000
[twitch:vod] 2100000000: Downloading stream metadata GraphQL
[twitch:vod] 2100000000: Downloading VOD access token
[twitch:vod] 2100000000: Downloading m3u8 information
[info] Available formats for 2100000000:
ID          EXT RESOLUTION  FPS | TBR    PROTO | VCODEC ACODEC
audio_only  mp4 audio only      |        hls   |        mp4a
160p        mp4 284x160     30  |  230k  hls   | avc1   mp4a
360p        mp4 640x360     30  |  700k  hls   | avc1   mp4a
480p        mp4 852x480     30  | 1500k  hls   | avc1   mp4a
720p60      mp4 1280x720    60  | 3400k  hls   | avc1   mp4a
1080p60     mp4 1920x1080   60  | 6000k  hls   | avc1   mp4a
chunked     mp4 1920x1080   60  | 6000k  hls   | avc1   mp4a  (source)

The actual download command (Step 8)

Here is the invocation and roughly what a healthy run prints. Note the output template, the concurrent fragments, and the retry counts that keep a flaky CDN segment from killing the whole job:

$ yt-dlp -f chunked \
    --concurrent-fragments 8 \
    --retries 20 --fragment-retries 40 \
    -o "%(uploader)s - %(title)s [%(id)s].%(ext)s" \
    https://www.twitch.tv/videos/2100000000

[twitch:vod] 2100000000: Downloading m3u8 information
[hlsnative] Total fragments: 431
[download] Destination: SomeStreamer - Ranked grind to Masters .mp4
[download] 100% of 3.42GiB in 04:11 at 13.9MiB/s
[FixupM3u8] Fixing MPEG-TS in MP4 container of "SomeStreamer - Ranked grind to Masters .mp4"

Confirming the file is real (Steps 10-11)

Never trust a download you have not probed. FFprobe tells you in one line whether the audio actually survived — critical, because DMCA muting and SSAI both express themselves as missing or broken audio:

$ ffprobe -v error -show_entries stream=index,codec_type,codec_name,width,height \
    -of default=noprint_wrappers=1 "SomeStreamer - Ranked grind to Masters .mp4"
index=0
codec_type=video
codec_name=h264
width=1920
height=1080
index=1
codec_type=audio
codec_name=aac

# If timestamps are broken (playback jumps/desyncs), remux without re-encoding:
$ ffmpeg -fflags +genpts -i broken.mp4 -c copy -movflags +faststart fixed.mp4

Two streams, one video and one audio, at the resolution you chose: that is a good file. One stream, or a zero-byte audio track, means you have a muted or ad-corrupted VOD, and no amount of re-downloading fixes what Twitch already stripped at the source.

The Browser-Extension Route

Not everyone wants a terminal, and for the everyday "save this clip" case a browser extension is a defensible, low-friction choice. It also matters for the wider picture: extensions target browser-side access to Twitch content rather than the official app-download path, which is a distinct branch of the whole "download" ecosystem and worth understanding even if the CLI is your daily driver.

Twitch VOD Downloader on the Chrome Web Store

The most visible option is the Twitch VOD Downloader extension, which shipped a Version 3.26 update on 2026-02-21. Its own listing says it can download sections of Twitch VODs — a genuinely useful feature the CLI makes you compute manually — as well as stories, highlights, and clips. For "I need minutes 42 through 55 of a three-hour VOD," an extension that lets you drag a range is faster than working out fragment offsets by hand.

What an extension can and cannot do

An extension runs inside the page, with your session, which is both its strength and its ceiling. Strength: it inherits your login, so your own sub-only content is visible without exporting cookies. Ceiling: it is at the mercy of Twitch's front-end, which changes constantly, so extensions break more often and more quietly than a well-maintained CLI, and a dead extension gives worse error messages than yt-dlp's verbose logging. Extensions also cannot do server-side-grade repair — no ffprobe pass, no remux, no checksum. They fetch; they do not curate.

The permission tax you are paying

The Machine's standing advice on any Twitch-adjacent extension: read the permissions. A downloader legitimately needs to read the current tab and talk to Twitch's video hosts. It does not need to "read and change all your data on all websites," and if it asks for that, assume the download feature is the bait and your browsing history is the product. Prefer extensions that are narrowly scoped and recently updated — the 2026-02-21 timestamp on the listing above is the kind of signal you want, because an abandoned extension is a liability whether it still downloads or not.

Clips, Highlights, and Chat

VODs are the hard case; clips and chat are where the specialist tools earn their place. This is also where TwitchDownloader outclasses yt-dlp, particularly for chat, which yt-dlp does not handle at all.

Clips and highlights

Clips are short, they do not expire the way past broadcasts do, and they are the easiest thing on Twitch to save. yt-dlp handles them with the same command shape as a VOD — just paste the clip URL:

# Clip via yt-dlp — either URL form works
yt-dlp -o "%(uploader)s - %(title)s [%(id)s].%(ext)s" \
    "https://clips.twitch.tv/SomeFunnyClipSlugHere"

# Or with TwitchDownloader's CLI, which takes the slug directly
TwitchDownloaderCLI clipdownload --id SomeFunnyClipSlugHere -o clip.mp4 --quality 1080p60

Highlights behave like short VODs and download the same way. The one wrinkle is that a highlight is a curated slice of a past broadcast, so its retention outlives the raw broadcast — grabbing a highlight is often the only way to save a moment from a stream whose seven-day VOD window has already closed.

Chat, as JSON and as video

Chat is the archival material nobody thinks about until it is gone. TwitchDownloader downloads it as structured JSON and can render that JSON back into a video overlay — the scrolling chat you see in edited VOD reuploads. This is a two-step pipeline:

# 1) Download the chat log for a VOD as JSON (includes badges, emotes, timestamps)
TwitchDownloaderCLI chatdownload --id 2100000000 -o chat.json --embed-images

# 2) Render that JSON into a 1080p60 overlay video
TwitchDownloaderCLI chatrender -i chat.json -o chat.mp4 \
    --framerate 60 --output-width 340 --output-height 1080

The JSON alone is the valuable artifact — it is searchable, portable, and future-proof in a way a burned-in overlay is not. Render to video only when you specifically need the visual for an edit.

Sub-only VODs and the OAuth token

For subscriber-only VODs you legitimately have access to, TwitchDownloader accepts an OAuth token so it can authenticate as you. You extract the auth-token cookie from your logged-in browser session and pass it with --oauth. Understand exactly what that string is: it is your live session credential, functionally a password. Do not paste it into a pastebin, do not commit it to a repo, and rotate it (log out) when you are done. Treat a leaked auth-token the way you would treat a leaked password, because it is one.

Common Pitfalls and Fixes

Six ways this goes wrong, and the specific fix for each. Five of the six are avoidable entirely if you read this section before you start rather than after.

Trust and content pitfalls

• Installing an APK from an unverified mirror. The mirrors disagree on version and size for a reason — some of them are repackaged. Fix: run the apksigner --print-certs check from the mirrors section and compare the SHA-256 against a Play-installed copy. Whose key signed it is the only question that matters.
• Downloading sub-only or gated content you do not have access to. An anonymous request simply cannot see it, and no flag changes that. Fix: authenticate with your own logged-in session via --cookies-from-browser (yt-dlp) or --oauth (TwitchDownloader). If you are not entitled to the content, you are not entitled to the download.
• Assuming VODs live forever. Standard past broadcasts vanish in about 7 days, 14 for Partner/Affiliate/Prime/Turbo. Fix: download promptly, or save the Highlight, which outlives the raw broadcast. A VOD you meant to grab "next week" is frequently already deleted.

Technical pitfalls

• DMCA-muted audio. Twitch's Audible Magic scan mutes segments where it detects copyrighted music, and the mute is baked into the stored VOD. Fix: there isn't one on the download side — a muted VOD downloads muted. Your only recourse is a live capture made before the mute, which is why archivists record live.
• SSAI ad segments corrupting the file. Server-side ad insertion can splice ad fragments into the manifest, producing discontinuities, desync, or ads welded into your capture. Fix: keep yt-dlp current (its Twitch extractor handles most ad-stitching), and if a file desyncs, remux with -fflags +genpts.
• Stale tooling. The single most common failure. A binary from three months ago hits a changed API and 403s. Fix: yt-dlp -U before every session that matters. If it still fails after updating, check the project's issue tracker — a broken extractor is usually a known issue with a nightly fix already merged.

Troubleshooting Table

Ten failure modes, their real causes, and the fix. If your symptom is not here, the first move is always the same: update yt-dlp and try again before you debug anything else.

Symptom	Likely Cause	Fix
HTTP Error 403: Forbidden on a VOD	Stale extractor or rotated access token	Run yt-dlp -U; retry. Twitch changed its API and your binary is behind.
"This video is unavailable"	VOD expired (7/14-day retention) or was deleted	Nothing to recover. Check for a surviving Highlight of the same moment.
Subscriber-only VOD returns nothing	Anonymous request cannot see gated content	Add --cookies-from-browser firefox (yt-dlp) or --oauth (TwitchDownloader) with your own logged-in session.
Audio missing on part of the file	DMCA/Audible Magic muted those segments at source	Unfixable on download. Only a pre-mute live capture has the audio.
Ads spliced into the middle; playback desyncs	Server-side ad insertion (SSAI) discontinuities	Update yt-dlp; remux with ffmpeg -fflags +genpts -c copy.
Download crawls or stalls repeatedly	Serial fragments or CDN rate-limiting	Add --concurrent-fragments 8 and --fragment-retries 40; consider an external downloader (aria2c).
APK will not install (signature mismatch)	Existing app signed with a different key	Uninstall the current copy first, or verify the APK's signer — a mismatch can mean a repackaged file.
Chat download returns partial or empty log	Rate-limiting or a very long VOD	Retry; TwitchDownloader resumes. For huge VODs, download chat in timestamp ranges with --beginning/--ending.
A/V out of sync after muxing	Broken presentation timestamps in the TS source	Remux with ffmpeg -fflags +genpts -i in.mp4 -c copy out.mp4.
Clip URL downloads the whole channel page	Wrong URL shape passed to the extractor	Use the exact clip form: clips.twitch.tv/<slug> or twitch.tv/<channel>/clip/<slug>.

Advanced Tips

Once the basics are muscle memory, these turn a manual chore into a pipeline. None of it is exotic; all of it saves time at volume.

A persistent yt-dlp config

Stop retyping flags. yt-dlp reads a config file automatically, so your defaults — source quality, parallel fragments, output template, cookie source — apply to every invocation. Drop this at ~/.config/yt-dlp/config (Linux/macOS) or %APPDATA%\yt-dlp\config (Windows):

# ~/.config/yt-dlp/config
-f chunked
--concurrent-fragments 8
--retries 20
--fragment-retries 40
--output ~/Twitch/%(uploader)s - %(title)s [%(id)s].%(ext)s
--write-info-json
--embed-metadata
--no-part
# Pull auth from your logged-in browser so sub-only VODs "just work"
--cookies-from-browser firefox

Speed, quality, and automation

• Push the parallelism. --concurrent-fragments 8 is a safe default; go higher on a fat connection, but back off if the CDN starts throwing 429s. For genuinely large jobs, hand the transfer to aria2c with --downloader aria2c.
• Always choose "chunked" for archival. It is Twitch's source rendition. Downloading 720p to save space is a decision you will regret the first time you want a real clip out of it.
• Automate the seven-day race. If you archive your own channel, a cron job that runs the download script against your latest VOD nightly means you never lose a broadcast to the retention timer. Pair it with the checksum step so you can prove nothing corrupted in storage.
• Render chat only when you need it. Keep the JSON as the archive; rendering to video is a re-encode and a large one. This is the same "keep the source, derive on demand" discipline that governs a good emulation setup — the philosophy we lay out in the RetroArch cores guide.

Capturing live, before the robots

For content you must have with intact audio, record the live stream rather than the VOD. Streamlink writes the broadcast straight to a file as it airs, which sidesteps both retention and DMCA muting — the mute is applied to the stored VOD, not to the live feed you are capturing:

# Record a live channel to a timestamped .ts file at source quality
streamlink --twitch-low-latency \
    twitch.tv/somechannel best \
    -o "capture-$(date +%F-%H%M).ts"

# Then remux the .ts to a clean .mp4 when the stream ends
ffmpeg -i capture-2026-08-15-2030.ts -c copy -movflags +faststart capture.mp4

Live capture is also the honest way to archive tournaments and one-off events that may never see a VOD at all — the same reason streamers obsess over their capture and input chain, right down to the keyboard, as we get into in the 2026 gaming keyboard roundup.

The Complete Configuration

Everything above, welded into one reusable script. Save it as grab-vod.sh, make it executable with chmod +x grab-vod.sh, and run it against any VOD or clip URL. It downloads at source quality, probes the result, writes a checksum, and keeps the metadata sidecar — the full archival pipeline in one command.

#!/usr/bin/env bash
# grab-vod.sh — pull a Twitch VOD/clip, verify it, and write provenance.
# Usage: ./grab-vod.sh <twitch-url> [quality]
#   quality defaults to "chunked" (source). Others: 1080p60, 720p60, audio_only
set -euo pipefail

URL="${1:?usage: grab-vod.sh <twitch-url> [quality]}"
QUALITY="${2:-chunked}"
OUTDIR="${TWITCH_ARCHIVE:-$HOME/Twitch}"
TEMPLATE="$OUTDIR/%(uploader)s - %(title)s [%(id)s].%(ext)s"

mkdir -p "$OUTDIR"

# 0) Never run a stale binary against a moving API.
yt-dlp -U || true

# 1) Metadata dry run — fail fast on deleted/gated VODs before any GB moves.
yt-dlp --skip-download --write-info-json -o "$TEMPLATE" "$URL"

# 2) The download itself: source quality, parallel fragments, aggressive retries.
yt-dlp \
  -f "$QUALITY" \
  --concurrent-fragments 8 \
  --retries 20 --fragment-retries 40 \
  --embed-metadata --no-part \
  --cookies-from-browser firefox \
  -o "$TEMPLATE" \
  "$URL"

# 3) Resolve the produced filename and verify streams + integrity.
FILE=$(yt-dlp --get-filename -f "$QUALITY" -o "$TEMPLATE" "$URL")
echo "== ffprobe =="
ffprobe -v error -show_entries stream=codec_type,codec_name \
  -of default=noprint_wrappers=1 "$FILE"

echo "== checksum =="
sha256sum "$FILE" | tee "$FILE.sha256"

echo "Archived: $FILE"

That script encodes the entire opinionated position of this guide: update first, dry-run before you commit disk, take source quality, authenticate as yourself, and never keep a file you have not verified and fingerprinted. It downloads your own content cleanly, it archives clips and public VODs for personal use, and it will not, cannot, and does not care to launder someone else's stream into a reupload — that last part is on you, and it always was.

For the primary distribution facts behind all of this — who publishes the app, on which stores, and how the version chaos shakes out across mirrors — the authoritative sources remain Google Play, the Apple App Store, and the Chrome Web Store for anything running in the browser, with version-tracking context from directories like TechSpot and the APK mirrors. Trust the stores for identity, trust the signature for integrity, and trust the checksum for everything after that.