Podcast live item tag: declaring a live stream
Open a source-aware analysis with this article as the primary source.
Add us to your Preferred Sources.

The podcast live item tag is channel-level RSS metadata for delivering a live audio or video stream to supporting podcast apps. It is written as <podcast:liveItem>. The tag resembles a standard episode item but adds a required event status and intended start time, while stream sources tell an app what to play and a required content link gives the listener an external fallback.
How the podcast live item tag works
The official Podcast Namespace liveItem specification allows multiple live items under <channel>. Each live item can contain the tags allowed under a normal RSS <item>, including a title, GUID, description, people, enclosures, and links, although app support for those child tags can vary in a live context.
Three attributes describe the event:
| Attribute | Status | Meaning |
|---|---|---|
| `status` | Required | `pending`, `live`, or `ended` |
| `start` | Required | Intended start time as an ISO 8601 timestamp |
| `end` | Recommended | Intended end time as an ISO 8601 timestamp |
The start and end times are approximations because a real broadcast may shift, but supporting apps should use status="live" as the canonical signal that the stream has started.
The stream, fallback, and GUID
The specification highly encourages <podcast:alternateEnclosure>. It provides explicit stream transport and codec details. The specification also calls for a standard <enclosure> as a fallback for apps that have not implemented alternate enclosures.
Test the exact protocol and codec. Format choice affects how many apps can play the stream, so feed validity alone does not mean the stream will play.
A <podcast:contentLink> is required. It points to an HTML player or another external stream destination that listeners can open when their app cannot play the feed source. The podcast content link tag explains its required href and listener-facing label.
<podcast:liveItem
status="pending"
start="2026-11-12T18:00:00Z"
end="2026-11-12T19:00:00Z">
<title>Listener call-in show</title>
<guid>call-in-2026-11-12</guid>
<enclosure
url="https://stream.example.com/call-in.mp3"
type="audio/mpeg"
length="312" />
<podcast:contentLink href="https://example.com/live">
Listen on the web
</podcast:contentLink>
</podcast:liveItem>The GUID identifies the stream in the same way it identifies a regular item. If the GUID changes, podcast apps must consider the live item a new stream, so keep it stable while the same event moves from pending to live to ended.
Moving through pending, live, and ended
Publish pending while the event is scheduled but has not started. At broadcast time, change the value to live, then set it to ended when the stream finishes. Update the source feed rather than relying on an app-side change. Apps retrieve the state from RSS.
The specification says a host should send a Podping notification when the stream starts so apps can learn about the update. That notification complements the feed change, but it does not replace the status attribute or fix stale XML.
A live event may also name a dedicated conversation room. For that event, the podcast chat tag can sit under <podcast:liveItem> and override channel-level chat information. Test the room separately from stream playback.
What liveItem does not guarantee
Publishing a valid live item shows that the feed declares an event and its sources, but playback still depends on app support, stream availability, transport, codec, network conditions, and any access rules at the fallback page. Some accepted child tags may receive no useful treatment from a particular app.
Scheduled timestamps cannot prove that audio or video is flowing. Check the stream endpoint itself, then check the current status in the public feed, and finally inspect apps that matter to your audience.
Live-item presence also does not create listening measurement by itself. Use separate reporting for feed delivery, player activity, and visits to an external content link, following the podcast analytics guide to keep measurement sources labeled instead of folding unlike events into one total.
How to publish and test a live item
Build the event under <channel> with a stable GUID, clear title, required attributes, playable enclosure, and content link. Add an alternate enclosure when your feed generator supports it, then set the status to pending before announcing the event.
Open the raw RSS. Check the parent, timestamp format, status value, GUID, source URLs, MIME type, and content-link destination. Test the enclosure in the apps you expect listeners to use, then open the external page in a signed-out browser and confirm that the label describes the page listeners reach.
At start time, update the status to live, send the expected feed notification through your host, and verify the public XML changed. After the event, mark it ended. Then decide whether the same URL should keep serving a replay or direct visitors to an archive.
For delivery context around live and recorded releases, start with Podder Analytics while keeping stream-health checks in your broadcast tools.
FAQ
What is the podcast live item tag?
It is a channel-level Podcast Namespace element that describes a live audio or video stream with item-style metadata and live-event attributes.
Which podcast:liveItem attributes are required?
Status and start are required. Status must be pending, live, or ended; start is an ISO 8601 timestamp, and end is recommended.
Why does a live item need podcast:contentLink?
The specification requires a contentLink so listeners have an external fallback when their podcast app cannot play the stream directly.
See who's actually listening.
Podder gives you audience demographics, per-episode analytics, and chart tracking. The Chartable alternative that goes deeper.
Start free