Invidious

Keep subscriptions, notifications, and history outside a Google account

Invidious can maintain channel subscriptions and notifications independently from Google accounts. Its viewing experience includes a customizable homepage, light and dark themes, audio-only playback, and background play on mobile. Subscription and watch-history imports from YouTube and NewPipe, plus subscription exports to NewPipe and FreeTube, make it possible to move between clients instead of treating one interface as the permanent owner of the user's library.

Sources: [1]

Use it as an API and embedding layer as well as an alternate website

The project lists a Developer API and embedded-video support among its technical features. Since it does not use the official YouTube APIs, Invidious can be deployed not only as a web UI for people but also as an intermediate service for other front-ends and tools that need video or channel data. Users can start with a public instance or run their own instance when they want to control configuration and availability.

Sources: [1]

For users reducing ads, tracking, and Google-account dependency

Invidious fits people who want a lighter viewing interface without advertising and tracking, users who want subscription lists without signing into Google, and operators who want to host their own viewing layer. The Developer API also makes it relevant to developers building privacy-focused video clients or internal viewers. A practical adoption path is to try a public instance first, then self-host when control over uptime, configuration, and data becomes more important.

Sources: [1]

Upstream changes and self-hosted stream retrieval require ongoing operations

Invidious retrieves YouTube information without the official API, so changes in YouTube behavior can require corresponding Invidious updates. The CHANGELOG shows ongoing work to stabilize video retrieval, and the configuration supports Invidious Companion as an external program for loading video streams from YouTube servers. Depending on the environment, operators may need to plan for Companion, proxies, and reverse-proxy routing in addition to the main application.

A PostgreSQL connection is mandatory for self-hosting, and the docker-compose file checked into the repository is explicitly labeled for development rather than production. Production deployments therefore need to manage domain and HTTPS settings, secrets, the database, and updates according to the official installation guidance. Public instances are operated by third parties, so availability, logging, and operating policy can differ between instances. Invidious itself is licensed under AGPLv3, and the project asks users to follow applicable laws and avoid inappropriate use.

Sources: [1][2][3][4][5]