LibreTube: the Android YouTube client that avoids Google's app

What LibreTube actually replaces

LibreTube is an alternative frontend for YouTube, for Android. That phrasing matters: it is not a video host and not a downloader with a player bolted on. It is a client that renders YouTube content through a different path, and the README frames the motivation in privacy terms. YouTube's privacy policy, in the project's words, relies on using user data in unethical ways, and LibreTube aims to improve user privacy by being independent from Google and bypassing their data collection as much as possible. The stated behaviour is narrow: the app only sends the minimum amount of data necessary to ensure that the app works, for example loading the YouTube video you want to play without tracking your behaviour while you use the app.

The target user is someone on Android who already watches a lot of YouTube and wants the familiar shape of a client (subscriptions, playlists, history, downloads) without the official app. The feature list is conventional for that audience: no ads or tracking, subscriptions and subscription groups, user playlists, playlist bookmarks, watch and search history, downloads, and background playback. Two of those, subscription groups and playlist bookmarks, are organisational features you rarely see in this category, and they suggest the project is aimed at people with large subscription lists rather than casual viewers.

The project is written in Kotlin and licensed GPL-3.0. The repository layout is a standard Android Gradle project: app/, gradle/, build.gradle.kts, settings.gradle.kts, plus a baselineprofile/ directory for Android baseline profiles and fastlane/ for store metadata. Nothing exotic. If you have opened an Android project before, you can find your way around this one.

How Piped sits between the app and YouTube

The mechanism visible in the README is Piped. LibreTube lists user accounts via Piped as optional, and the search data around the project shows people asking what Piped is inside LibreTube. Piped is a separate project, linked from the README, that acts as the intermediary. The app is a client; the Piped instance is the server-side component that handles the requests to YouTube and returns data the app can render.

That architecture explains both the privacy claim and the failure modes. The app does not talk to Google directly in the way the official client does, so the data Google sees is whatever the Piped instance forwards. At the same time, the app's usefulness is bounded by the health of whichever Piped instance it is configured to use. This is a dependency the project does not hide, but it is also the single biggest operational risk for a user. A frontend that depends on community-run infrastructure inherits that infrastructure's outages, rate limits and IP blocks.

The README also lists three integrations that live outside the core playback path: SponsorBlock, which skips sponsored segments in videos; ReturnYouTubeDislike, which provides video dislike statistics; and DeArrow, which provides better titles and thumbnails. Each is a separate service with its own operator. Enabling all three means your client is talking to at least four parties in some form. That is not a contradiction of the privacy goal, since none of them is Google, but it is worth being honest about: the design trades one large data collector for several small ones, and the privacy benefit rests on those small operators behaving differently.

Installing LibreTube on Android

The README offers four distribution channels. F-Droid and IzzyOnDroid are the repository-based options, and the GitHub releases page carries both the latest stable release and a separate nightly tag. There is no Play Store badge in the README, and no iOS or desktop build is mentioned anywhere.

If you use F-Droid, the package identifier is com.github.libretube, and adding the IzzyOnDroid repository gives you the same package from a second index. The GitHub route means downloading an APK from the releases page and installing it manually, which requires allowing installation from unknown sources on your device. The nightly builds are published under a tag named nightly, and the README warns that they include features and fixes before the official release, are generally less stable than normal releases, and are used at your own risk.

For a first run, the practical steps are: install the APK, open the app, and check which Piped instance is selected before you do anything else. The README does not spell out the settings path for this, so treat instance selection as something to find in the app rather than something documented in the repository. Once a working instance is set, search for a channel and subscribe.

The project's contribution notes are worth knowing before you file anything. The README states that feature and bug requests are not accepted on Matrix, Mastodon or Lemmy, and that issues avoiding the issue template will be ignored and closed. It also states that AI-generated issue texts and pull requests are not permitted. If you hit a bug, the GitHub issue tracker with the template filled in is the only accepted channel.

Building from source follows the normal Android path. The README says you can open and build the project like any other normal Android project by using Android Studio. Commit messages are expected to follow conventional commit types such as feat, fix, refactor, ci and chore.

Where LibreTube breaks, and when it is the wrong tool

The honest limitation is the one the architecture creates: LibreTube is only as available as the Piped instance behind it. The search questions around the project include people asking why LibreTube is not working and whether it is still working, which is the pattern you would expect from a client whose backend is community-operated. The README does not document a fallback, an official instance, or a rollback path, and the repository's PRIVACY_POLICY.md and ROADMAP.md are present but their contents are not summarised in the README. If your use case requires guaranteed uptime, this is the wrong category of tool entirely, not just the wrong app.

Platform is the second boundary. The project is Android-only. The search data shows demand for LibreTube for PC and LibreTube iOS, and neither exists in the documentation. If you watch on a laptop or an iPhone, you are outside the supported surface.

Third, the nightly channel is a real trap for the impatient. It is a separate release tag with its own cadence, and the README's own warning is that nightly builds are less stable than normal releases. Someone who installs the nightly for a feature and then reports instability as a bug is doing the opposite of what the project asks.

Finally, there is a governance constraint that is unusual and worth flagging. The README bans AI-generated issue texts and pull requests outright. If your workflow involves drafting reports with a language model, that output will be ignored here. That is a policy choice, not a defect, but it changes how you participate.

LibreTube compared with NewPipe

NewPipe is the obvious comparison, and the search data shows people making it directly. The difference is architectural. NewPipe is a standalone Android client that extracts the data it needs itself, so there is no intermediate server you depend on. LibreTube routes through Piped, which means a server component exists between the app and YouTube.

That single difference drives most of the trade-offs. A standalone extractor has no third-party uptime dependency but must be updated whenever YouTube changes something on its side, and the update has to ship to your device. A server-mediated client can, in principle, absorb some of those changes on the server without an app update, but you inherit the server operator's availability and rate limits instead. Neither approach is strictly better; they fail in different ways and at different times.

Feature-wise, both projects occupy the same niche: subscriptions, background playback, downloads, no ads. LibreTube's README lists SponsorBlock, ReturnYouTubeDislike and DeArrow as built-in integrations, and it lists optional user accounts via Piped. If you want a client with no server dependency at all, NewPipe is the closer match. If you want the option of an account that syncs through a Piped instance, LibreTube is the one that offers it. The README does not compare itself to NewPipe, so treat this as a structural distinction rather than a claim from either project.

Maintenance, releases and the GPL-3.0 licence

The repository is not archived, and the last push was on 2026-09-21. Recent releases are v32.0 and v32.1, both dated 2026-08-20, plus a nightly tagged LibreTube Nightly 21-09-2026 dated 2026-09-02. The version numbering suggests a reasonably active release cadence, and the presence of a separate nightly channel means changes land there before they reach a numbered release.

Upgrade cost is low if you install through F-Droid or IzzyOnDroid, since those clients handle updates for you. It is higher if you sideload APKs from GitHub, because updating means downloading and installing again by hand. The nightly channel adds a third path with its own risk profile. There is no migration or data-format documentation in the README, so if you are moving from another client there is nothing here that describes importing subscriptions.

The licence is GPL-3.0. In practical terms for a user, that is a free-software licence that permits use and modification and requires derivative distributions to carry the same licence. For anyone planning to fork the app or ship a modified build, the obligations attach to distribution, and the LICENSE file at the repository root is the authoritative text. This is a description of what the licence identifier means in general, not legal advice; if you intend to redistribute, read the licence itself.

The project accepts contributions and lists a Code of Conduct, a Weblate translation project, and donation channels including GitHub Sponsors and Liberapay. The README notes that the Matrix room is the main communication channel and that other forums and social media accounts are maintained by community volunteers rather than the developers.

Editorial conclusion

Adopt LibreTube if you watch YouTube on Android and want subscriptions, downloads and background playback without Google's app or tracking. Skip it if you need iOS, a desktop client, or a viewer that keeps working when community Piped instances are down. Before you commit, check which Piped instance the app is pointed at, whether SponsorBlock and DeArrow are enabled in settings, and whether the F-Droid build or the GitHub nightly suits you. The nightly channel is explicitly labelled less stable than normal releases.

Frequently asked questions

Official sources

1. libre-tube/LibreTube on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases