Twitch VOD Download 2026: 12 Steps, 15-Min Setup

Twitch costs nothing in 2026. Watching, chatting, holding an account, even going live — all free, the way they have been for years. The one thing the platform will not do for free is keep your video. That distinction is the entire reason the phrase twitch download exists, and it is why you are here.

A little lore, because context is cheap and useful. Justin Kan spun Twitch out of the lifecasting curio Justin.tv and flipped the switch on 6 June 2011. Fifteen years later it moves roughly two million concurrent viewers on a slow afternoon — TwitchTracker logged an average of 1,997,256 concurrent on 1 June 2026 and 1,885,645 on 1 July 2026, a small but real decline heading into mid-year — while feeding 35 million-plus daily viewers and hosting 7.5 million-plus monthly streamers. Business of Apps pegs the platform at roughly $1.8 billion in revenue in 2024. This is an Amazon-scale firehose. And it has a fourteen-day memory.

That last number is the one that matters. Your past broadcasts are not archived for you; they are held on a countdown. If you have ever wanted the file — for a highlight reel, a legal record, a DMCA dispute, a speedrun submission, or the simple retro-preservation instinct that anything unpreserved is already half-deleted — you have to pull it yourself, and you have to do it before the timer runs out. This tutorial is the mechanically precise, no-marketing way to do that: five routes, one 12-step command-line workflow, and a complete working configuration you can paste and forget.

What 'Twitch Download' Actually Means

The search term is three questions wearing one trenchcoat. Before you touch a tool, decide which one you are actually asking, because the answers do not overlap.

Three searches wearing one trenchcoat

The first meaning is get the Twitch app — the mobile or desktop client for watching. That is a thirty-second app-store task covered in Route 1 and it requires no skill, so we will dispatch it quickly. The second meaning is get the broadcasting software — Twitch Studio, the Desktop App, or, if you have sense, OBS. That is a setup question, handled near the end. The third meaning — the one with any technical substance and the only one worth a long-form tutorial — is get the video off the platform: VODs, clips, highlights, and chat, downloaded to a file you control. Everything between the prerequisites and the config block is about that third meaning.

The clock you are actually racing

Here is the fact that turns 'download' from convenience into urgency. A regular user's VODs (past broadcasts) expire after 14 days. If you are a Twitch Partner or Affiliate, you get 60 days — Affiliate status itself is not free either, requiring 50 followers plus 500 broadcast minutes, 7 unique stream days, and an average of 3 concurrent viewers over 30 days, but that is a separate hurdle. The practical upshot is blunt: unless you actively pull the file, a normal streamer's six-hour Tuesday session is gone two weeks later, permanently, with no undo and no support ticket that will bring it back. Twitch does not warn you the morning it deletes. The countdown is silent.

What never expires — clips and highlights

Two categories dodge the guillotine. Clips do not expire; a clip someone cut from your stream can sit on Twitch indefinitely. Highlights do not expire either, because a highlight is a manually curated segment you carved out of a VOD and told Twitch to keep. This asymmetry is the single most useful thing to internalize: if you cannot download a full VOD before day 14, the fallback preservation move is to convert the moments you care about into highlights first, which resets their lifespan to forever, and download them at leisure. The full-broadcast source, though, still dies on schedule — highlighting saves the segment, not the whole.

Prerequisites: Versions and Hardware

You are going to be doing this on a computer, not a console — which, given that PC is on track to overtake console on revenue by 2028, is where most of you already are. Here is the exact stack.

Hardware and disk math

The CPU is nearly irrelevant here, because the correct workflow performs no re-encoding — it copies streams, it does not transcode them. Any machine from the last decade is fine. What you need is disk, and you need to respect the arithmetic. Twitch source for a 1080p60 broadcast runs about 6000 kbps of video. That is roughly 2.7 GB per hour, so a typical six-hour marathon lands near 16 GB, and a channel's back-catalogue of two dozen such VODs is a third of a terabyte before you have blinked. Provision accordingly, and prefer an SSD or a fast NAS target — thousands of small HLS fragments hammer random writes, and a tired 5400 rpm drive will bottleneck the download harder than your network does. A stable wired connection beats Wi-Fi for multi-hour pulls; a dropped fragment mid-download is a retry, and retries compound.

The software stack (versions)

Four tools cover every scenario. Install what you need for your route; you do not need all four.

• yt-dlp — latest nightly build. This is the workhorse for VODs and clips. Do not use the ancient youtube-dl it forked from; Twitch extractors rot fast and only the maintained fork keeps pace.
• FFmpeg 7.x (7.1 or newer) — required by yt-dlp to merge HLS fragments and to remux containers. Non-negotiable for a clean file.
• TwitchDownloader — latest release, GUI on Windows or the cross-platform TwitchDownloaderCLI. This is the only good tool for downloading chat and rendering it back to video.
• Streamlink 7.x (latest) — for recording a stream live to disk as it airs, which sidesteps the expiry problem entirely.

One-line installs per platform

Pick your platform. The pipx route isolates yt-dlp in its own environment and is the least fragile; the standalone binary from the yt-dlp GitHub repository avoids Python entirely if you prefer.

# Linux (Debian/Ubuntu)
sudo apt update && sudo apt install -y ffmpeg pipx
pipx install yt-dlp
pipx install streamlink

# macOS (Homebrew)
brew install ffmpeg yt-dlp streamlink

# Windows (winget, run in PowerShell)
winget install yt-dlp.yt-dlp
winget install Gyan.FFmpeg
winget install Streamlink.Streamlink

TwitchDownloaderCLI is a single self-contained binary; grab the archive for your OS from the TwitchDownloader releases page, unzip it, and put it on your PATH. No installer, no runtime — it is one file.

Route 1: The Official Apps

If your 'download' meant the client, this is the whole section. It is trivial, but there is exactly one non-obvious thing worth knowing.

The four official stores

In 2026 the officially sanctioned ways to install Twitch are the Apple App Store, the Google Play Store, the Amazon Appstore, and the Microsoft Store. On Google Play the listing names the publisher as Twitch Interactive, Inc. and carries real support contact details — the official Android listing shows android@twitch.tv and a San Francisco corporate address. Match the publisher name before you tap install. Anything sideloaded from a third-party APK mirror is a security question you are answering with your account credentials, and the answer is usually 'no.'

Desktop app vs browser

There is a Twitch Desktop App for Windows and Mac. It exists. It wraps the same experience the browser gives you, plus a few integrations. For pure viewing, the browser is lighter and gets features first; the desktop app mainly earns its keep if you want a persistent, chrome-free window. Neither one downloads video — do not go hunting a hidden 'save' button in the client, because it is not there.

Why this route is a dead end for archiving

This is the deadpan truth the app-store route buries: the official clients are built to stream content to you, never to hand you the file. There is no 'download this VOD' button for viewers anywhere in the app. Every archiving method below reaches around the client, not through it. If you came for the app, you are done. If you came for the video, the app was never going to help you, and the next four routes are the actual tutorial.

Route 2: Your VODs From the Dashboard

If the VOD is yours, Twitch gives you a sanctioned download button. This is the cleanest, most legally uncomplicated route, and it should be your first choice for your own content.

The Creator Dashboard path

Log in, open the Creator Dashboard, and navigate Content → Video Producer. Each past broadcast has a three-dot menu; open it and choose Download. Twitch prepares the file and serves it to you directly. No third-party tool, no cookies, no command line — this is Twitch handing you your own data, exactly as it should.

Creator Dashboard
  └─ Content
       └─ Video Producer
            └─ [your VOD] ⋮  (the three-dot menu)
                 └─ Download

What Twitch actually hands you

The dashboard download is typically delivered at source quality, meaning the saved file preserves the original broadcast bitrate without re-encoding. This matters more than it sounds. Every GUI 'downloader' that promises to 'convert' your VOD is transcoding it — throwing away bits, softening detail, and adding hours of CPU time for a strictly worse file. The dashboard route, like the yt-dlp route below, is a byte-faithful copy of what you streamed. If you want the original, do not let anything re-encode it. Insist on source.

Where the dashboard route falls down

Three limits push people to the command line. First, it only works for your own channel — you cannot dashboard-download someone else's VOD. Second, the browser download of a multi-hour source file is a single fragile HTTP stream; if it drops at 90%, you often start over. Third, and fatally, it is still bound by the 14-day / 60-day expiry — the button vanishes when the VOD does. For your own recent streams it is perfect. For everything else, or for anyone who wants resumable, parallelized, scriptable downloads, keep reading.

Route 3: The 12-Step yt-dlp Workflow

This is the core of the tutorial and the method I actually use. yt-dlp is a command-line downloader that speaks Twitch's HLS natively, pulls source quality, parallelizes fragment fetches, resumes cleanly, and never re-encodes unless you tell it to. Setup is about fifteen minutes once; after that each archive is one command. Twelve steps, each with the reason it exists so you understand what you are doing rather than pasting blind.

Steps 1–4: Install, verify, and get the URL

1. Install yt-dlp. Use the pipx or Homebrew line from the prerequisites, or the standalone binary. Rationale: the maintained fork is the only build whose Twitch extractor still works; last year's binary will silently fail on this year's manifest format.
2. Install FFmpeg and put it on PATH. Rationale: Twitch source arrives as thousands of HLS fragments. yt-dlp streams them, but FFmpeg is what stitches and remuxes them into one clean container. Without it on PATH you get an error or a pile of loose fragments.
3. Verify both binaries before you trust them. A ninety-second check saves a six-hour mistake.

   yt-dlp --version
   ffmpeg -version | head -n 1

   Expected output:

   2026.07.21
   ffmpeg version 7.1.1 Copyright (c) 2000-2026 the FFmpeg developers

   Rationale: if either command errors with 'not found,' your PATH is wrong and nothing downstream will work — fix it now, not at 12% of a 16 GB pull.
4. Get the VOD URL. From the video page or the Creator Dashboard, copy the address; you want the numeric video ID in twitch.tv/videos/<id>. Rationale: the ID is what every subsequent command keys on. Clips use a different URL shape and are covered in Route 4.

Steps 5–8: Probe, dry-run, download at source, name it

5. Probe available formats first.

   yt-dlp -F https://www.twitch.tv/videos/2384756019

   Expected output:

   [twitch:vod] Extracting URL: https://www.twitch.tv/videos/2384756019
   [info] Available formats for 2384756019:
   ID         EXT RESOLUTION  FPS │    TBR PROTO │ VCODEC       ACODEC
   audio_only mp4 audio only      │  ~128k https │ audio only   mp4a.40.2
   160p       mp4 284x160     30  │  ~230k https │ avc1.4D401F  mp4a.40.2
   360p       mp4 640x360     30  │  ~630k https │ avc1.4D401F  mp4a.40.2
   480p       mp4 852x480     30  │ ~1500k https │ avc1.4D401F  mp4a.40.2
   720p60     mp4 1280x720    60  │ ~3000k https │ avc1.4D401F  mp4a.40.2
   Source     mp4 1920x1080   60  │ ~6000k https │ avc1.640028  mp4a.40.2

   Rationale: confirms Source exists before you commit. On non-partnered channels the transcoded tiers (720p, 480p) may be absent and Source is your only real option — good to know up front.
6. Do a metadata dry run.

   yt-dlp --skip-download --print title --print duration_string \
     https://www.twitch.tv/videos/2384756019

   Rationale: this resolves the VOD and prints its title and length without downloading a byte. If it errors here — 403, or 'unable to download JSON' — you have an access or expiry problem to solve before you waste bandwidth.
7. Download at source with parallel fragments.

   yt-dlp -f Source -N 8 https://www.twitch.tv/videos/2384756019

   Rationale: -f Source takes the original bitrate with no re-encode; -N 8 fetches eight HLS fragments concurrently, which on a decent connection is several times faster than the default single stream. Do not go wild with -N — past 8–16 you invite rate-limiting.
8. Set a sane output template.

   yt-dlp -f Source -N 8 \
     -o '%(uploader)s/%(upload_date)s - %(title).80s [%(id)s].%(ext)s' \
     https://www.twitch.tv/videos/2384756019

   Rationale: files land in a per-streamer folder, sort chronologically by date, cap the title length so Windows does not choke on a 260-character path, and keep the ID for deduplication. Future-you, staring at a folder of 200 VODs, will be grateful.

Steps 9–12: Auth, muted segments, verify, remux

9. Authenticate for sub-only or private VODs.

   yt-dlp -f Source -N 8 --cookies-from-browser firefox \
     https://www.twitch.tv/videos/2384756019

   Rationale: Twitch gates subscriber-only VODs behind your logged-in session. --cookies-from-browser lends yt-dlp your browser's Twitch cookies so it sees what you see. Log into Twitch in that browser first; if cookies expire you get a 403 and simply refresh them.
10. Understand muted segments before you are surprised by them. Twitch runs audio-recognition on VODs and mutes any stretch it flags as copyrighted music — the silence is baked into the source itself. Rationale: yt-dlp will download the muted VOD faithfully, gaps and all; there is no flag that un-mutes it, because the audio is not there to recover. If music silence is unacceptable, the only fix is to capture the stream live (Route 5) before Twitch's scanner touches it.
11. Verify file integrity with ffprobe.

    ffprobe -hide_banner 'TheMachine/20260728 - Six Hours of Silent Hill .mp4'

    Expected output (trimmed):

    Duration: 05:58:11.98, start: 0.000000, bitrate: 6021 kb/s
      Stream #0:0: Video: h264 (High), yuv420p, 1920x1080, 59.94 fps
      Stream #0:1: Audio: aac (LC), 48000 Hz, stereo, 128 kb/s

    Rationale: confirm the duration matches the broadcast and both streams are present. A file that ends at 02:11 when the stream ran six hours was truncated — re-run before the VOD expires.
12. Remux only if a tool refuses the container.

    ffmpeg -i input.ts -c copy output.mp4

    Rationale: yt-dlp usually delivers a clean MP4 already. But live captures and some fragmented pulls land as raw .ts, which chokes certain editors. -c copy rewraps the exact same streams into MP4 in seconds with — again — no re-encoding. If your file already plays and edits, skip this step entirely.

That is the whole workflow. Steps 1–3 are one-time. Steps 4–12 collapse, in daily use, to a single command you will memorize. The full documentation for every flag lives in the yt-dlp README, which is worth ten minutes of skimming once.

Route 4: Clips, Chat, and Highlights

yt-dlp handles video superbly and chat not at all. For clips-plus-chat-plus-rendering, the purpose-built tool is TwitchDownloaderCLI, and it does one thing yt-dlp cannot: reconstruct the chat log as data and paint it back onto the video.

Clips and highlights that outlive the VOD

Remember the asymmetry: clips and highlights never expire, so they are often the only surviving trace of a stream whose VOD died on day 14. Download them while you can. yt-dlp takes a clip URL directly:

yt-dlp 'https://clips.twitch.tv/CrunchySavageWolfKappa'

TwitchDownloaderCLI does the same by slug or ID, and is the better choice when you also want the chat that scrolled during the moment:

TwitchDownloaderCLI clipdownload --id CrunchySavageWolfKappa -o clip.mp4
TwitchDownloaderCLI videodownload --id 2384756019 -q source -o vod.mp4

Downloading chat as data

Chat is where Twitch's culture actually lives, and it is the first thing lost when a VOD expires. Pull it as structured JSON so it is future-proof and searchable:

TwitchDownloaderCLI chatdownload --id 2384756019 -o chat.json --embed-images

The --embed-images flag bakes emotes and badges into the file so the archive still renders correctly years later, after the third-party emote CDNs have rotated their URLs and gone dark. Raw JSON is the format that survives; a rendered MP4 is a convenience layered on top of it.

Rendering chat back to video

To watch chat replay alongside the stream — or to composite it into an edit — render the JSON to a transparent or solid-background video:

TwitchDownloaderCLI chatrender -i chat.json -o chat.mp4 \
  --framerate 60 --background-color \"#0e0e10\" --font-size 18

Now you hold three files — vod.mp4, chat.json, and chat.mp4 — which together are a complete, self-contained record of the broadcast that owes Twitch nothing. Full command reference is in the TwitchDownloader documentation.

Route 5: Streamlink Live-to-Disk

Every route above pulls video after the broadcast, which means it is subject to the expiry clock and to Twitch's DMCA audio muting. Streamlink attacks the problem from the other end: it records the stream as it airs, straight to your disk, before Twitch's systems have finished with it.

Recording the stream as it airs

The base command points Streamlink at a live channel, asks for the best quality, and writes it to a file:

streamlink https://www.twitch.tv/somestreamer best -o 'somestreamer_20260731.ts'

Streamlink writes an MPEG-TS stream, which is why the extension is .ts — it is the format that survives an interrupted recording without corrupting the whole file. When the stream ends, remux to MP4 with the FFmpeg one-liner from step 12. Because you captured the live source, the muted-segment problem does not apply: Twitch's copyright scanner mutes the hosted VOD, not your local file. This is the single strongest reason to record live if music matters to you.

Killing ad-injection with the right flags

Twitch splices ad segments into the HLS manifest, and left alone they can land in your recording as garbled frames or a stall. Streamlink can strip them:

streamlink --twitch-disable-ads \
  --twitch-low-latency \
  --retry-streams 5 --retry-max 10 \
  https://www.twitch.tv/somestreamer best -o 'capture.ts'

--twitch-disable-ads keeps ad segments out of the file; --twitch-low-latency tightens the buffer; and the retry flags let Streamlink wait for a stream that has not started yet or reconnect through a brief drop, which is what you want when you queue a recording before the streamer goes live.

The config file that makes it one command

Typing those flags every time is how you eventually forget one. Put them in Streamlink's config file — full option list at the Streamlink documentation — and the command collapses back to streamlink URL best -o file.ts. The exact file is in the final configuration section below.

Five Pitfalls That Corrupt Your Archive

Seven, actually — I refuse to leave two out because they cost the most time. These are the failures that produce a file which looks downloaded but is quietly broken.

Timing, muting, and ads

Pitfall 1 — downloading a VOD that is still live. If you point yt-dlp at a broadcast that has not ended, you get a partial file and possibly a confusing error, because the manifest is still growing. Fix: wait for the 'Live' badge to clear and the VOD to finish processing before you pull it, or use Route 5 to record live on purpose. Pitfall 2 — the silent stretches. If chunks of your downloaded audio are dead silent, that is Twitch's DMCA muting baked into the source, not a bug in your tool. There is no post-hoc fix; capture live next time. Pitfall 3 — ad segments corrupting the stream. Injected ads can wedge a download or scramble frames. Fix: keep yt-dlp on the latest nightly, and for live captures use Streamlink's --twitch-disable-ads.

Disk, filenames, and cookies

Pitfall 4 — running out of disk mid-pull. At ~2.7 GB/hour a long marathon eats space fast; a download that dies at 95% because the partition filled is pure waste. Fix: check free space against the duration before you start, using the disk math from the prerequisites. Pitfall 5 — illegal filename characters. A stream titled with a colon, slash, or question mark will fail to write on Windows. Fix: use the output template from step 8, or add --restrict-filenames to force filesystem-safe names. Pitfall 6 — expired cookies on sub-only VODs. A 403 on content you can watch in the browser almost always means the cookies yt-dlp grabbed have gone stale. Fix: re-open Twitch in the source browser, confirm you are logged in, and re-run.

Rate limits and the batch trap

Pitfall 7 — hammering Twitch during a batch. Firing twenty concurrent downloads with -N 16 each is a fast way to get your IP throttled, at which point everything slows to a crawl or starts 429-ing. Fix: throttle deliberately with --sleep-requests 1.5 and a modest -N 8, and run VODs sequentially rather than all at once. Patience is faster than a rate-limit timeout. Preservation is a marathon; treat the platform's servers the way you would want yours treated.

Troubleshooting: 10 Failure Modes

When something breaks, read the error before you panic — Twitch downloaders fail loudly and specifically, and the message almost always names the fix.

The table

Symptom	Likely cause	Fix
HTTP Error 403: Forbidden	Sub-only/private VOD, no auth	Add --cookies-from-browser firefox; confirm you are logged in
Unable to download JSON metadata	VOD deleted or past its 14/60-day expiry	Nothing — it is gone. Preserve sooner next time
Long silent gaps in the audio	Twitch DMCA muted the segment	Expected; unrecoverable. Record live via Streamlink
Download stalls at a fixed %	Ad segment or a dead fragment	Add --fragment-retries infinite; update yt-dlp
ffmpeg not found	FFmpeg missing from PATH	Install FFmpeg and add its folder to PATH
Write error / illegal filename (Windows)	Colon or slash in the title	Add --restrict-filenames or use the output template
Painfully slow single-threaded pull	Default one-fragment-at-a-time fetch	Add -N 8 for concurrent fragments
.ts file rejected by editor	Container mismatch	ffmpeg -i in.ts -c copy out.mp4
Chat missing from the download	yt-dlp does not do chat	Use TwitchDownloaderCLI chatdownload
1080p/720p absent in -F	Non-partner channel has no transcodes	Use -f Source — it is the only tier

Reading the error before you panic

The two categories to distinguish are access errors and gone errors. A 403 is access — you can fix it with cookies. 'Unable to download JSON metadata' on a VOD that no longer appears on the channel is gone — no flag resurrects deleted content. Ninety percent of 'yt-dlp is broken' reports are actually an out-of-date binary meeting a changed Twitch manifest; before anything else, run yt-dlp -U and try again.

When the VOD is simply gone

Accept the hard cases. If a regular user's broadcast passed day 14 and was never highlighted or clipped, it is deleted at the source and there is no archive to reach — not on Twitch, not through any tool, not via support. The lesson is procedural, not technical: the fix for 'the VOD is gone' is a habit that downloads within the window, which is exactly what the automation section builds.

Advanced: Automation and Batch Archiving

Manual downloads solve today's problem. Automation solves the expiry problem permanently, by pulling every new VOD before the clock starts. This is where a casual downloader becomes an archivist.

Batch a whole channel

Put a list of VOD URLs in a text file and feed it to yt-dlp with -a, and pair it with --download-archive so already-pulled VODs are skipped on re-runs:

yt-dlp -f Source -N 8 \
  --download-archive done.txt \
  --write-info-json \
  -o '%(uploader)s/%(upload_date)s - %(title).80s [%(id)s].%(ext)s' \
  -a urls.txt

--download-archive done.txt records every completed ID so the command is safely idempotent — run it daily and it only ever fetches what is new. --write-info-json saves a sidecar of title, description, timestamps, and duration, which is the metadata a bare MP4 loses.

Automate with cron / Task Scheduler

Wrap that command in a script (the final config section has a complete one) and schedule it. On Linux or macOS, a cron entry that runs nightly at 03:00:

0 3 * * * /home/you/bin/twitch-archive.sh >> /home/you/logs/twitch.log 2>&1

On Windows, the same script under Task Scheduler with a daily trigger. Now VODs are pulled well inside the 14-day window with zero human attention — the archive maintains itself. This is the same set-and-forget discipline behind our other step-by-step maintenance walkthroughs, like the 13-step PS5 cache clear; a good routine you never think about beats a heroic manual effort you forget to do.

Metadata, archives, and NAS

Point the output at a NAS or a dedicated archive drive and let the per-streamer folders accumulate. Keep the .info.json sidecars and the chat.json files next to the video — a preservation copy is video plus metadata plus chat, not just an orphan MP4. And review your capture chain end to end while you are at it: if you are also the one streaming, the quality of your archive starts at the source, which is a fine excuse to look hard at your monitor, like the ROG Swift PG32UCDM 4K 240Hz OLED, and your input gear such as the G Pro X Superlight 2. Garbage in, archived forever.

Twitch Studio, the Desktop App, and OBS

If your 'download' meant broadcasting software, read this before you install the wrong thing — because the most-recommended answer is a corpse, and the internet has not caught up.

Twitch Studio is a ghost

Plenty of 2026 write-ups still describe Twitch Studio as Twitch's own broadcasting app, a free download for Windows and macOS. The installer does still exist and still runs. But here is the correction the marketing copy omits: Twitch discontinued Twitch Studio, ending support on 30 May 2024, after it accounted for under 4% of hours streamed and got roughly ten days' notice before the plug came out. It is unmaintained software. Do not build a 2026 streaming setup on a tool its own maker abandoned two years ago. There is a grim symmetry worth noting for the lore: the TwitchCon Rotterdam roundup Twitch posted on 30 May 2026 landed exactly two years to the day after Studio's obituary. The platform moves on; the guides do not.

The Desktop App is not OBS

Separately, a Twitch Desktop App for Windows and Mac exists, but do not confuse a viewing/companion client with broadcasting software — it is not a production suite and will not run a serious stream. The distinction trips people who read 'desktop app' and assume 'the thing that broadcasts.' It is not.

Use OBS — settings that match Twitch

Most experienced streamers use OBS Studio, and they are right to; it is more capable, more widely supported, free, and actively developed. If you are setting up to stream, install OBS and configure it to Twitch's ingest spec: for 1080p60, use 6000 kbps CBR with a 2-second keyframe interval — note that is kilobits per second, not the kilobytes some guides mangle it into, and 6000 kbps is the ceiling Twitch's non-partner ingest reliably accepts. Do not overthink the encoder: hardware NVENC or AV1 if your GPU offers it, x264 on 'veryfast' if it does not. And close the loop back to this tutorial's real subject — whatever you broadcast, it still expires in 14 days, so point the yt-dlp automation at your own channel and archive yourself.

The Complete Working Configuration

Everything above, distilled into files you can paste. Three artifacts: a yt-dlp config, a Streamlink config, and a one-command archive script.

The yt-dlp config file

Save as ~/.config/yt-dlp/config on Linux/macOS or %APPDATA%\yt-dlp\config.txt on Windows. Every future yt-dlp invocation inherits these defaults, so a bare yt-dlp URL now downloads source quality, named correctly, resumable, and rate-polite.

# ~/.config/yt-dlp/config — Twitch VOD archival defaults
-f Source
-N 8
--concurrent-fragments 8
--fragment-retries infinite
--retries 20
--sleep-requests 1.5
--restrict-filenames
--write-info-json
--download-archive ~/twitch/done.txt
-o ~/twitch/%(uploader)s/%(upload_date)s - %(title).80s [%(id)s].%(ext)s
# For sub-only content, uncomment and set your browser:
# --cookies-from-browser firefox

The Streamlink config file

Save as ~/.config/streamlink/config (Linux/macOS) or %APPDATA%\streamlink\config (Windows). Now live recording is just streamlink URL best -o file.ts with ads stripped and retries handled.

# ~/.config/streamlink/config — live capture defaults
twitch-disable-ads
twitch-low-latency
retry-streams=5
retry-max=10
default-stream=best
# Optional auth for sub-only live:
# twitch-api-header=Authorization=OAuth YOUR_TOKEN_HERE

The one-script archive wrapper

Save as twitch-archive.sh, make it executable with chmod +x twitch-archive.sh, and schedule it via cron or Task Scheduler. It reads a channel's VOD URLs from urls.txt, pulls anything new at source, verifies each file's duration, and logs the result. This is the whole tutorial as a single self-running artifact.

#!/usr/bin/env bash
# twitch-archive.sh — nightly source-quality VOD archiver
set -euo pipefail

ARCHIVE_DIR=\"$HOME/twitch\"
URL_LIST=\"$HOME/twitch/urls.txt\"

mkdir -p \"$ARCHIVE_DIR\"
cd \"$ARCHIVE_DIR\"

# Keep the binary current — stale extractors are the #1 failure.
yt-dlp -U || true

# Pull everything new; config file supplies -f Source, -N 8, naming, archive.
yt-dlp -a \"$URL_LIST\"

# Verify each freshly written mp4 actually has a duration.
find \"$ARCHIVE_DIR\" -name '*.mp4' -mtime -1 -print0 |
while IFS= read -r -d '' f; do
  dur=$(ffprobe -v error -show_entries format=duration \
        -of default=nk=1:nw=1 \"$f\" 2>/dev/null || echo 0)
  printf '%s\t%ss\n' \"$f\" \"${dur%.*}\"
done

echo \"Archive run complete: $(date)\"

That is the complete machine. The 14/60-day expiry facts that started this article are the reason the script exists; the platform-scale numbers and the daily concurrency figures are the reason the queries never stop. Twitch will keep deleting your video on a fourteen-day timer. Now you have a workflow that beats the timer every single night, at source quality, with no re-encode, and no button that was never going to be there. Point it at your own channel first, and stop losing your own broadcasts to a countdown you were never shown.