A podcast RSS feed is an XML file that lists a show's episodes, audio file locations, titles, and release dates so podcast apps can find and download them. It's the delivery mechanism, not the audio itself. Without a working feed, your show exists only on your hosting dashboard, invisible to Apple Podcasts, Spotify, and every other listening app.

The confusion most people hit: they think the RSS feed is something you build once and forget. In reality, it's a live document your podcast host regenerates every time you publish, and any mistake in its structure breaks distribution across all directories at once. Understanding what's inside that file, and who controls it, is the difference between a show that appears everywhere and one that mysteriously stops updating.

The XML File Behind Every Podcast Episode

RSS stands for Really Simple Syndication, and it's a text format that predates podcasting by years. The specification most podcast feeds follow today traces back to RSS 2.0, published in 2003, with podcast-specific additions layered on through Apple's podcasting guidelines. A feed is plain text anyone can open in a browser or text editor.

Open a podcast feed and you'll see nested tags. The element wraps everything and holds show-level data: title, description, artwork URL, and contact email. Inside sit individual elements, one per episode, each carrying an enclosure tag that points to the audio file. That enclosure tag is the podcasting innovation β€” a standard RSS field repurposed to attach media files.

The feed itself is usually generated by your podcast hosting platform. You record audio, upload it, fill in episode details, and the host writes or updates the XML automatically. Most hosts give you a feed URL in the format https://yourhost.com/feed/showname or similar, and that single URL is what you submit to directories.

Here's the part that trips people up: the feed doesn't contain your audio. It contains links to where your audio lives, typically on a content delivery network the host operates. Delete an episode from your host and the feed entry vanishes β€” but anyone who already downloaded that file keeps their copy.

Why One URL Controls Your Show Across Apple, Spotify, and YouTube

Apple Podcasts, Spotify, and every other directory don't host your podcast. They read your RSS feed and build their own index from it. When you submit a feed to Apple Podcasts, Apple's servers check it periodically and pull in new episodes. Spotify does the same, though Spotify also offers its own hosting for shows that want to skip RSS entirely.

This architecture means your feed URL is the single most important piece of your podcast's identity. Change hosts without setting up a 301 redirect from the old feed to the new one, and every directory loses track of your show. Apple's own podcasting documentation warns that a broken feed URL can take days or weeks to resolve, and some directories may drop the show entirely.

The directories poll on different schedules. Apple Podcasts historically checked feeds roughly every few hours to a day depending on the show's activity; Spotify's refresh timing isn't published. This is why a new episode sometimes shows up on one platform before another. It's not a bug in your feed β€” it's the polling interval.

If you want to see the raw structure, paste your feed URL into a browser. You'll get XML. If your podcast host offers a "feed preview" or "RSS validator" tool, use it before submitting anywhere; Apple's Podcasts Connect and third-party validators like Podba.se flag broken tags, missing artwork, and malformed dates.

What Actually Lives Inside the Feed

Every podcast feed carries two layers of metadata: channel-level and item-level. Channel data tells a directory what the show is. Item data describes each episode. Both matter for discovery, and both are editable β€” usually through your host's dashboard rather than by hand.

Channel-level tags include , , , and itunes:author. The itunes:image tag points to your cover art, which Apple requires at a minimum of 1400Γ—1400 pixels in RGB, though 3000Γ—3000 is the current standard. That artwork URL must be publicly accessible; a private or expiring URL will break your listing.

Item-level tags carry the episode. The tag needs three attributes: the audio file URL, its byte length, and its MIME type (usually audio/mpeg for MP3). Get the length wrong and some apps refuse the file. The tag uses RFC 822 format, and a malformed date can push an episode to the bottom of a feed or hide it entirely.

Tag Level What it does Common failure
Episode Points to the audio file Wrong byte length blocks download
Episode Sets release date Bad format hides the episode
itunes:image Show Cover art URL Expiring URL breaks listing
itunes:explicit Show or episode Content rating Missing tag delays Apple review
Episode Unique episode ID Duplicate GUIDs collapse episodes

The tag deserves attention. It's a permanent identifier for each episode, and directories use it to decide whether an episode is new or already indexed. Reuse a GUID across two episodes and one of them simply won't appear. Most hosts generate GUIDs automatically, which is why editing episodes through your dashboard is safer than hand-editing XML.

Self-Hosting Versus a Podcast Host: The Real Trade-Off

You can write a podcast RSS feed by hand and serve it from any web server. People did this in the mid-2000s. The question today is whether the control is worth the operational burden, and for most creators it isn't.

A manual feed means you maintain the XML, host the audio files, manage bandwidth, and handle the byte-length and MIME-type details yourself. Bandwidth is the killer. A 60-minute MP3 at 128 kbps runs about 55 MB; 1,000 downloads of that episode is roughly 55 GB of transfer. A modest shared host will throttle or bill you for that. Podcast-specific hosts exist because they solve exactly this problem.

Approach Feed control Bandwidth handling Setup time Best for
Manual XML on web host Full You pay and manage Hours Developers, archival projects
Podcast host (e.g., Buzzsprout, Libsyn, Podbean) Templated, editable metadata Included with plan Under an hour Most independent shows
Spotify for Podcasters (hosted) Limited, Spotify-centric Included, free Under an hour Shows prioritizing Spotify

The hosted route has a real drawback: you're locked into the host's feed structure and analytics. Migrating means exporting audio and republishing, or redirecting the feed if the host supports it. Libsyn and Buzzsprout both offer feed redirects on paid plans; free tiers often don't, which is why a free host can become expensive in time when you outgrow it.

Choose manual hosting only if you have server skills and a reason to own every byte. Otherwise pick a host with redirect support from day one. The redirect is your escape hatch, and it costs nothing to confirm it exists before you upload a single episode.

Redirects, Migrations, and the 301 That Saves Your Audience

When you move a podcast to a new host, the old feed URL becomes a liability unless you redirect it. A 301 permanent redirect tells directories and apps that the feed has moved, and they follow it to the new location. Without one, subscribers who added your show by its old feed keep polling a dead URL.

The redirect needs to point from the old feed URL to the new one, and it has to stay in place indefinitely. Apple's guidance is that the redirect should persist; removing it after a few months can orphan listeners whose apps cached the old address. Some hosts charge for this feature on lower tiers, so confirm it before migrating.

A redirect also matters for the audio URLs, not just the feed. If your old host deletes the audio files after cancellation, episodes that were already indexed but not yet downloaded will 404. Most hosts keep files accessible for a grace period after cancellation β€” Buzzsprout's terms and Libsyn's terms both specify windows that change, so check the current policy on each provider's site before you cancel.

The failure case worth remembering: a redirect set up wrong, pointing to a 404 or a staging URL, is worse than no redirect. Directories may mark the feed as broken and stop checking. Test with a feed validator and open the redirect chain in a browser before you cancel the old account.

What Makes a Feed Fail in Apple Podcasts and Spotify

Feeds break for predictable reasons. Apple's Podcasts Connect rejects feeds with missing required tags, artwork below the minimum size, or enclosure URLs that return errors. Spotify's ingestion is more forgiving on metadata but strict about audio accessibility.

A common failure is an enclosure URL that requires authentication. If your audio files sit behind a login or a signed URL that expires, directories can't fetch them and the episode appears broken. Public, non-expiring URLs are the requirement. Another frequent problem is mixed protocols: an HTTPS feed containing HTTP audio URLs triggers warnings in some apps and blocks playback in others.

Apple also enforces content ratings. The itunes:explicit tag must be present, and shows flagged as explicit face additional review. Missing the tag delays approval. For shows with clean content, set it explicitly to false rather than omitting it.

If a feed validates but episodes don't appear, the usual culprit is the being in the future or malformed. Some hosts schedule episodes with future dates, and directories won't surface them until that time passes β€” which is the intended behavior, but confusing if you didn't set the schedule yourself.

Bandwidth, File Size, and the Numbers Behind Delivery

The feed points to audio, and audio costs bandwidth. Understanding the arithmetic helps you choose a host tier and an encoding bitrate without guessing.

A 45-minute episode encoded at 128 kbps mono is about 43 MB. At 1,000 downloads, that's roughly 43 GB of transfer for one episode. Publish weekly and you're at roughly 172 GB a month from that single episode's first-run downloads alone, before back-catalog plays. Podcast hosts price plans around these volumes, and the tiers change often enough that you should read the current plan page rather than trust a number from a blog post.

Bitrate is the lever. Dropping from 128 kbps to 96 kbps cuts file size by about 25% with modest quality loss for spoken-word audio. Stereo doubles the data for content that's usually mono anyway β€” a common waste in interview shows. Setting your recorder or export to mono at 96–128 kbps is the standard recommendation for voice.

The feed file itself is tiny, usually a few hundred kilobytes even for shows with hundreds of episodes. The bandwidth cost lives entirely in the audio, which is why hosts meter downloads rather than feed requests. If your host advertises "unlimited storage, metered downloads," the download meter is the number that matters.

How to Get Your Feed and Submit It

Getting a feed live takes four steps if you're using a host, and the order matters because directories won't accept a feed that fails validation.

1: Upload your first episode to your podcast host and fill in the show title, description, author, and cover art at 3000Γ—3000 pixels in RGB. Save the episode as a draft rather than publishing it, so the feed exists with at least one item but isn't live yet. 2: Copy the feed URL from your host's dashboard β€” usually labeled "RSS feed" or "feed URL" under distribution or settings. 3: Paste the URL into a feed validator such as Podba.se or Apple's own validation in Podcasts Connect. Fix any flagged tag before proceeding; missing artwork or a malformed date will block Apple submission. 4: Submit the feed to Apple Podcasts via Podcasts Connect, to Spotify via Spotify for Podcasters, and to any other directory you want. Publish the episode after submission succeeds.

Failure handling: if Apple rejects the feed, the error message names the tag. If Spotify accepts but episodes don't appear, check the pubDate and the enclosure URL accessibility. If the validator passes but a directory still refuses, compare your feed against Apple's current podcasting requirements page, since required tags have changed over the years.

FAQ

Can I have a podcast without an RSS feed?

Yes, but only on platforms that host the audio themselves. Spotify for Podcasters and YouTube let you publish audio or video without exposing a feed, and the show stays inside that platform. You lose distribution to Apple Podcasts and other apps that rely on feeds.

Does the RSS feed contain my audio files?

No. The feed contains links to your audio, not the files. Your host stores the audio and serves it from its servers, and the feed's enclosure tag points to that location. Deleting the audio from your host breaks the link even though the feed entry may linger.

Why did my new episode not show up in Apple Podcasts?

Apple checks feeds on a polling schedule, so a delay of hours to a day is normal. If it's longer, verify the pubDate isn't set in the future and that the enclosure URL returns the audio file in a browser. A malformed date or a private audio URL are the most common causes.

What happens to my feed if I switch podcast hosts?

The old feed URL stops working unless you set a 301 redirect from it to the new feed. Without the redirect, directories lose track of the show and subscribers polling the old address get errors. Most paid hosts support redirects; confirm before you migrate.

How much does podcast hosting cost for the bandwidth I need?

Hosting plans are priced around monthly download volume, and rates change, so check each provider's current pricing page. As a planning figure, a weekly 45-minute show at 128 kbps mono generates roughly 43 GB per 1,000 downloads, so a plan covering a few thousand downloads a month is the usual starting point.

Is an RSS feed the same as a podcast?

No. The podcast is the show β€” the audio, branding, and episodes. The RSS feed is the technical document that tells apps where to find that show. A podcast can exist without a feed on platform-only services, but a feed can't exist without audio to point to.

Can I edit my RSS feed directly?

You can if you self-host the XML, but most creators edit metadata through their host's dashboard, which regenerates the feed. Hand-editing risks breaking required tags, and hosts may overwrite manual changes on the next publish. Use the dashboard fields and validate after any change.