Open the Podcasts app on your Mac and look at a show you subscribed to months ago, and you may find a dozen episodes still sitting there marked as downloaded. Podcasts keeps a local copy of every episode it downloads so playback works without a connection, and it stores those files in its own per-app group container, roughly ~/Library/Group Containers/243LU875E5.groups.com.apple.podcasts. On its own that is not a problem — a handful of downloaded episodes is a few hundred megabytes. The problem starts when you are subscribed to a dozen shows with "download all new episodes" switched on, especially if some of them run long interview formats or publish video. Multiply a few hundred megabytes by every show, every week, and the total grows until Storage Settings shows Podcasts as a surprisingly large slice of your disk.

Where the downloaded audio actually lives

Podcasts, like most modern Mac apps, keeps its data inside its own sandboxed container rather than scattering files around your home folder. The general location is the group container named for the Podcasts app, under ~/Library/Group Containers/. We say "roughly" and "general location" deliberately: Apple has changed the internal folder layout inside that container across macOS releases, and the exact subfolder names are not something worth memorising or depending on. What matters practically is that the space is real, it is measurable, and it belongs entirely to episodes you or the app chose to download.

You can confirm how much space is involved without touching anything inside it:

du -sh ~/Library/Group\ Containers/243LU875E5.groups.com.apple.podcasts

That number is a read-only measurement. It tells you whether Podcasts is worth investigating further; it does not tell you which files to delete, because you should not be deleting files there directly (more on why below).

Why the folder grows without you noticing

Podcasts defaults to convenience over caution. When you subscribe to a show, its default setting is often to download new episodes automatically as soon as they publish, so you always have something ready when you open the app. That is a sensible default for one or two shows. It stops being sensible once you have accumulated a long list of subscriptions over the years, some of which you no longer actively listen to but never unsubscribed from. Each of those shows keeps quietly downloading new episodes in the background, and episodes you have already heard do not always get removed automatically unless you have told the app to do so. Video podcasts and long-form interview shows make this worse — an hour of video or a three-hour conversation is a much bigger download than a fifteen-minute daily briefing.

The per-show settings that actually control this

Podcasts gives you fine-grained control per show, and this is the setting most people never open. From a show's own page, tap the "..." menu (or use Podcasts > Settings for global defaults) to find options that govern:

  • How many recent episodes to keep downloaded at once, rather than keeping everything indefinitely.
  • Whether to automatically remove an episode once you have finished playing it.
  • Whether new episodes download automatically at all, or only when you tap to play them.

Setting a sensible limit — say, keep the three most recent episodes — means a show you forgot you were subscribed to cannot silently accumulate a season's worth of audio. This is the setting worth checking first for any show you have been subscribed to for more than a year.

Why hunting through the container folder is the wrong approach

It is tempting, once you know the group container path, to go in with Finder and start deleting files you do not recognise. Resist that. Podcasts keeps its own database of what has been downloaded, what has been played, and what your per-show settings expect to exist. If you delete files directly from underneath the app, that database falls out of sync with what is actually on disk, and Podcasts can behave unpredictably — showing episodes as downloaded when they are not, or failing to detect that space is available for new downloads. This is not a defect specific to Podcasts; most apps that manage their own local cache of remote content expect to be the only thing writing to and reading from that cache.

The supported way to reclaim the space

The reliable path is entirely inside the app. Two actions do the actual work:

  1. Adjust the per-show download and retention limits described above, so future accumulation stops.
  2. For episodes you have already listened to, use the app's own controls to clear their downloaded status — this removes the local audio file while leaving the episode in your history, and it is the action Podcasts expects you to take, so its own bookkeeping stays correct.

Doing an occasional pass through your subscriptions list, tightening the retention limit on shows you rarely get around to, and clearing already-played downloads is a five-minute task that keeps this category from creeping back up. There is no faster or safer route through the app's own storage than the app's own settings.

Conclusion / VolumeLens tie-in

Podcasts downloads are a good example of a storage category that looks alarming until you understand the mechanism behind it: nothing sinister is happening, an app is just doing exactly what its default settings told it to do, for years, without anyone checking in. The fix is rarely deletion — it is turning a permissive default into a deliberate one.

We built VolumeLens because we needed a way to see which of these background categories was actually large on a given Mac, without guessing or digging through container folders by hand. It scans your disk, shows you where a Group Containers folder or any other unfamiliar directory sits relative to everything else, and lets you decide what to do next — without ever touching a file it cannot safely account for. You can download VolumeLens and point it at your own ~/Library to see exactly how much of it is Podcasts, and how much is something else entirely.