gPodder is a free desktop podcast download manager for Windows, macOS and Linux. It follows feeds and saves episodes to your computer, then uses a separate media player for playback. This walkthrough builds a small collection from publisher-provided RSS feeds. It does not unlock Spotify Premium or paid and exclusive catalogs. AltStack reviewed provider documentation and stable 3.11.5 interface definitions on October 23, 2026; we have not installed or tested the application, installers or a podcast download for this article.

1. Check costs and choose a small first task

gPodder is GPL-3.0-or-later free software. You supply a computer, disk space, a connection and a media player. Optional synchronization and individual publishers can have separate accounts or charges. A subscription feed remains subject to its publisher's terms even when the reader is free.

Choose this workflow for collecting episodes from feeds you can use and retaining local copies. Moving a subscription list from Pocket Casts or Spotify does not transfer premium access, listening history or exclusive recordings. Start with one public podcast whose creator supplies RSS. A small trial helps you decide whether desktop download management fits your listening habits before migrating a large library.

2. Install from the official download page

The provider's site lists gPodder 3.11.5 as its current stable desktop release. Windows users can choose an installer or portable package. On macOS, use the linked macOS package and check its release information against your system. Linux users can follow the site's Flatpak link or use their distribution's package; packaged versions can differ.

Keep the package source and version in your setup notes. Use the operating system's normal installation process and resolve any compatibility or verification warning through provider guidance. Do not disable platform security to follow this guide. A source checkout has separate Python and GTK requirements, so a ready-made package is the simpler starting point for this exercise.

3. Add a publisher's actual RSS feed

Choose Subscriptions > Add podcast via URL and paste the publisher's feed address. This is the stable 3.11.5 menu label; older manual sections use a different subscribe label. Check the resulting title before accepting a similarly named podcast.

Prefer a public feed without a password or token for the first trial. A podcast's ordinary website address is not always its feed address. If discovery fails, return to the creator's RSS or subscribe link instead of repeatedly guessing URLs. Keep the original address in your notes so you can distinguish a publisher-side change from a local configuration problem.

4. Download one episode before automating

Select a short episode and choose Episodes > Download. Wait for completion before testing it as an offline file. A small download separates feed access, transfer and playback while limiting bandwidth and storage use.

Review Preferences before turning on automatic downloads. Choose behavior appropriate for your connection and free disk space, then add feeds gradually. Check the destination and a completed file rather than treating a title in the episode list as proof of a saved recording. Retain files only within the publisher's permissions and access terms. Avoid a first experiment that immediately fills your drive with an entire feed archive.

5. Configure the separate playback application

In Preferences, select an installed audio player, then use Episodes > Play on the completed download. gPodder handles subscriptions and downloads; the player supplies the listening experience. Follow provider instructions if setting a custom player command.

Test pause, seeking and reopening that same file. Resume position and playback speed depend on the chosen player and integration. If the file works when opened directly in the player but fails through gPodder, inspect the player selection first. Re-downloading it is unlikely to solve an application-association problem. Keep the working downloaded file available while testing changes.

6. Export subscriptions with OPML

Use Subscriptions > Export to OPML file to retain the feed list. The stable release also provides Import from OPML file. Keep an untouched export from your previous app and try a small recognizable group before importing hundreds of subscriptions.

OPML carries feed addresses, not every recording or a universal copy of played status. Plan those needs separately. Check titles and duplicates after importing, and save a dated export somewhere accessible without launching gPodder. Private feed URLs can contain access tokens: do not place them in public screenshots, support reports or shared example files. A subscription backup deserves the same privacy review as the addresses it contains.

7. Back up metadata and recordings separately

Decide whether your goal is recreating subscriptions or preserving a listening archive. An OPML file helps with the former; missing audio needs its own backup. The manual documents the application home directory and GPODDER_HOME/GPODDER_DOWNLOAD_DIR overrides. Package type, existing settings and operating system affect the actual location, so verify it before copying or relocating data.

Close the app before copying metadata consistently. Leave the originals in place while checking your backup, and record the version that created it. Verify a few copied recordings. A backup is useful only when it contains what you expect and you can find it later; changing storage paths is a separate task from following a feed.

8. Review sync, extensions and network privacy

gpodder.net synchronization is optional and needs its own account and service availability. Export first, decide which device holds the list you want, and read any action that replaces remote subscriptions carefully. Sync should not be the first experiment with your only copy.

Local storage does not make feed retrieval anonymous or offline: requesting a feed or episode contacts its hosting provider. Extensions can add external programs and services. Keep optional integrations disabled until a concrete need justifies them, then review their dependencies and privacy separately. AltStack has not measured the application's network traffic or audited every plugin.

9. Troubleshoot the failing layer

For an empty feed, check the creator's RSS address and whether it is still available. For a transfer failure, compare another small episode and check the destination's free space and permissions. For playback failure, open the completed file directly in the chosen media player before changing feed settings.

Record your app version, operating system, package source and the exact failed step, removing private URLs and credentials before asking for help. Historical manual sections describe older mobile editions and integrations; use stable-release labels for this desktop workflow. A useful first result is one verified feed, one completed download, working playback and a checked OPML backup. Expand only after those pieces work together.

Official instructions and sources

Official packages and stated stable versionStable 3.11.5 packages and checksumsActual stable subscription, playback, download and OPML menu definitionsProvider manual: preferences, feeds, backup and storageGPL terms and runtime dependency distinctionsActual distributed GPL license

Original AltStack guide by Sushil Kumar Sah. Installation steps follow provider documentation; they do not imply testing on every supported device.