Invidious vs Stash
| Tagline | Privacy-respecting alternative front-end for YouTube | Self-hosted adult media library organizer with auto-tagging and metadata scraping |
| Category | Media Servers & Streaming | Media Servers & Streaming |
| Replaces | Netflix | Plex |
| GitHub stars | 24k | 13k |
| Language | Docker | Docker |
| License | AGPL-3.0 | AGPL-3.0 |
| Self-host difficulty | 3/5 Moderate | 2/5 Easy |
| Deploy options | Docker Docker Compose Manual | Docker Docker Compose Manual |
| Managed hosting | ||
| Last updated | 4 days ago | 5 days ago |
| View repo | View repo |
Where each falls short
The honest trade-offs — what you give up with each, versus the proprietary tools they replace.
Invidious
- Relies entirely on YouTube's infrastructure; Google can and does throttle or break the API at any time.
- No support for YouTube Shorts, YouTube Music, or YouTube Premium content.
- Comment loading and search quality degrade as Google tightens API restrictions.
- No upload capability; purely a viewing front-end.
Stash
- Highly niche scope; not suitable for general-purpose media libraries.
- Mobile apps are community-made and not officially supported.
- Metadata scraping depends on community-maintained StashDB, which can have gaps.
- No hardware transcoding support; playback quality is limited by server CPU.
Bottom line
Choose Stash if you want the lower-effort setup; choose Invidious for the larger community and ecosystem. Invidious has seen more recent development. Open each guide below for deploy steps and the full feature gap.
Stash
Self-hosted adult media library organizer with auto-tagging and metadata scraping