Invidious vs Tube Archivist: Which to Self-Host?

Quick Verdict

These tools solve different problems. Invidious is a private YouTube frontend — you watch videos streamed from YouTube without ads or tracking. Tube Archivist downloads and archives videos to your local storage for permanent offline access. Most serious self-hosters run both: Invidious for daily YouTube browsing and Tube Archivist for preserving content they want to keep.

Overview

Invidious is a Crystal-based YouTube frontend that proxies requests to YouTube, stripping ads, tracking scripts, and JavaScript requirements. It provides subscriptions, playlists, and search through a clean web interface — all without a Google account. Videos stream from YouTube through your server.

Tube Archivist is a Python/Django-based YouTube media manager that downloads videos using yt-dlp and indexes them with Elasticsearch for full-text search. It manages channel subscriptions, automated downloads, and provides a watching interface for your local video library.

AspectInvidiousTube Archivist
Primary functionYouTube proxy/frontendYouTube video archiver
Video storageNone (streams from YouTube)Local (your disk)
LanguageCrystalPython (Django)
Latest versionv2.20260207.0v0.5.9
LicenseAGPL-3.0GPL-3.0
First release20172021

Feature Comparison

FeatureInvidiousTube Archivist
Watch YouTube videosYes (streamed)Yes (downloaded locally)
Ad-free viewingYesYes
No Google trackingYesYes
Channel subscriptionsYesYes
PlaylistsYesYes
SearchYouTube search (proxied)Full-text across downloaded content
Subtitle supportYouTube-servedDownloaded and searchable
Video quality optionsAll YouTube qualitiesConfigurable per-download
Offline viewingNo (requires internet)Yes (videos stored locally)
Automated downloadsN/AYes (scheduled per channel)
Mobile appNone (responsive web)None (responsive web)
Multi-userYes (accounts with preferences)Yes (admin + viewers)
APIYouTube-compatible REST APICustom REST API
CommentsYouTube comments (proxied)Not available
Live streamsYesNo
Age-restricted contentVia companion serviceVia yt-dlp cookies

Installation Complexity

Invidious requires cloning the repository (for SQL initialization files), then running three Docker services: the main app, the companion service for video retrieval, and PostgreSQL. Configuration is done via YAML embedded in an environment variable, which is unusual but well-documented. Two different secret keys must be generated and matched across services.

Tube Archivist is simpler to deploy — no repo clone needed, just a docker-compose.yml with three services: the app, Elasticsearch, and Redis. The catch is Elasticsearch requires a kernel parameter change (vm.max_map_count=262144) that may not be allowed on all hosting platforms (particularly LXC containers without configuration).

Setup AspectInvidiousTube Archivist
Repo clone requiredYes (SQL init files)No
Services3 (app + companion + PostgreSQL)3 (app + Elasticsearch + Redis)
Config formatYAML in env varStandard env vars
Kernel changesNonevm.max_map_count required
First-start time~30 seconds2-3 minutes (ES init)
Secret keys to generate2 (must match across services)1 (ES password, shared)

Performance and Resource Usage

ResourceInvidiousTube Archivist
RAM (idle)~200 MB~2 GB (Elasticsearch dominates)
RAM (active)500 MB+3-4 GB
CPU usageLow (proxying only)Medium (downloading + indexing)
Disk for application~20 GB~20 GB + video storage
Disk for contentNone (streamed)Depends on library (easily 100+ GB)
BandwidthStreams from YouTube on demandDownloads once, serves locally
Known issuesMemory creep (periodic restart recommended)ES disk watermark at 95% usage

Invidious is significantly lighter — it’s essentially a web proxy. Tube Archivist’s Elasticsearch service alone consumes 1 GB of heap memory. If you’re resource-constrained (Raspberry Pi, small VPS), Invidious is the better choice.

Community and Support

AspectInvidiousTube Archivist
GitHub stars20,000+6,000+
Active developmentActive (with periods of uncertainty)Active
DocumentationGood (docs.invidious.io)Good (GitHub wiki)
CommunityMatrix, GitHubDiscord, GitHub
Update frequencyRegularRegular (monthly releases)
Public instancesMany availableN/A (local only)

Invidious has a larger community and longer history, but it periodically faces existential challenges when YouTube changes break video playback. The companion service has largely stabilized this, but breakages still occur. Tube Archivist’s reliance on yt-dlp means it benefits from that project’s large contributor base for YouTube compatibility fixes.

Use Cases

Choose Invidious If…

  • You want ad-free, tracking-free YouTube browsing as your daily driver
  • You don’t need to keep videos permanently
  • You want a lightweight deployment (200 MB RAM vs 2+ GB)
  • You run a small VPS or Raspberry Pi
  • You want to host a YouTube frontend for your household
  • You watch live streams
  • You want YouTube comments without Google tracking

Choose Tube Archivist If…

  • You want to permanently archive YouTube content (channels, playlists, individual videos)
  • You’re concerned about videos being deleted, copyright-claimed, or channels disappearing
  • You want full-text search across video subtitles and descriptions
  • You have substantial storage capacity (NAS, large drives)
  • You want scheduled automatic downloads of new content from subscribed channels
  • You want to build a personal video library independent of YouTube’s availability

Run Both If…

  • You want Invidious for daily browsing and Tube Archivist for archiving specific channels
  • You want the best of both: privacy-respecting streaming + permanent local copies of important content

Final Verdict

These are complementary tools, not competitors. Invidious replaces the YouTube website for daily viewing — it’s lightweight, fast, and strips the surveillance. Tube Archivist replaces YouTube as a content platform — videos live on your hardware, searchable and permanent.

If you can only pick one: Invidious for most people. Ad-free, private YouTube browsing solves the everyday problem. Add Tube Archivist when you start worrying about video preservation or want offline access to a curated library.

Comments