Podcast Technology: RSS, Distribution & Players

Podcasting may be the last frontier of open standards: no platform algorithm, no proprietary format — an RSS file plus a set of audio URLs is the whole stack. That “crudeness” is precisely its vitality: the content belongs to the creator forever, and platforms are merely readers. The full technical picture, enough for any independent podcaster to start.

The Stack: Beautifully Simple

[RSS feed XML]  ← describes the show and episodes (title/cover/duration/audio URL)
      ↓ crawl
[Directories]   ← Apple Podcasts / Spotify / regional apps…
      ↓ play
[Audio URLs]    ← your hosted mp3/m4a

The core mechanism is the RSS enclosure tag: per episode — <enclosure url="https://...mp3" length="bytes" type="audio/mpeg"/>. Directories crawl your feed, follow the enclosure to the audio, listeners download and play. You upload nothing “to the platform”; the platform is a reader.

The Anatomy of a Feed

<channel>
  <title>Show name</title>
  <itunes:image href="cover URL"/>
  <item>
    <title>Episode 42: the title</title>
    <pubDate>Mon, 24 Aug 2026 00:00:00 +0000</pubDate>
    <enclosure url="https://cdn.example.com/ep42.mp3" length="52428800" type="audio/mpeg"/>
    <itunes:duration>3600</itunes:duration>
  </item>
</channel>

Three classic mistakes: length must be the exact byte size (some directories reject mismatches); pubDate is strictly RFC 822; changing the feed address requires an iTunes <new-feed-url> redirect or every subscription on earth is lost.

Format and Bitrate

Podcasts are speech; the bitrate discipline is in the audio bitrate guide: 64–96 kbps AAC or MP3 — an hour-long episode at 30–45MB, plenty for voice. MP3 is the most bulletproof (indifferently universal); AAC (m4a) is slightly more efficient. Not 320k — triple the update traffic for inaudible gains.

How Distribution Actually Works

  • Apple Podcasts: the “iTunes directory” of podcasting — submit the feed once, reviewed, visible globally; the de-facto registration source;
  • Spotify: crawls feeds but runs its own directory (submit in the dashboard);
  • Regional apps: the same crawl model with their own submission doors;
  • Your website: the ground you fully own — and the place for a deep experience.

Hosting: audio on high-volume object storage + CDN (nearly free at podcast scale); the feed can be statically generated (it’s XML file) or a podcast host handles everything for a monthly fee.

Web Playback: The Underrated Ground

In-app players are uniform; your site can offer the deep experience — exactly where ZWPlayer’s music mode shines:

  • Music mode: vinyl cover + LRC word-synced lyrics — turn an interview into a follow-along transcript experience;
  • Chapter navigation: split long episodes by topic with chapters so listeners jump straight to what they care about;
  • Full-text search over transcripts: pair with subtitle search — search a sentence, land on that minute; a killer for knowledge shows;
  • Speed and A-B loop: heavy-listener staples (power features).

One-line embed:

new ZWPlayer({
  playerElm: 'player',
  url: '/audio/ep42.m4a',
  mode: 'music',
  lyrics: '/lyrics/ep42.lrc',   // transcript converted to LRC
});

The Independent Podcaster’s Minimum Checklist

  1. Record (any USB mic; room treatment beats gear);
  2. Edit and export: AAC 96k mono (mono halves speech size again);
  3. Upload to object storage + CDN; statically generate the RSS feed;
  4. Submit to Apple Podcasts / Spotify / regional directories;
  5. Embed ZWPlayer on the site with chapters and transcript.

FAQ

Switching hosts — do subscribers follow? Yes — leave <itunes:new-feed-url> on the old feed pointing to the new address; the world migrates automatically.

Video podcasts? Point the enclosure at a video file (type="video/mp4"); on the web, a full player brings subtitles, chapters, and interaction along.

Listening analytics? Each directory has its own dashboard; your CDN logs hold the true download counts (more honest than platform stats).