PigeonPod vs Pinchflat: Self-Hosted YouTube Downloads, Podcast RSS, Plex, and Jellyfin

PigeonPod and Pinchflat can both follow YouTube sources, download media, and run on your own infrastructure. The useful decision is not whether either tool can save a video locally. It is whether your primary workflow is following a source in a podcast app, or building and operating a local media library.

PigeonPod self-hosted combines channel and playlist subscriptions, downloaded audio or video, private podcast RSS, and an application workflow for managing the result. Pinchflat is a self-hosted downloader and library manager that can also expose a source as a podcast RSS feed. Its own RSS documentation describes that feature as beta and requires you to handle public access to the feed endpoints.

Only add supported public sources and content you are allowed to access. Neither tool turns restricted, private, removed, or region-limited media into a reliable library.

The short answer

Choose PigeonPod self-hosted when you want podcast RSS to be a first-class part of the workflow, while still retaining downloaded audio and video in a structured local library. It is the better fit when you want to follow selected YouTube updates in a podcast app and may also scan the downloaded media with Plex or Jellyfin.

Choose Pinchflat when your local downloader and media-library workflow comes first. It is a sensible fit when you are already comfortable exposing and securing self-hosted services, and podcast RSS is an additional delivery option rather than the centre of the setup.

Choose PigeonPod Cloud instead when you want the PigeonPod listening workflow without operating the host, storage, backups, and network boundary yourself.

Compare the workflows

Podcast-first library

PigeonPod self-hosted

A self-hosted YouTube subscription and download workflow that also delivers private podcast RSS.

Best for

People who want podcast-app listening and a locally managed media library together.

Media layout

Downloaded audio and video are stored separately, so an external media server can scan the relevant directory.

Trade-off

The storage layout is product-managed; it is not a general-purpose yt-dlp filename-template system.

Library-first downloader

Pinchflat

A self-hosted download and source-management tool with an optional podcast RSS delivery path.

Best for

People whose main goal is maintaining a local YouTube media collection.

Podcast app access

Its RSS feature requires a stable public URL and deliberate authentication and feed-endpoint configuration.

Trade-off

You take responsibility for the host, downloads, storage, networking, and RSS exposure.

This is a workflow comparison, not a permanent feature checklist. Check each project’s current documentation before committing a large library or making a migration plan.

Downloads and media archiving

PigeonPod self-hosted is not limited to lightweight RSS generation. It can download media as audio or video and keep those variants in separate storage paths. The separate video storage directory was added in the open-source release line so an operator can keep audio and video libraries distinct. That makes it practical to point Plex, Jellyfin, Emby, or another scanner at the directory that matches the library you want to browse. See the PigeonPod v1.19.1 release notes.

That is useful, but it has a boundary: separate media folders are not the same as a native Plex or Jellyfin integration. PigeonPod does not promise a custom output filename template for every downstream metadata-agent workflow; a request for yt-dlp-style filename control was closed as not planned. See the related issue. Test a small set of episodes with your media-server scanner before importing an entire channel.

Pinchflat is a strong choice when the local collection is the central product outcome. The decision is not that one tool downloads and the other does not. It is whether you want the application to organize a listening workflow around subscriptions and feeds, or you want to organize your own media-library workflow around downloaded files.

Podcast RSS is where the operating model differs most

PigeonPod treats a private podcast feed as a core delivery path. Add a supported public channel or playlist, manage the source and eligible episodes in PigeonPod, then follow the feed in a compatible podcast app. See the YouTube-to-podcast setup guide for the listener flow.

Pinchflat can serve podcast RSS feeds too, but its official guide asks the operator to make the instance reachable outside the home network, choose an authentication approach, and explicitly expose the RSS, image, and media endpoints needed by a podcast client. That is a sound self-hosting design, but it is work you should expect to own. Read Pinchflat’s podcast RSS guide.

If you use a podcast app that fetches feeds from its own servers, a private LAN address will not be enough. Whichever tool you choose, validate feed refresh and media playback from the actual client before moving your full library.

Plex and Jellyfin: use them as a separate delivery layer

Plex and Jellyfin are media servers, not replacements for a private podcast RSS workflow. They work best when you want to browse and watch a local video collection from a TV, browser, or media-client interface. A podcast app works best when you want an audio-first subscription queue on a phone, watch, or in the car.

With PigeonPod self-hosted, the separate audio/video directories let you keep those delivery paths distinct: use podcast RSS for the listening queue, and let your media server scan the video library when you want a screen-first catalogue. With Pinchflat, the local library is naturally the focal point; add RSS when a podcast client is another useful way to consume a source.

Neither approach removes the normal self-hosting work: storage capacity, backups, upstream platform changes, secure remote access, and upgrades remain your responsibility.

Choose PigeonPod self-hosted when

• You want YouTube channels or playlists to become private podcast subscriptions, not just downloaded folders.
• You want audio-first listening in a compatible podcast app, while retaining downloaded media locally.
• You want one product workflow for subscriptions, filtering, downloading, and private RSS.
• You want to keep audio and video in separate directories for a Plex or Jellyfin library scan.
• You are comfortable self-hosting, but do not need fully custom download filenames for every external tool.

Choose Pinchflat when

• Your priority is a local download library and its surrounding media-server workflow.
• You are comfortable configuring a stable external URL, reverse proxy or equivalent access layer, authentication, and feed exposure.
• Podcast RSS is useful, but it is not the primary product boundary you are optimizing for.
• You want to evaluate a downloader-oriented workflow before adding a separate podcast delivery layer.

A practical test before you choose

Run one real channel or playlist through the workflow you intend to use:

1. Subscribe to a supported public source.
2. Download a few audio and video episodes.
3. Let Plex or Jellyfin scan the intended local directory, if that is part of your plan.
4. Add the RSS feed to the podcast app you actually use away from home.
5. Confirm that new uploads, media playback, storage usage, and cleanup behave the way you expect.

Choose PigeonPod self-hosted if that test shows you value the podcast workflow and local media library equally. Choose Pinchflat if the library itself is the product you are building. If you want the PigeonPod workflow without the operational work, start with PigeonPod Cloud instead.