← All articles

Podcast medium tag: identify the feed's content type

Explore this article with AI

Open a source-aware analysis with this article as the primary source.

ChatGPTClaudePerplexityGeminiGrokGoogle AI
Follow Podder on Google

Add us to your Preferred Sources.

The podcast medium tag identifies what kind of content an RSS feed contains. Written as <podcast:medium>, it helps a supporting app distinguish a podcast from music, video, film, an audiobook, written publishing, a course, or a list of remote items. If the tag is absent, the specification says podcast is assumed.

Medium describes the content's form. Category metadata describes its subject. A history podcast and a history newsletter may cover the same topic, but their medium values can tell an app to present them differently.

How the podcast medium tag works

The official medium tag specification places one <podcast:medium> element under the RSS <channel>. Its node value is one of the names maintained by the Podcast Namespace community.

A standard podcast feed can state its medium explicitly:

<channel>
  <title>Example show</title>
  <podcast:medium>podcast</podcast:medium>
</channel>

The document gives app behavior as the reason for the element. For example, an app reading music may choose playback and audio settings suited to music rather than spoken word. The specification provides the content label, while each app decides whether and how to use it.

The setting applies to the whole channel. Episode-level details still belong inside each <item>, including structured metadata such as the podcast episode tag.

Defined medium values

The specification lists these standard values:

ValueFeed content
`podcast`A podcast show and the default when the tag is missing
`music`An album-like feed with songs as items
`video`A feed intended for a visual, channel-style experience
`film`Cinematic video, with one item per feed
`audiobook`A book as one item or as chapter items
`newsletter`Selected written articles, which may include spoken audio enclosures
`blog`Informally written articles in a traditional blog style
`publisher`A feed that points to other feeds owned by a publisher
`course`Training material whose items are sessions or chapters

Choose the value that describes what the feed contains, not the value you hope an app will promote. A video recording of every podcast episode may support a video feed when the feed itself is built for that visual experience. A conventional podcast feed does not become video merely because some episodes have external video links. The podcast content link tag covers labeled destinations outside an app without redefining the entire feed.

List mediums and mixed feeds

Each standard medium can have a list counterpart formed by adding an uppercase L. For example, podcastL, musicL, and audiobookL describe lists of those content types.

A list feed is designed around <podcast:remoteItem> references. The specification says it should not be expected to contain regular <item> elements, <podcast:liveItem> elements, or future item types. The remote items point to feeds or items elsewhere using Podcast Namespace identifiers.

The dedicated mixed value describes a list whose remote items point to different medium types. One mixed list could reference music, podcast, and audiobook content. Use it for a collection that genuinely crosses medium types rather than as a fallback when the channel owner has not decided how to classify a feed.

<channel>
  <title>Music collection</title>
  <podcast:medium>musicL</podcast:medium>
  <podcast:remoteItem
    feedGuid="example-feed-guid"
    itemGuid="example-item-guid"
    medium="music"
  />
</channel>

What the medium value changes

The value gives apps structured information they can use in interface and playback decisions. It does not require a particular layout, equalizer setting, playback speed, or discovery position. App support and presentation can differ.

It also does not replace the feed fields needed to deliver media or identify episodes. A medium value of podcast does not create enclosures, titles, GUIDs, or publication dates. A course value does not establish a curriculum.

Audience reporting remains separate. Changing a medium value does not convert downloads from one reporting definition to another. Use a consistent measurement process such as the one in our guide to tracking podcast analytics when you compare delivery over time.

How to choose and verify a value

Start with the feed's actual structure. If it contains ordinary spoken-word podcast episodes, use podcast or rely on the documented default. If it represents an album, book, film, course, or written publication, compare that structure with the definitions in the specification.

For list variants, confirm that the channel contains remote-item references rather than ordinary episode items. Preserve the uppercase L suffix exactly. After publishing, open the raw RSS and verify that the tag appears once under <channel> with the intended value. Then inspect the feed in the apps your audience uses, without assuming every app exposes the medium in its interface.

For delivery analysis after the metadata is live, Podder Analytics gives you a separate place to review podcast performance.

FAQ

What is the podcast medium tag?

It is a channel-level Podcast Namespace element that identifies the type of content contained in a feed, such as a podcast, music album, video channel, or audiobook.

What happens if podcast:medium is missing?

The Podcast Namespace specification says that podcast is the assumed medium when the channel has no medium tag.

What does the L suffix mean in a medium value?

An L suffix marks a list variant, such as musicL. A list feed is intended to contain podcast:remoteItem references rather than regular items or live items.

Put it into practice

See who's actually listening.

Podder gives you audience demographics, per-episode analytics, and chart tracking. The Chartable alternative that goes deeper.

Start free