PipePipe Brings SponsorBlock to a NewPipe-Style Android Player

Picture a 40-minute tutorial that finally reaches the useful part—then the presenter pauses for a two-minute password-manager pitch. You drag the seek bar, overshoot, drag back, and lose the thread.

That small annoyance explains the appeal of PipePipe. PipePipe is an open-source Android video app based on NewPipe, but it is not a skin or a plug-in. It is a hard fork: a project copied from another codebase and then developed independently. Its defining extra is built-in SponsorBlock support, which can skip community-marked sections inside videos on YouTube and BiliBili. (github.com)

PipePipe starts with a deliberate split

NewPipe is a lightweight front end, meaning an app that gives you another way to browse and play content from online services. It can fetch service data through official interfaces where available, or parse websites and internal interfaces when necessary. The project also avoids proprietary libraries such as Google Play Services, which makes it useful on devices and custom Android systems without Google apps.

PipePipe keeps much of that shape: local subscriptions and playlists, background playback, downloads, search filters, playback gestures, and support for several services. It adds its own direction rather than waiting for changes to land in NewPipe. As of September 26, 2026, PipePipe’s GitHub release page lists v5.4.0 as the latest release, while the suggested F-Droid package is v5.3.1, added on September 12. That gap is a reminder that app repositories can trail a project’s own release page.

SponsorBlock is a timeline, not a magic ad filter

The useful mental model is a second timeline layered over the video. SponsorBlock is a crowdsourced database, meaning viewers submit and review time ranges that mark sponsored messages, introductions, outros, self-promotion, and other categories. A compatible player requests those ranges, compares them with the current playback position, and skips or marks them according to the user’s settings. It does not edit the original video file.

A simplified segment record might look like this:

{
 "category": "sponsor",
 "segment": [312.4, 371.9],
 "videoDuration": 1460
}

The real SponsorBlock response also includes identifiers and additional information used to judge whether a submission still matches the current version of a video. The important part is the pair of numbers: playback should move from 312.4 seconds to 371.9 seconds when the player reaches that interval. SponsorBlock exposes this data through an application programming interface, or API, which is a structured way for software programs to exchange information. (github.com)

Because people create the database, errors are part of the bargain. A creator may trim a video, change the location of a sponsorship, or publish a new edit under the same link. A viewer may also choose the wrong category or mark a boundary a few seconds early. PipePipe’s documented SponsorBlock work has included a manual mode, submission support, BiliBili support, and background loading of segment data so the player interface does not have to wait before appearing.

Why this feature belongs in a fork

NewPipe and PipePipe made different choices about what a privacy-focused media app should do. NewPipe’s project has argued that sponsorships embedded in videos can be a relatively privacy-friendly way for creators to fund their work: viewers see the same message, and the sponsorship itself does not require targeted advertising. The project therefore decided not to support SponsorBlock, which skips sponsored sections without distinguishing between different kinds of advertising. (newpipe.net)

PipePipe accepts a different trade-off. Its author describes the project as an independent development line started from NewPipe in early 2022. A hard fork gives the new project room to change behavior, add services, and fix issues without waiting for agreement from the original maintainers. The cost is just as real: fixes do not automatically flow between the two apps, and a solution for NewPipe may never appear in PipePipe, or the other way around.

The three pieces under the hood

SponsorBlock integration makes more sense when you separate it into three moving parts.

1. Content extraction. An extractor is the part of the app that turns a service response into usable information such as a title, thumbnail, stream URL, duration, and video identifier. NewPipe and PipePipe both rely heavily on this layer because they do not use the normal official mobile application as their playback shell.

2. Segment lookup. Once the app knows which video is playing, it asks the SponsorBlock service for matching ranges. The API supports a privacy-oriented lookup in which a client hashes the video identifier with SHA-256, a one-way hashing algorithm, and sends only a short prefix of that hash. The server can return several possible matches without receiving the exact video identifier in that request. This is a capability documented by SponsorBlock’s API; the precise request path depends on the client implementation.

3. Playback control. The player watches its current timestamp. When that timestamp enters a segment marked for skipping, it seeks to the end of the range. Other categories can be shown on the seek bar or handled differently, which is why SponsorBlock is more flexible than a single on-or-off advertisement switch.

That last step is where a small timestamp database becomes a noticeable user experience. The player must handle buffering, seeking, downloads, live playback, and changes in video duration without jumping at the wrong moment. PipePipe’s release notes and development discussions show attention to that detail, including asynchronous SponsorBlock loading, meaning the lookup runs in the background while the rest of the player remains responsive.

What installing PipePipe changes

PipePipe is best treated as a separate app rather than an ordinary NewPipe update. F-Droid recommends installing its client for updates, while direct Android application package downloads, commonly called APKs, do not provide the same update notifications and are described as a less secure installation path on the listing. The current suggested F-Droid build requires Android 6.0 or newer. (f-droid.org)

Moving between the projects also deserves a backup first. NewPipe recommends exporting subscriptions, history, and playlists before changing installation sources, then importing the saved database afterward. Since PipePipe and NewPipe are independent projects, it is unwise to assume that every setting or database detail will transfer perfectly between them.

PipePipe also supports login for selected scenarios. Its documentation says the app uses the login cookie—a small stored piece of account state—only for the functions you enable, and for YouTube it limits cookie use to retrieving playback streams. That is narrower than sending login information through every feature, but a signed-in setup still deserves more care than anonymous browsing.

PipePipe is interesting because it turns a disagreement about video sponsorship into a concrete engineering choice. NewPipe preserves its original privacy and advertising position; PipePipe builds a separate Android player around features such as SponsorBlock, additional services, and more playback controls. The result is not merely NewPipe with one extra switch. It is a different project, using community-maintained timestamps to make long videos feel a little less interrupted.