What a podcast host actually does
A podcast host does two jobs. It stores your audio files and delivers them to listeners, and it generates the RSS feed that describes your show. Everything else a host sells sits on top of those two jobs. Get the two jobs clear and the rest of the decision gets simple.
When someone presses play in a podcast app, that app is not pulling the file from Apple. It is fetching your audio from wherever your host keeps it. That is why Apple's RSS feed requirements say your hosting server has to support HTTP HEAD and byte range requests, and why the feed itself has to be publicly addressable rather than password protected.
The feed is the other half. It is a text file, updated every time you publish, that lists your show title, artwork, category, and every episode with a link to its audio file and a permanent identifier. Apple's requirements are explicit that a feed can be self generated and hosted or issued by a hosting provider. Paying a host means paying someone to write that file correctly so you never have to think about it.
Your host is the landlord. The apps are just readers.
You never upload an episode to Apple or Spotify. You submit your feed URL once, and from then on those apps check the feed on their own schedule and pick up whatever is new. This is the single fact that clears up most beginner confusion about hosting.
It also means you are not on twelve platforms. You have one feed being read twelve times. Beginners hear that a show is on Apple, Spotify, Overcast, Pocket Casts, and Amazon, and assume five separate publishing chores. There is one chore, and it happens at your host. The apps handle themselves.
Why this matters the first time something breaks
You publish an episode with the wrong audio file, or a typo now sitting in someone's feed. You do not fix that at Apple. You fix it at your host, the feed regenerates, and the apps pick up the correction the next time they read it. Knowing where the source of truth lives saves you an afternoon of clicking around a directory that cannot help you.
What you are actually paying for
Storage and delivery are the floor, and almost every host clears it. What separates platforms is everything stacked on top: feed control, analytics, an episode page or website, transcripts, dynamic ad insertion, and how much of your own data you can take with you.
- File storage and delivery. Your audio, served fast enough that nobody waits on it, from anywhere in the world.
- Feed generation. The correct XML, with permanent episode identifiers, updated the moment you publish.
- An episode page. A public URL per episode with show notes, which is where your sponsor links and guest links live.
- Download analytics. How the host counts a download, and whether that count follows a standard a buyer recognizes.
- A website and transcripts. Increasingly bundled, and genuinely useful for search, though not a reason to pick a host on its own.
- Dynamic ad insertion. The ability to place an ad into a slot and change it later, including in old episodes. Only matters if selling ads is the plan.
The five questions that actually decide it
Skip the feature grids. Five questions separate hosts that will still fit your show in three years from hosts that will not. Ask them in this order, because the first one protects every answer after it.
- Can you redirect the feed away later? If a host will not let you point your feed somewhere else, nothing else about the plan matters, because you cannot leave without abandoning your audience.
- How are downloads counted? Look for adherence to the IAB Tech Lab Podcast Measurement Technical Guidelines, which define how downloads, audience, and ad delivery are measured, and for the related compliance program.
- What does it cost as the catalog grows? Read the pricing page for what happens at episode one hundred, not episode one. Hosts meter different things, and the cheap plan for a new show is not always the cheap plan for a running one.
- Does it support dynamic ad insertion? Skip this if sponsorship is not the plan. If it is, you will want to change an ad without re-uploading audio, and hosts differ on whether that is included, extra, or absent.
- How easily can you leave? Can you export your audio files and your episode identifiers, intact, without asking permission. Check this on the way in, not on the way out.
Question two is the one that resurfaces in a sponsor conversation a year later. A buyer comparing your show against another is comparing numbers produced by two different measurement systems, and if yours were not counted to a common standard, the comparison quietly goes against you. Pod Green Room builds your media kit from your show's real numbers instead of numbers you retype, which only helps if the numbers your host reports are ones you can defend.
You are not locked in
Switching hosts is a routine operation, not a catastrophe. Apple supports it directly: put an itunes:new-feed-url tag in the new feed and have the old host return a 301 redirect. Followers move across and keep getting episodes. The risk is not switching. The risk is switching sloppily.
Apple's guidance on changing the RSS feed URL says to keep both the tag and the 301 redirect in place for at least four weeks so followers land on the new feed. Its guidance on changing hosting providers adds the part people miss: episode identifiers must not change, because new ones can produce duplicate episodes and distort your analytics.
A botched migration does lose subscribers, and it loses them predictably. Someone kills the old feed the day the new one goes live, and every app still pointed at the old address gets nothing. Or the new host regenerates identifiers, and listeners see the whole back catalog arrive again as new. Both are avoidable, which is what lets you pick a host without treating it as a marriage.
The honest read on free plans
Free hosting is real, and plenty of shows launch on it without regret. But free plans differ enormously, so read for three things specifically: whether you can redirect the feed away, how much analytics detail you get, and whether monetization is restricted. Storage limits are the least important line.
Those three are the ones that cost you later. A plan that keeps analytics shallow leaves you unable to answer a sponsor's first question. A plan that takes a cut of monetization, or routes sponsorship through its own marketplace, has priced itself and you just did not see the invoice. And a plan that will not let you redirect the feed is not free at all. It is a deposit you cannot get back.
The category itself is crowded and mostly competent. Buzzsprout, Libsyn, Transistor, Captivate, Podbean, Spotify for Creators, and RedCircle are all in it, along with plenty of others. I am not going to rank them here, because pricing and features change faster than any article can honestly track, and because the ranking is not the point. Your answers to the five questions above are what decide which one fits your show.
Hosting is a solved problem. Publishing is not.
You can pick a host in an afternoon and be right often enough. What decides whether the show is still running in a year is whether you publish on schedule, and that is not a hosting question. For an interview show, it is a booking question.
Shows rarely go quiet because a host failed. They go quiet because the week after next had nobody booked and nobody noticed until it arrived. Pod Green Room treats that as the real infrastructure: your bookings run as a guest pipeline with follow-up nudges attached, so an empty slot surfaces while there is still time to fill it.
Once the feed is live, the free sponsor readiness grader reads it the way a sponsor would and tells you what your setup is signaling. And the guide to booking podcast guests covers the outreach cadence that keeps the schedule full enough that hosting never becomes the interesting problem.