Twitch Download 2026: App + VODs in 14 Steps, 25 Min

Type twitch download into any search box and two entirely different crowds come shoving through the same doorway. One crowd wants the Twitch application — the thing that plays live streams on a phone, a laptop, or a television. The other wants to pull a specific past broadcast, clip, or highlight off Twitch and keep it as a file, usually before the platform's retention clock deletes it. Same three words. Opposite problems. Almost no shared tooling.

This tutorial handles both, in that order, because you cannot archive a VOD you cannot watch, and you cannot watch reliably through an app you grabbed from a sketchy mirror. We will get the official client onto every platform Twitch actually ships one for, confirm it is the genuine article and not a re-signed impostor, and then move to the part the search engines are really asking about: getting the video out and onto a disk you control.

A word on why a retro-gaming site cares. Our interest in downloading a Twitch video is not idle. Speedrun history, tournament VODs, the one stream where somebody finally cleared the level nobody could clear — that footage lives on Twitch under a retention policy that deletes it on a timer. Preservation is the job. The law and the Terms of Service both have opinions about how you go about it, and we are going to respect them, because getting an account nuked to save a forty-minute run is a bad trade.

Why 'Twitch Download' Means Two Things

Before you download anything, you have to know which of two unrelated tasks you are actually performing. The search term hides the fork in the road.

Two Jobs Wearing One Search Term

The first job is installing the client. Twitch ships native apps for Android, iOS, Windows, macOS, Amazon Fire tablets, Fire TV, and Android TV. Each of those is a distinct build with its own version number and its own update cadence — and, the part people miss, its own correct source. The Android phone build does not come from the same place as the Fire TV build, and neither should come from a random APK aggregator unless you know exactly what you are doing.

The second job is exporting content. A Twitch VOD (Video On Demand, the saved copy of a past live broadcast), a clip (a short, shareable cut), a highlight (a curated permanent segment), or one of the newer stories is a piece of media sitting behind Twitch's player. Twitch does not put a download button on it. Getting a local copy means a browser extension, a command-line tool, or a desktop utility — and it means understanding what you are and are not allowed to keep.

These two jobs share nothing except the word 'download'. Confusing them is how people end up installing a 'Twitch downloader' that is neither the app nor a legitimate archiver, but a bundle of adware wearing the logo. We are going to keep them strictly separate throughout.

The Preservation Case for Keeping a Local Copy

Twitch keeps past broadcasts for a limited window. The exact number has drifted over the years and depends on your account tier, but it has historically ranged from roughly a week for a standard account to around sixty days for Partners, Turbo, and Prime subscribers. After that window, the VOD is gone. Highlights and uploads persist; the raw past broadcast does not. If the run you care about is a past broadcast rather than a saved highlight, you are on a clock whether you realize it or not.

For a games publication, this is not abstract. Entire eras of competitive and speedrunning footage have quietly evaporated because nobody pulled a copy before the retention timer fired. If you are the sort of person who keeps ROMs verified against a database and cartridges in anti-static sleeves, the logic here is identical: the artifact is fragile, the platform is not a promise, and the only copy you can rely on is the one on your own storage.

What We Are Not Going To Do

We are not going to re-host anyone's stream, strip a creator's mid-roll ads and republish, or bulk-scrape a channel to reupload it elsewhere. Twitch's Terms of Service prohibit reproducing or distributing content except through the features Twitch provides, and downloading someone else's VOD to redistribute is both a ToS violation and, depending on the footage, a copyright one. Archiving for personal, private reference — the digital equivalent of taping a match off the television to rewatch — is the use case this guide supports. Keep it personal, keep it offline, do not monetize somebody else's work. The Machine will not help you get sued.

Prerequisites: Versions, Hardware, Accounts

Version numbers matter here because the mobile app iterates fast and the archiving tools change even faster. Get your inventory straight before you start.

Software Versions You Actually Need

As of this writing the moving parts look like this:

Twitch mobile (Android)   30.8.0   (17 Aug 2026) - newest tracked build
Twitch mobile (Android)   30.7.2   (14 Aug 2026) - prior build
Twitch Android TV / Fire  13.0.0.2 (11 Aug 2025) - separate track
Twitch Fire tablet        23.0.0   (12 Feb 2025) - separate track
Twitch desktop (Win/mac)  from twitch.tv/downloads (rolling)
yt-dlp                    latest release from GitHub (self-updating)
TwitchDownloader          latest release from GitHub
Twitch VOD Downloader     3.26     (21 Feb 2026) - Chrome extension
Browser                   Chrome/Chromium 120+ or Firefox 115+ ESR
Python (for yt-dlp)       3.9+ for the pip build; the static build needs none

Those Android figures are not guesses. The 30.8.0 build dated 17 August 2026 and the 30.7.2 build from 14 August 2026 both came off third-party Android distribution pages that mirror Google Play, and the three-day gap between them tells you everything about the cadence: Twitch pushes mobile builds constantly. Earlier in 2026 the same tracking showed version 29.7.1 on 2 June 2026 at 83.12 MB, version 29.2.2 at 93.4 MB on 27 April 2026 (via APKPure, listed as 'Twitch Live Streaming'), version 28.4.1 BETA on 20 March 2026 at 96.61 MB with the next listed build, 28.7.1, arriving just three days later on 23 March 2026, and version 27.9.1 back on 27 January 2026 at 103.37 MB — a build a Spanish Uptodown page had racked up more than 7.8 million downloads on by itself. The file size wanders between roughly 83 and 103 MB depending on the build and the mirror's packaging, which is worth memorizing before you eyeball whether a download looks legitimate.

Hardware and Storage

The app itself is trivial: any Android 8.0+ phone, any iPhone on a currently supported iOS, or a Windows 10 / Windows 11 or modern macOS machine will run the client comfortably. If you intend to watch Twitch on something less conventional — a gaming handheld, say — the app runs fine on Android-based devices, and even the odd ones without it will reach the web player in a browser. If you are still deciding which handheld to watch on in the first place, that is a separate rabbit hole we have already been down in our Retroid Pocket 6 versus 5 comparison.

Archiving is where storage becomes the constraint. A source-quality VOD is not small. Twitch broadcasts at up to 1080p60, which for a long stream means multiple gigabytes per hour; a single archived tournament day can run 20 to 40 GB. Budget accordingly, because a spare 1 TB drive fills faster than you expect once you start pulling full past broadcasts rather than two-minute clips. For the download itself, a wired connection beats Wi-Fi for anything over an hour — a dropped connection mid-pull on a three-hour VOD is a special kind of misery, and while good tools resume, not every one does.

Accounts, Permissions, and the Law

You need a Twitch account to use the app in any meaningful way and, for some archiving methods, to reach subscriber-only or age-gated VODs. Where a tool asks for authentication, it is usually reading your browser cookies to prove to Twitch that you are allowed to see the content — that is normal for private or sub-only material and does not, by itself, mean the tool is malicious. What you should never do is paste your Twitch password into a third-party downloader. Legitimate tools use OAuth or your existing browser session; they do not need your credentials typed into their own box. Anything that asks for your raw password is a phishing attempt wearing a helpful costume.

The Official Download Paths (And the Fakes)

There is exactly one correct source per platform, and a much larger number of incorrect ones. Here is the map.

Mobile: Google Play Is the Source of Truth

For Android, the canonical download is the Google Play listing for Twitch: Live Streaming. The publisher shown there is Twitch Interactive, Inc., the support contact is android@twitch.tv, and the registered address is 350 Bush St Fl 2, San Francisco. Those three details are your authenticity checklist. If a listing claims to be Twitch but the developer name is off by a word, the support email is a free webmail address, or the company address is missing, you are not looking at the real thing.

As of 19 August 2026, that Play listing showed the app as actively maintained, with the store page itself updated that same day — a useful signal, because a legitimate first-party app on a platform this size gets touched constantly, and a listing that has sat untouched for a year is a red flag. On iOS the equivalent is the App Store listing under the same publisher; Apple's review process makes impostors rarer there, but the same publisher-name check still applies.

Desktop: twitch.tv/downloads, Not the Microsoft Store

For Windows and macOS the official source is twitch.tv/downloads. A 2026 walkthrough from recharge.com makes the point bluntly: the desktop app in 2026 is obtained directly from that page, it is the standard install path for Windows 10 and Windows 11, and the Microsoft Store is not the current source for the newest version. That last part trips people up, because searching 'Twitch' in the Microsoft Store returns something — it is simply not guaranteed to be the current build. A July 2026 TechSpot catalog entry, for context, listed a cross-platform Twitch App at version 27.1.0 for Windows, macOS, and Android at 91.6 MB, which is the kind of aggregated reference that is fine for a sanity check but should never replace going to the source.

One correction to that recharge.com guide, because The Machine reads the footnotes: it lists the download page as the place to get 'the Windows app and Twitch Studio.' Twitch Studio — Twitch's own broadcasting software — had its support ended by Twitch on 30 May 2024. It is deprecated. If your goal is to broadcast rather than watch or archive, do not build a workflow on a dead tool; use OBS Studio (version 32.1.2 as of April 2026) instead, which is what the overwhelming majority of streamers already run. The desktop Twitch app remains perfectly valid for watching, following, and managing your channel; it is Twitch Studio specifically that you should treat as a museum piece.

TV, Fire, and the Separate Tracks

Television devices are their own world. Twitch maintains distinct builds for Android TV and Amazon Fire hardware, versioned completely separately from the phone app. The archive at APKMirror's Twitch Interactive, Inc. page records, for example, an Android TV build at version 13.0.0.2 uploaded 11 August 2025, a Fire TV / Android TV build at 13.0.0.1 uploaded 6 September 2025, and a Fire tablet build at version 23.0.0 uploaded 12 February 2025. Notice the version numbers: 13.x for TV, 23.x for the Fire tablet, 30.x for the phone. They are not the same lineage, and you cannot sideload the phone build onto a Fire TV and expect the ten-foot interface to work.

On a Fire TV or Fire tablet, the correct store is Amazon's Appstore, which serves the TV-appropriate build for you. On an Android TV, it is the Play Store on the device itself. Manual APK sideloading from a mirror is a legitimate last resort for a TV device that cannot reach its store — but it is a last resort, and it comes with the verification homework in the next section firmly attached.

Installing the Twitch App: 14 Steps

This is the core procedure. It assumes you want the client installed and verified on your primary platform, with the sideload path documented for the awkward cases. Every step includes the reason it exists, because a step you do not understand is a step you will skip at the worst possible moment.

The Fourteen-Step Install

Work straight down the list. Steps 7 through 9 apply only if you are sideloading an APK; everyone else skips them.

1. Identify your platform precisely. Phone, tablet, desktop, or TV — and which OS. Rationale: the correct source differs per platform, and the version lineages (30.x phone, 23.x Fire tablet, 13.x TV) do not cross. Getting this wrong is the single most common failure.
2. Go to the first-party source for that platform. Google Play or the App Store for phones, twitch.tv/downloads for desktop, the device's own store for TV and Fire. Rationale: first-party sources sign their builds and push updates. Mirrors do neither on your behalf.
3. Verify the publisher before you tap install. Confirm 'Twitch Interactive, Inc.', support android@twitch.tv, and the 350 Bush St address on the listing. Rationale: publisher identity is the cheapest, fastest authenticity check you have, and impostors fail it immediately.
4. Check the version and its date together. A current phone build in mid-to-late 2026 is in the 30.x range (30.8.0 landed 17 August 2026). If a 'newest' listing offers something far older with a stale date, walk away. Rationale: version-and-date together catch both impostors and abandoned mirrors that a version number alone would not.
5. On mobile, install directly from the store. Tap install, let it complete, do not interrupt it. Rationale: an interrupted install leaves a partial package the OS may or may not clean up, which resurfaces later as a mystery crash.
6. On desktop, download the installer from twitch.tv/downloads and run it. Rationale: this is the sanctioned path recharge.com's 2026 guide points to, and it sidesteps the stale Microsoft Store build entirely.
7. (Sideload only) Download the APK from a reputable mirror and note the size. Legitimate recent builds have run roughly 83 to 103 MB (83.12 MB for 29.7.1, 93.4 MB for 29.2.2, 96.61 MB for 28.4.1 BETA, 103.37 MB for 27.9.1). A 12 MB 'Twitch' APK is not Twitch. Rationale: file size is a crude but effective sanity check against repackaged fakes.
8. (Sideload only) Verify the APK's signing certificate. Before installing anything you did not get from a store, check who signed it with Android's apksigner tool from the SDK build-tools. Rationale: the signature is cryptographic proof of origin — a genuine Twitch build carries Twitch's certificate; a re-signed fake carries someone else's.

   $ apksigner verify --print-certs twitch-30.8.0.apk
   
   Signer #1 certificate DN: CN=Twitch Interactive, O=Twitch Interactive
   Signer #1 certificate SHA-256 digest: <compare to a known-good build>
   Signer #1 certificate SHA-1 digest:   <compare to a known-good build>
   
   # Cross-check the file hash against the mirror's published checksum:
   $ sha256sum twitch-30.8.0.apk
   a1b2c3d4e5f6...  twitch-30.8.0.apk

   The certificate DN should name Twitch Interactive. If it names anything else, delete the file and stop.
9. (Sideload only) Install the verified APK. Enable install-from-this-source for your browser or file manager only for the duration, then disable it again. Rationale: leaving unknown-sources on globally is how the next dodgy APK gets in without asking.
10. Launch the app and let first-run setup finish. Rationale: the first launch fetches configuration and may pull a delta update; killing it early is a common cause of a blank or looping start screen.
11. Sign in — and use the app's own login, never a third-party credential box. Rationale: your Twitch password belongs in Twitch's login flow and nowhere else.
12. Enable two-factor authentication. Settings, Security, enable 2FA. Rationale: a download workflow often involves pasting session tokens into tools; 2FA is your backstop if a token ever leaks.
13. Set your quality and data preferences. Cap mobile playback quality if you are on a metered connection. Rationale: Twitch will happily stream 1080p60 over cellular and evaporate a data plan in an afternoon.
14. Confirm the installed version. On Android, Settings, Apps, Twitch, read the version in App Info; on Windows, query it directly.

    PS> Get-AppxPackage *Twitch* | Select-Object Name, Version
    
    Name     Version
    ----     -------
    Twitch   <installed build>
    
    # For the standalone desktop installer, use the About panel:
    # Twitch menu -> About Twitch -> version string.

    Rationale: confirming the build closes the loop. You now know exactly what you installed, which is the first question any troubleshooting session will ask.

When Sideloading Is the Only Option

Steps 7 through 9 exist for exactly one situation: a device that genuinely cannot reach its own app store, such as an Android TV box cut off from Google's services. In every other case, skip them — sideloading trades away automatic updates and store-level malware screening for control you do not actually need. When you do sideload, the signature check in Step 8 is not optional garnish; it is the entire safety mechanism. An APK that fails to name Twitch Interactive in its certificate has been tampered with, full stop, and the fact that it displays a purple logo means nothing.

Confirming and Locking It Down

The install is not done when the app opens; it is done when you have confirmed the version (Step 14), enabled 2FA (Step 12), and turned unknown-sources back off (Step 9). Those three together are the difference between an app you installed and an app you can account for. If you ever have to file a support ticket or debug a crash, the first thing anyone competent will ask is which build you are on — and now you will know.

Downloading VODs, Clips, and Highlights

Now the other job. Three routes, in ascending order of power and descending order of convenience: a browser extension, a command-line tool, and a desktop GUI. Pick by temperament. If you want the full step-by-step for a single VOD, we keep a dedicated walkthrough in our any-VOD-in-12-steps guide; what follows is the comparative version that tells you which tool to reach for and why.

The Browser Extension Route

The lowest-friction option is a browser extension that adds a download control to Twitch's own pages. The Twitch VOD Downloader extension on the Chrome Web Store is a representative example: as of version 3.26, updated 21 February 2026, its description states it can download sections of a VOD — meaning you can grab a fifteen-minute stretch of a four-hour stream without pulling the whole thing — and that it now also supports stories, highlights, and clips. That section-download feature is the selling point. Nobody wants the entire broadcast when they need one boss fight.

The trade-off with any extension is trust and longevity. Extensions break when Twitch changes its player, they can change hands, and they run with access to the pages you visit. Install from the official Chrome Web Store listing, read the current reviews rather than the launch-day ones, check the update date (a February 2026 update on a tool like this is a good sign it is being maintained), and treat any extension that suddenly demands sweeping new permissions with the suspicion it has earned.

The Command-Line Route: yt-dlp

For power and scriptability, nothing beats yt-dlp, the actively maintained fork of youtube-dl that handles Twitch VODs, clips, and highlights. It is a single command, it resumes interrupted downloads, and it slots straight into the archiving scripts we build at the end of this guide.

# Download a full past broadcast at best available quality:
$ yt-dlp https://www.twitch.tv/videos/1234567890

# List available formats first, then pick one:
$ yt-dlp -F https://www.twitch.tv/videos/1234567890
$ yt-dlp -f 720p60 https://www.twitch.tv/videos/1234567890

# Download only a slice (e.g. from 1h02m to 1h18m):
$ yt-dlp --download-sections "*1:02:00-1:18:00" \
    https://www.twitch.tv/videos/1234567890

# A clip:
$ yt-dlp https://clips.twitch.tv/SomeCleverClipSlug

A healthy run prints progress like this:

[twitch:vod] 1234567890: Downloading storyboard metadata
[twitch:vod] 1234567890: Downloading m3u8 information
[info] 1234567890: Downloading 1 format(s): 1080p60
[hlsnative] Total fragments: 842
[download]  38.2% of ~5.41GiB at 22.10MiB/s ETA 02:31

The --download-sections flag is the yt-dlp equivalent of the extension's section feature, and it is why the command line wins for anyone archiving regularly: you can express exactly the slice you want, feed it a list of URLs, and walk away while it works.

The GUI Route: TwitchDownloader

If a terminal makes you itch, TwitchDownloader is a purpose-built desktop application (with a CLI companion, TwitchDownloaderCLI) for VODs, clips, and — its standout feature — chat. It renders chat replay into a video overlay or a standalone file, which for preservation is enormous: a speedrun VOD without its chat reactions is only half the artifact.

# TwitchDownloaderCLI: download a VOD
$ TwitchDownloaderCLI videodownload --id 1234567890 \
    -o run.mp4 -q 1080p60

# Download the chat as JSON (for later rendering or analysis)
$ TwitchDownloaderCLI chatdownload --id 1234567890 \
    -o chat.json

# Render that chat JSON into a video overlay
$ TwitchDownloaderCLI chatrender -i chat.json \
    -o chat.mp4 -h 1080 -w 340

Between the three, the rule of thumb is simple: extension for a one-off grab, yt-dlp for anything you will do more than twice, TwitchDownloader when the chat matters as much as the video.

Common Pitfalls and How to Undo Them

The mistakes that cost an afternoon, not the exotic ones — grouped by where in the process they bite.

Install-Time Pitfalls

Installing the wrong build for the device. The mistake: sideloading the 30.x phone APK onto a Fire TV, or grabbing the 13.x TV build for a phone. The app installs, then behaves bizarrely — no remote navigation on the phone build, touch targets you cannot reach on the TV build. The fix: uninstall it and install the build whose version lineage matches the device (23.x for Fire tablets, 13.x for TV, 30.x for phones). The version number is the tell; check it before you install, not after.

Trusting a mirror because the logo looked right. The mistake: downloading an APK from an aggregator, seeing the purple glyph, and installing without checking the signature. The fix: there is no fix after the fact except a clean uninstall and a malware scan. The prevention is Step 8 — verify the signing certificate names Twitch Interactive and the file size lands in the sane 83 to 103 MB range. A 'Twitch' APK that is 12 MB or 300 MB is lying to you.

Archiving Pitfalls

Downloading a VOD that has already expired. The mistake: bookmarking a past broadcast to archive 'later', then finding it gone when the retention window closes. The fix: you cannot recover a deleted VOD; Twitch does not keep it. The prevention is to treat the retention window as a hard deadline and pull anything you care about immediately. If the creator saved it as a highlight, that copy persists — but the raw past broadcast does not.

Expecting a local tool to un-mute a muted segment. The mistake: downloading a VOD and finding stretches silent, then blaming the downloader. The fix: nothing local fixes it. Twitch mutes audio at the source when it detects a copyright-claimed track, and that mute is baked into the VOD itself before you ever touch it. No downloader can restore audio that was never in the file.

Security and Maintenance Pitfalls

Pasting your password into a downloader. The mistake: a slick 'Twitch downloader' asks for your username and password to reach sub-only VODs, and you type them in. The fix: change your Twitch password immediately, from Twitch's real site, and enable 2FA if you had not. Legitimate tools use your browser session or OAuth. A raw-password prompt is phishing; there is no benign version of it.

Letting the app's cache balloon. The mistake: months of use leave the Twitch app's cache bloated, and playback starts stuttering or the app refuses to load a stream. The fix: clear the app's cache (App Info, Storage, Clear Cache on Android; a full reinstall on desktop) rather than reinstalling blindly. The principle is the same one we apply to a misbehaving console — when in doubt, clear the cache before you nuke the install, exactly as in our PS5 cache-clear walkthrough. Clearing cache keeps your login; clearing data does not.

Troubleshooting Table

The symptoms you are most likely to hit, split by which half of the job they belong to. Work top to bottom; the common cases are first.

Install and Playback Symptoms

Download and Archiving Symptoms

Escalating Beyond the Table

If none of the above matches, the fault is usually one layer down: a network filter blocking Twitch's CDN, a corporate proxy mangling the HLS stream, or a browser profile whose cookies have gone stale. Test the same download from a clean browser profile and an unfiltered connection before assuming the tool is broken. Nine times in ten, the tool is fine and the environment is the problem.

Advanced Tips: Pinning, Batching, Chat

Once the basics work, three refinements separate a casual grab from a real archive.

Pinning a Known-Good Version

The mobile app updates constantly — three-day gaps between builds are normal, as the 30.7.2-to-30.8.0 jump across 14 to 17 August 2026 showed. Usually that is fine. Occasionally a build regresses something you rely on and you want to hold position. On Android you can disable auto-update for Twitch specifically (Play Store, Twitch listing, menu, untick 'Enable auto update') and, if you must roll back, sideload a verified earlier APK — the mirrors keep the history, which is exactly what makes 29.7.1 (2 June 2026) or 27.9.1 (27 January 2026) retrievable. Pin deliberately, and un-pin once the regression is fixed; running a frozen social app forever is a security liability, not a strategy.

Batch-Archiving a Channel's VODs

The reason to graduate from the extension to yt-dlp is batching. Feed it a text file of VOD URLs and it works through them unattended:

# urls.txt holds one VOD or clip URL per line
$ yt-dlp -a urls.txt -o "%(uploader)s/%(upload_date)s - %(title)s.%(ext)s"

# Restrict to a recent count when pulling a whole channel:
$ yt-dlp --playlist-end 20 \
    https://www.twitch.tv/somechannel/videos

The -o template sorts downloads into per-uploader folders named by date and title, which is the difference between an archive and a pile. Do this only for content you have a right to keep, and do not hammer the service — a sane pull is a courteous pull, and a courteous pull does not get your IP rate-limited.

Chat, Context, and Your Own Footage

For preservation, the chat is not garnish; it is the crowd reaction, the timestamps of the big moment, the context that makes footage legible years later. TwitchDownloader's chat export (shown earlier) writes a JSON transcript you can render into an overlay or simply keep as text. If you are archiving a competitive run or a milestone stream, pull the chat alongside the video and store them together — future-anyone will want the reaction track.

And if the footage you want is your own gameplay, you do not need to archive it off Twitch at all. Capture it at the source at full quality, then decide what to stream. For console play that is a capture-card or remote-play workflow, which we cover in the PS Remote Play 1080p guide. Source capture beats re-downloading a re-encoded VOD every time; the VOD is a lossy copy of what you already had in hand.

The Complete Working Configuration

Everything above, distilled into a setup you can drop in and run. This is the archiving rig: a yt-dlp config that sets sane defaults, and a small script that turns 'download this channel's recent VODs, with chat, sorted into folders' into one command.

The yt-dlp Config File

Place this at ~/.config/yt-dlp/config (Linux/macOS) or %APPDATA%\yt-dlp\config.txt (Windows). yt-dlp reads it automatically, so every invocation inherits these defaults.

# ~/.config/yt-dlp/config
# Sane defaults for archiving Twitch VODs and clips.

# Output layout: one folder per uploader, files named by date + title
-o %(uploader)s/%(upload_date)s - %(title)s [%(id)s].%(ext)s

# Prefer 1080p source, fall back gracefully
-f "bestvideo[height<=1080]+bestaudio/best"

# Resume partial downloads, never overwrite a finished file
--continue
--no-overwrites

# Pull authenticated content using your logged-in browser session
--cookies-from-browser firefox

# Be a good citizen: cap concurrent fragments, add a retry budget
--concurrent-fragments 4
--retries 10
--fragment-retries 10

# Write a metadata sidecar and embed the thumbnail
--write-info-json
--embed-thumbnail

The One-Command Archive Script

A small POSIX shell script that ties the pieces together: it collects the most recent VOD IDs from a channel and, for each one, downloads the video (via the config above) and then pulls the matching chat with TwitchDownloaderCLI. Adjust the count and paths to taste.

#!/usr/bin/env sh
# archive-channel.sh - pull recent VODs + chat for one channel
# Usage: ./archive-channel.sh somechannel 5

set -eu

CHANNEL="$1"          # Twitch channel login name
COUNT="${2:-5}"       # how many recent VODs (default 5)
OUTDIR="./archive/$CHANNEL"

mkdir -p "$OUTDIR"
cd "$OUTDIR"

echo "Archiving the $COUNT most recent VODs for $CHANNEL ..."

# 1) Collect the VOD IDs for the channel's most recent broadcasts
IDS=$(yt-dlp --playlist-end "$COUNT" --print id \
      "https://www.twitch.tv/$CHANNEL/videos")

# 2) For each ID: download the video, then pull the chat as JSON
for id in $IDS; do
    echo "  VOD $id: video ..."
    yt-dlp "https://www.twitch.tv/videos/$id"
    echo "  VOD $id: chat ..."
    TwitchDownloaderCLI chatdownload --id "$id" -o "chat-$id.json"
done

echo "Done. Archive is in $OUTDIR"

Running the Whole Rig

Run it with sh archive-channel.sh somechannel 5 and it deposits five recent VODs, their metadata sidecars, their embedded thumbnails, and their chat transcripts into ./archive/somechannel/, each sorted into a named folder. That is the entire setup: a verified app on the front end, a config-driven archiver on the back end, and nothing paying rent that you did not install on purpose. Keep the config and the script in version control, and your archiving rig survives a machine rebuild in minutes.

The Verdict

Two jobs, two verdicts. Here is the short version to tape above the desk.

For Watching

Get the app from the first-party source for your exact device — Google Play or the App Store for phones, twitch.tv/downloads for desktop, the device's own store for TV and Fire — and verify the publisher is Twitch Interactive, Inc. before you install. The version lineage tells you whether a build belongs on your device (30.x phone, 23.x Fire tablet, 13.x TV), and a current 2026 phone build sits in the 30.x range. Skip the Microsoft Store; it lags. Skip Twitch Studio; it has been dead since May 2024.

For Keeping

Match the tool to the job: the Twitch VOD Downloader extension (v3.26, updated February 2026) for a quick section grab, yt-dlp for anything scriptable or repeated, TwitchDownloader when the chat is part of the artifact. Verify signatures on anything sideloaded, never type your password into a downloader, and treat the retention window as the hard deadline it is.

The Bottom Line

'Twitch download' was never one task. It is a client install with a verification checklist and an archiving workflow with a legal conscience, wearing the same three words. Do the first job right and the app is boring and reliable, which is exactly what you want from an app. Do the second job right and the footage that matters outlives the platform's timer, which is the entire point. The stream is ephemeral by design. Your copy does not have to be.