PipePipe is an open-source Android app whose project describes it as a way to browse YouTube and other services. Its README presents the app as a reimagining of NewPipe and lists features ranging from SponsorBlock to playlist tools and playback gestures. This article follows the project’s own documentation and separates those descriptions from claims that would require independent testing.
In short: PipePipe began as a NewPipe fork and has been developed independently since early 2022. Its maintainer says it neither receives updates from NewPipe nor sends its own changes upstream. The README lists SponsorBlock for YouTube and BiliBili, restored YouTube dislikes, danmaku-style live-chat overlays, AV1 and VP9 support, search filters, playback controls, and playlist features. These are project statements, not the result of a device-by-device review.
What Is PipePipe?
PipePipe is an Android project hosted in a public GitHub repository. The repository description calls it an open-source app for browsing YouTube and other services, while the README uses the phrase “NewPipe, reimagined.” The README is the primary source for the feature list in this article; it describes what the maintainers say the project provides rather than offering an independent benchmark or compatibility test.
The maintainer says the project started by forking NewPipe in early 2022 because of differences in development philosophy. The README says the fork then moved into independent development. That history matters more than the label alone: PipePipe and NewPipe are separate projects, with their own repositories and change histories, rather than two names for a single synchronized release line. See the official PipePipe repository for the current description and documentation.
What Does Independent Development Mean?
The README is explicit about how changes move between the projects: PipePipe does not receive NewPipe updates and does not push its changes back to NewPipe. It also says that issues found in NewPipe do not necessarily occur in PipePipe and that changes made in NewPipe may not be adopted by PipePipe. In practical terms, a fix or feature in one repository should not be assumed to exist in the other.
The project maintainer presents a hard fork as a way to address issues with quick fixes and maintain frequent feature updates. That is the project’s stated rationale. Readers comparing update histories can check the release information in each project’s repository.
This distinction also changes where users should look for help. If a playback problem occurs in PipePipe, the relevant issue tracker is PipePipe’s own repository. A report filed against NewPipe may describe a related part of the code history, but the README warns that problems do not necessarily carry over. Conversely, a change in NewPipe may not appear in PipePipe unless its maintainers choose to implement it separately.
How Does PipePipe Describe SponsorBlock and Dislikes?
The README places SponsorBlock under “YouTube Enhancements” and describes it as a way to skip sponsored segments in YouTube and BiliBili videos. The project also lists restoring YouTube dislikes through ReturnYouTubeDislike. Those are separate feature entries in the official documentation; they should not be stretched into a promise that every video, account, or service exposes the same data or behavior.
The same section lists showing original, non-localized YouTube titles. It also says users can log in to access restricted or premium content. Anyone relying on a particular item should check the current release notes and test that option in the installed version.
The useful takeaway is specific: PipePipe’s own documentation names SponsorBlock for YouTube and BiliBili, and names ReturnYouTubeDislike for restoring YouTube dislikes. The feature list identifies options to investigate; readers can compare the clients against their own needs.
What Media and Playback Features Are Listed?
PipePipe’s README says the app can display live chats as danmaku-style overlays. Danmaku is the presentation style named by the project. Check the current release and a suitable stream to see how the option works in practice.
The same media section lists support for the AV1 and VP9 codecs and describes them as intended for efficient, high-quality playback. Check the playback settings and results on the device you use.
A music-player mode with background playback is another listed option. That can matter to someone who wants audio to continue while another app is open, but the README’s short entry is not a complete guide to Android background restrictions, lock-screen controls, or battery behavior. Those details can depend on the device and app version, so check the current settings rather than inferring them from the feature name.
Can Users Filter What Appears?
The README lists advanced search filters and options to filter unwanted items by keywords or channels. It separately names controls for blocking Shorts and paid videos. Users can check the current app settings to see how these options fit their own workflow.
That distinction is useful when evaluating the app. If your goal is to hide a specific content type, open the current version’s settings and try the option before relying on it.
The project’s filtering entries describe search filters and user-selected exclusions. Users choose the filters and decide whether the resulting list suits their needs.
What Gestures and Playlist Tools Are Included?
The playback-controls section lists swipe-to-seek and fullscreen gestures, changing playback speed with a long press, and a sleep timer. Check the current version for the exact gesture map and speed settings, especially if a gesture conflicts with a device’s navigation controls.
For playlists, PipePipe lists downloading full playlists at once. It also lists searching and sorting within local playlists and histories. These are distinct tasks: the first concerns obtaining a playlist’s media, while the second concerns organizing items already represented in the app. Try the relevant option with the playlist and service you use.
The feature set is therefore broader than a single SponsorBlock integration. Someone who values playlist organization may care about local search and sorting; someone using the app for listening may care about background playback and the sleep timer. Whether those features work for a specific account or source still needs to be checked against the current app and service conditions.
What Does the README Say About Login Cookies?
PipePipe has a separate “About sign in” section. It says the app uses a login cookie only for scenarios selected by the user in “Cookie Functions.” For YouTube, the README narrows that use to retrieving playback streams. This is the project’s own explanation of cookie behavior, and it is more specific than a general claim that the app either always or never uses account data.
For account-related use, read the current instructions, check which cookie options are enabled, and use only the scenarios you actually need.
Where Does the Project Point Users for Downloads?
The official README links to PipePipe listings on F-Droid and IzzyOnDroid. These are the destinations shown by the project itself: F-Droid and IzzyOnDroid. Check the listing and its current version before installing.
The official GitHub repository is the place to check the README, issues, changes, and release information. Because PipePipe is not synchronized with NewPipe, the history of one project is not a substitute for the history of the other. Users should verify that a package or release points back to the intended PipePipe project.
How Should the Feature List Be Read?
The README is useful because it identifies the project’s stated scope in concrete terms: video enhancements, media playback, filtering, controls, playlists, and account-related behavior. This article summarizes those project descriptions; test the specific options you need in the version you install.
A practical check starts with the feature you actually need. Look for it in the current release notes, confirm the relevant setting in the app, and test it with a source you can use. For a problem or missing option, consult PipePipe’s own repository, since the maintainer says updates and changes do not move automatically between PipePipe and NewPipe.
This approach avoids two common leaps: treating a listed feature as proven to work in every environment, and treating the word “hard fork” as evidence that one client is better. PipePipe has a distinct development path and a detailed feature list. The right question is whether those documented options match your use case and are present in the version you install.
Frequently Asked Questions
Does PipePipe receive updates from NewPipe?
No. Its README says the project neither receives updates from NewPipe nor sends changes back. The maintainer says independent development began in early 2022.
Which services does the README name for SponsorBlock?
It lists sponsored-segment skipping for YouTube and BiliBili. Check the current app and the videos you use for the behavior you need.
Which codecs are listed?
The project lists AV1 and VP9. Check playback on the device you use.
Where does PipePipe point users for downloads?
The README links to project listings on F-Droid and IzzyOnDroid, as well as the official GitHub repository. Check the current package and release information before installing.
How does the project describe YouTube login cookies?
The README says cookies are used only for scenarios the user selects in “Cookie Functions.” For YouTube, it says the cookie is used when retrieving playback streams.
Summary
PipePipe is a NewPipe fork with an independent development path and its own feature list. Its README says the projects do not exchange updates, and lists SponsorBlock for YouTube and BiliBili, dislike restoration, danmaku-style live chat, AV1 and VP9 support, filters, playback gestures, playlist tools, and selected cookie use.
Those are the maintainer’s descriptions. This article summarizes them rather than reporting a device-by-device review. Read the current repository and release information, then check the specific options you need in the version you install.