Twitch's default VOD retention is 7 days — 14 if you're an Affiliate, up to 60 if you're a Partner. If your back catalog is only living on Twitch's servers, it's rented, not owned. We get asked a lot on support tickets how to set up a VPS for Twitch VOD backup storage that just runs quietly in the background and pulls everything down before it expires. Here's the setup we actually recommend, from the rack.
Why Your VODs Are Disappearing
Twitch's retention policy is a cost decision on their end, not a courtesy to you. By default, a VOD is gone in 7 days. Affiliates get 14, Partners get 60 — and once the window closes, there's no self-serve extension or bulk export tool for full VOD history. Clips technically stick around longer, but they're low-resolution derivatives, not a substitute for the source recording. If you've ever wanted to re-cut an old stream, pull a highlight reel for a sponsor deck, or just rewatch a good session from eight months ago, you've probably already hit this wall.
What an Archive Setup Actually Needs
A proper VOD archive isn't complicated, but it has three requirements that a laptop or a consumer NAS behind residential upload speeds struggles with:
- Storage that scales with your schedule. A single 6-hour 1080p60 stream can run 10-20GB depending on bitrate. Stream daily and you're archiving hundreds of gigabytes a month.
- Bandwidth that doesn't punish you for downloading your own content. Pulling VODs means sustained outbound transfer from Twitch to your server, then potentially serving that content again later.
- Uptime to run on a schedule. The pull job needs to fire reliably, every day, without you remembering to kick it off manually before the retention window closes.
A VPS with SSD storage and unmetered bandwidth solves all three without you having to babysit it.
Building a Self-Host Twitch VOD Archive Server
The actual mechanics are straightforward. Most streamers run this with yt-dlp or the Twitch-specific twitch-dl tool, both of which can pull full VODs (not just clips) at source quality. A typical setup on a self-host Twitch VOD archive server looks like this:
- A small script that queries the Twitch API (or scrapes your channel's VOD list) for new video IDs since the last run.
yt-dlportwitch-dldownloads each new VOD to local SSD storage, named and dated automatically.- A cron job runs the script daily — well inside even the shortest 7-day retention window, with margin for retries.
- Optional: a second step re-encodes or trims archived files for long-term storage efficiency, or syncs them to secondary storage.
Because this all runs server-side with root SSH access, you're not tying up your own streaming or gaming PC to babysit downloads — the VPS does it in the background whether you're online or not.
Sizing a VPS for Twitch VOD Backup Storage
We built our Streaming VPS line for exactly this kind of workload — it's the same box a lot of our customers already use to run OBS, RTMP ingest, and restreaming, so adding a VOD archive script alongside it is a natural fit rather than a separate server to manage.
| Tier | RAM / vCPU | SSD Storage | Price |
|---|---|---|---|
| Entry | 2GB / 1 vCPU | 20GB | EUR9.99/mo |
| Top tier | 32GB / 12 vCPU | 120GB | EUR139.99/mo |
Full range and intermediate tiers are on the Streaming VPS plan page. The largest plan carries 120GB of SSD, which at the 100-200GB a month of daily streaming estimated below holds a few weeks of back catalog, so plan to rotate older files to cold storage or an external drive on a schedule.
The Bandwidth Math Nobody Mentions
This is the part that catches people off guard on generic cloud providers: downloading VODs from Twitch counts as inbound transfer, but if you ever want to serve archived clips back out — to a website, a Discord bot, or a re-upload pipeline — that's outbound transfer, and plenty of providers meter it separately with overage fees. Our Streaming VPS plans are unmetered, with no per-VM bandwidth ceiling, so pulling VODs down and serving them back out later doesn't turn into a line item you have to watch.
GDPR-Compliant Storage for Streamer Content in Europe
If your VODs include chat overlays, donation alerts, or guest audio, you're storing more than just your own gameplay footage — you're storing community and third-party data too. Hosting that archive on infrastructure physically located in the EU, under EU data protection law, is a simpler compliance story than routing it through a US-based platform's terms of service. Our Streaming VPS runs in Bucharest, Sofia, Warsaw, Amsterdam, Frankfurt and Vienna, all inside the EU, as well as in Ashburn in the US; the six EU locations give European streamers GDPR compliant cloud storage for streamer content without having to think about cross-border data transfer rules for their own archive.
Beyond Twitch: One Box, Full Streaming Stack
Because the same VPS can also run OBS, Nginx-RTMP, MediaMTX, MistServer, Owncast or Restreamer, which you install yourself with full root, a VOD archive script isn't competing for a separate machine — it's one more cron job on infrastructure you're already running for RTMP, RTMPS, SRT, HLS, or LL-HLS output. If archiving is the only thing you need right now, our general-purpose hourly VPS line works fine too, billed by the hour with root SSH, if you'd rather size it independently of streaming workloads.
How Noded Can Help
We run our own network — own AS60982, SSD storage, unmetered bandwidth — so a VOD archive job doesn't have to compete with anyone else's noisy neighbor or hit a bandwidth cap partway through the month. If you want, we can walk you through sizing a Streaming VPS plan against your stream schedule and average VOD length before you commit to a tier. Deploys land in under a minute, so you can have the archive script running the same day you spin up the box.
FAQ
How long do Twitch VODs actually last before deletion?
By default, 7 days. Affiliates get 14 days, and Partners get up to 60, depending on their tier. Twitch doesn't guarantee these windows stay fixed, so treating the shortest one as your deadline is the safer assumption.
Can I download all my past VODs at once, or only new ones going forward?
Tools like yt-dlp and twitch-dl can pull any VOD still live on your channel, so you can do a one-time backfill of everything currently available, then switch to a daily cron job for new streams going forward. Anything already past its retention window is unrecoverable.
How much storage do I actually need for a VOD archive?
Rough rule of thumb: a 1080p60 stream runs roughly 1.5-3GB per hour depending on bitrate. Multiply by your average session length and streaming frequency per month, then add margin — 100-200GB covers a solid month of daily streaming for most setups.
Does archiving VODs affect my streaming setup or add latency?
No. The archive script runs independently of your live RTMP ingest and pulls completed VODs after the stream ends, so it has no effect on stream latency or encoding load.
Is a VPS overkill if I only stream occasionally?
Not really — the entry-tier Streaming VPS plan (2GB/1 vCPU/20GB SSD) is enough to run a lightweight cron-based archive script even for infrequent streamers, and you can resize up if your schedule picks up.