Clipious

An honest look at the privacy-first YouTube frontend for Android — and the elephant in the room.

TL;DR

• What it is: A Flutter-based Android app that connects to Invidious instances — privacy-respecting YouTube frontends — and wraps them in a native mobile interface [README].
• Who it’s for: Privacy-conscious Android users who want YouTube content without Google’s tracking, ads, or surveillance, and are comfortable pointing an app at a third-party server.
• Critical caveat: The repository was archived by its author on January 29, 2026 and is now read-only. No new features, no bug fixes, no security patches [GitHub].
• Cost: Free. The app is AGPL-3.0 licensed. You use a public Invidious instance (free) or host your own ($5–10/mo VPS).
• Key strength: The most complete native Android UI for Invidious — SponsorBlock, DeArrow, Android TV support, background playback, download, filtering, and Return YouTube Dislikes baked in [README].
• Key weakness: The project is dead. It had 1,270 stars and 48 forks — not a massive community to carry it forward without the original author.

---

What is Clipious

Clipious is an Android application written in Flutter that acts as a client for Invidious, an open-source alternative YouTube frontend that strips Google’s tracking, ads, and recommendation algorithms from video playback [README][5].

The architecture matters here because it shapes everything about how the app works. Clipious itself doesn’t fetch YouTube videos — it connects to an Invidious instance, which proxies the YouTube content and exposes an API. You choose either a public Invidious instance (a volunteer-run server anyone can use) or one you self-host. Clipious is the UI layer on top [README].

This approach has a real privacy upside: your viewing habits never touch Google’s servers. The Invidious instance sees your requests, but you can pick an instance run by a privacy-focused operator, or eliminate that trust dependency entirely by self-hosting [5][2]. Morgan, a privacy-focused self-hoster, describes this trade-off plainly while cataloguing their Big Tech exit: “There are alternatives frontends like Invidious, SkyTube (Android), Clipious (an Android client for Invidious instances)” [2].

The app was built by Paul Fauchon and reached 1,270 GitHub stars before the author archived it in January 2026. It’s built on Flutter, which explains why it covers phone, tablet, and Android TV with the same codebase [README][GitHub].

---

Why People Choose It

The reviews available barely mention Clipious by name — most coverage is about the broader “escape YouTube” movement, with Clipious appearing as one item in a list of alternatives. That sparseness is itself a signal: Clipious never had the mainstream profile of NewPipe or the developer attention of LibreTube. What people chose it for was specific.

The Invidious-native client gap. There are multiple ways to watch YouTube without Google — browser-based Invidious, NewPipe (which scrapes YouTube directly), SkyTube, and others. But if you specifically want to use an Invidious instance (either because your self-hosted infrastructure already runs one, or because you want Invidious’s server-side subscription syncing), Clipious is the cleaner native client compared to using the Invidious web interface in a mobile browser [README][2].

Feature completeness. Most privacy YouTube clients make you choose between privacy and features. Clipious didn’t: SponsorBlock, DeArrow (clickbait title/thumbnail removal), Return YouTube Dislikes, background audio playback, video download, and video filtering were all in [README]. The video filtering feature was specifically something the broader Invidious ecosystem lacked — one self-hoster notes that Invidious itself “does not yet support filtering of videos” [2], which is part of why a dedicated app client matters for granular control.

Android TV. The dedicated TV interface is a differentiator. Most open-source YouTube clients are phone-first and TV support is an afterthought. Clipious shipped a distinct TV UI [README].

Privacy philosophy alignment. The audience for Clipious is the person actively de-Googling their life. Morgan’s self-hosting blog [1][2] describes replacing YouTube with Invidious frontends as part of a systematic exit from GAFAM services. For that user, Clipious wasn’t just an app — it was the final piece of replacing Google’s Android YouTube client with something that doesn’t phone home.

---

Features

Based on the README and project documentation:

Video playback:

• Standard playback with progress tracking and view history [README]
• Background playback (audio continues when screen is off) [README]
• Audio-only mode [README]
• Live stream support [README]
• Video and audio download [README]

Privacy tools:

• SponsorBlock integration (skips sponsored segments, intros, outros) [README]
• DeArrow (replaces AI-baited titles and thumbnails with community-sourced alternatives) [README]
• Return YouTube Dislikes (restores the dislike count YouTube removed) [README]
• Video filtering (hide videos matching criteria — something Invidious itself doesn’t offer natively) [README][2]

Account and library:

• Subscription management (follows channels via Invidious account sync) [README]
• Playlists [README]

Server flexibility:

• Use your own self-hosted Invidious instance or any public instance [README]
• Multiple instance support

Platforms:

• Phone, tablet, and Android TV with dedicated UI per form factor [README]

Distribution:

• Available on F-Droid, IzzyOnDroid, and Accrescent [README]
• Obtainium-compatible for automatic updates [README]
• Direct APK download from GitHub releases [README]

---

Pricing: SaaS vs Self-Hosted Math

This one is simple because Clipious itself is free software. The cost question is really about the Invidious layer underneath.

Clipious app: $0. AGPL-3.0, no ads, no subscription, no in-app purchases [README].

Invidious instance (the backend Clipious talks to):

• Public instance: $0. There are dozens of public Invidious instances run by volunteers. You pick one from the Invidious instance list and point Clipious at it. The downside: you’re trusting whoever runs that instance, and public instances go down, get rate-limited, or disappear when the volunteer stops paying.
• Self-hosted Invidious: $5–10/month on a basic VPS (Hetzner, Contabo, DigitalOcean). You control it, it’s always up, and only your household’s traffic goes through it.

YouTube Premium for comparison: $13.99/month (US, individual). Includes ad-free viewing, background playback, YouTube Music. Requires a Google account and you’re inside Google’s data model.

Concrete math: A household running self-hosted Invidious + Clipious for 12 months = $60–120/year. YouTube Premium = $167.88/year per person, more for a family plan. The gap grows fast if multiple people share the self-hosted instance.

The honest asterisk: YouTube Premium’s content actually works reliably. Invidious instances have periodic reliability issues when Google changes the YouTube API or rate-limits instances. Data not available on uptime statistics for public instances, but it’s a real operational consideration.

---

Deployment Reality Check

Installing Clipious itself is a two-minute download from F-Droid or the GitHub releases page [README]. That part is trivial.

The real deployment question is Invidious. If you use a public instance, setup for Clipious is: install app → open settings → pick an instance → done. If you self-host Invidious:

What you need:

• A Linux VPS (2GB RAM minimum)
• Docker (Invidious distributes via Docker Compose)
• PostgreSQL (bundled in Invidious’s Docker Compose or external)
• A domain and reverse proxy for HTTPS
• Invidious configuration (notably, a YouTube API key is no longer required for basic use, but some features need it)

What can go sideways:

• Invidious’s relationship with YouTube is adversarial. Google periodically blocks or rate-limits Invidious instances, which breaks playback until the Invidious project patches around it. A self-hosted instance means you’re updating it yourself when this happens.
• Public instances have variable reliability. The best practice (recommended by the Clipious README) is to use Obtainium to keep the app updated [README], but you can’t automate keeping a public instance’s uptime stable.
• The project being archived means you won’t get fixes if a future Android version or Invidious API change breaks something in Clipious [GitHub].

For a non-technical user: this setup requires either a willingness to learn Docker basics or paying someone to set it up. Unlike self-hosting a web app, a broken Invidious instance means broken video playback, which has a low tolerance threshold for daily use.

---

Pros and Cons

Pros

• Actually no-tracking. Your viewing habits don’t reach Google. Invidious proxies the content, Clipious never calls home to any analytics service [README][5].
• No ads. The Invidious layer strips YouTube ads before they reach the client [5][README].
• Comprehensive feature set for a privacy client. SponsorBlock, DeArrow, Return YouTube Dislikes, video filtering, background playback, download — most privacy clients make you sacrifice features for privacy. Clipious didn’t [README].
• Android TV support. Dedicated TV UI is rare in this category [README].
• AGPL-3.0 license. You can read every line of code, fork it, verify it’s not doing anything unexpected [README].
• Multiple distribution channels. F-Droid, Accrescent, Obtainium, direct APK — maximum flexibility for users who don’t use the Play Store [README].
• Invidious account sync. Subscriptions persist via your Invidious account, not locally only [README].

Cons

• The project is archived. Development stopped January 29, 2026. This is disqualifying for anything you plan to rely on long-term. Android updates, Invidious API changes, or YouTube changes could silently break the app with no fix coming [GitHub].
• Depends on Invidious, which has its own fragility. Invidious instances break when Google pushes API changes. You’re adding a layer of operational complexity below the app [2][5].
• Limited content filtering for kids. One self-hoster specifically calls out that Invidious-based clients aren’t safe for unsupervised children’s use because content filtering is incomplete [2].
• Small community. 1,270 stars and 48 forks. Not enough to sustain active maintenance after the original author stepped back [GitHub].
• Android only. The Flutter codebase has platform stubs for iOS, Linux, macOS, Windows, and web (visible in the repo directory listing), but no public iOS release exists — App Store rules around third-party YouTube clients make that difficult. The practical deployment is Android [README][GitHub].
• Third-party reviews are sparse. No dedicated in-depth reviews found; coverage consists of brief mentions in broader self-hosting context posts [1][2]. Hard to benchmark against alternatives from community feedback.

---

Who Should Use This / Who Shouldn’t

Use Clipious if:

• You already run a self-hosted Invidious instance and want a native Android UI for it.
• You’re committed to de-Googling and need YouTube content without the tracking — and you’re willing to accept occasional reliability hiccups.
• You’re technically comfortable enough to handle Invidious maintenance or pick a stable public instance.
• You’re installing the last known-good version and aren’t worried about long-term updates (hobbyist use, single device, low stakes).

Don’t use Clipious if:

• You need reliable software with active security patches. The project is abandoned.
• You want a YouTube replacement for a household with children. Invidious-based clients lack the content filtering parents need [2].
• You’re evaluating this for a business or team use case where uptime matters.
• You’re a non-technical user expecting a set-and-forget install.

Consider alternatives instead if:

• You want an active, maintained open-source YouTube client on Android — see the section below.
• You need cross-platform (iOS + Android) privacy video access.

---

Alternatives Worth Considering

NewPipe — The most popular open-source YouTube client for Android. Scrapes YouTube directly (no Invidious dependency), supports background playback, download, subscriptions stored locally, no account required. Actively maintained, much larger community. Doesn’t require any server infrastructure. If you’re not specifically tied to Invidious, NewPipe is the more pragmatic choice.

Tubular — NewPipe fork with SponsorBlock baked in. Essentially NewPipe + the ad-segment skipping Clipious offered. Good default for most users in this category.

LibreTube — Also Invidious-based (like Clipious), actively maintained, similar feature set. If you specifically want an Invidious-backed Android client with an active developer, LibreTube is the current default recommendation as of early 2026.

SkyTube — Mentioned alongside Clipious in the same self-hosting context [1][2]. Scrapes YouTube directly. Has channel filtering, which is a plus for households with children [2].

Grayjay — Multi-platform aggregator from FUTO that supports YouTube, Twitch, Nebula, and others from a single app. Paid ($10 one-time) but not a subscription. More polished UX, more active development.

Invidious (web) — If you’re self-hosting Invidious anyway, the web interface on mobile is usable. Not ideal UX, but zero additional app maintenance.

---

Bottom line

Clipious was a well-built, feature-complete Android client for Invidious that solved a real problem: giving privacy-conscious Android users a native app experience on top of the privacy infrastructure they were already running. The feature set — SponsorBlock, DeArrow, Android TV support, video filtering, background playback — was genuinely good. The problem is straightforward: the project is archived. As of January 2026, no new code is being merged. If Android 16 breaks something, no fix is coming. If Invidious changes its API in a way Clipious doesn’t handle, no fix is coming.

For anyone exploring this in 2026: look at LibreTube if you want Invidious-backed Android, or NewPipe/Tubular if you just want a clean YouTube frontend without the Invidious dependency. Clipious was a good project that ran its course.

---

Sources

1. Morgan — “privacy” tag archive — Personal blog covering Big Tech exit and self-hosting tools, includes mention of YouTube alternatives. https://morgan.zoemp.be/tag/privacy/
2. Morgan — “Charting my journey away from Big Tech: Embracing Privacy and Self Hosting Solutions” — Self-hosting journey post with direct mention of Clipious as Invidious Android client. https://morgan.zoemp.be/selfhosting/
3. ReviewsApp.org — Invidious / AlternativeTo listing (via [5]) — Community reviews and feature listing for Invidious, the backend Clipious depends on. https://alternativeto.net/software/invidious/about/
4. GitHub — lamarios/clipious repository — Primary source: README, feature list, license, archive notice, star/fork counts. https://github.com/lamarios/clipious
5. AlternativeTo — Invidious listing — Community reviews of Invidious covering privacy, ad-blocking, and use cases that underpin the Clipious value proposition. https://alternativeto.net/software/invidious/about/