Blog

Your Podcast App Has No “Live” Button. The RSS Feed Has a Tag.

November 6, 2026  ·  Tablingo

A podcast is a file, not a channel. Apple Podcasts and Spotify have no “on air” state at all — and the live format that does exist is a tag most apps never read.

Type “live podcast” into a search box and you get a page about bitrates. OBS settings, multistreaming, where to put the cameras, how to keep the room's echo out of the recording. All of it is useful, and none of it answers what you asked, which was: the show I listen to is recording right now, so where do I hear it?

The reason for that gap is not laziness on anyone's part. It is that the two halves of the phrase belong to different people, and only one half has a documented answer.

The word is doing two jobs

For a host, “live” is a production format: no editing, an audience that can talk back, a stream that goes out once. Every guide you will find is written for that meaning, which is why they all end in a streaming setup.

For a listener, “live” is an address. It means the thing is happening now, and there should be a place to be when it happens. That meaning has almost nothing written about it, and the reason is uncomfortable: in the app you already use, the address does not exist.

The platforms never had the state

A podcast is distributed as a file. An RSS item with an enclosure, sitting in a feed, waiting to be downloaded. There is no field in that structure for “currently broadcasting”, because the whole point of the format was that there is nothing to wait for — the file is already there.

So Apple Podcasts and Spotify, the two apps most people mean when they say “my podcast app”, have subscriptions, downloads, queues and playback speeds. They do not have an on-air state. If a show you follow goes live tonight, nothing inside those apps will change at any point.

This is not for lack of trying. Spotify bought Betty Labs in 2021, launched the app as Greenroom, renamed it Spotify Live, moved it into the main Spotify app — and shut the standalone app down on 30 April 2023. What survived is a narrower thing: listening parties for artists. The largest podcast platform in the world spent two years trying to put live audio inside a listening app and then walked away from it. That is worth knowing before assuming the missing button is an oversight.

The standard does have a tag

There is one place where live podcasting genuinely exists, and it is not a platform. It is a tag.

Podcasting 2.0 — the independent extension to RSS that adds chapters, transcripts, funding links and so on — includes a live item. A hosting provider that supports it lets the creator schedule a broadcast, then flip it to live when they go on air, then ended when they stop. Apps that read the tag show the upcoming episode, send a notification when it starts, and offer a listen-live entry inside the app.

The catch is entirely in that last sentence. The apps reading it are the independent ones: Podverse, Fountain, Podcast Guru, TrueFans, AntennaPod. Apple Podcasts does not read this tag — it implemented transcripts its own way — and Spotify does not use the Podcasting 2.0 namespace at all. Most of the apps that do read it play the audio track only.

So the format that makes a live podcast discoverable exists, is implemented, and is almost invisible. Not because it failed, but because the apps holding the address book never opened it.

Where you lookLive shows appearCaptions
Apple Podcasts, SpotifyNoNo
Podverse, Fountain, GuruYes, if taggedNot specified
YouTube, Twitch, own siteYesDepends

Not specified is the honest entry in the middle row. The tag says where the audio is and whether it is on air. It says nothing about text, so whether you get a single line of it during the broadcast is decided by each app separately, and none of them promises anything.

So the broadcast happens somewhere else

Follow the show instead of the format and you end up on a different page. The live version happens on YouTube Live, on Twitch, on the show's own site, sometimes inside a StreamYard or Riverside room that is embedded on a landing page. That is where the hosts are, so that is where the guides are written, which is why the search results you got were all about production.

None of it is wrong. It just means the live episode has two addresses, and only one of them is in your subscription list — the one that does not work.

The text layer is thinner out there

And the place where the broadcast actually happens is the place where captions are weakest. Read the platform documentation together and the pattern is hard to miss.

YouTube's automatic captions for live streams are English only, require normal latency, are enabled per stream rather than per channel, and are still being rolled out. The same help page lists the conditions under which those captions drop words — unclear audio, overlapping speakers, several languages at once. That is a description of a live podcast, not an edge case.

Twitch does not generate captions for live video at all. A broadcaster can push embedded captions through their encoder, and the overwhelming majority do not, so the CC button is either absent or does nothing on the streams most people watch.

A show's own player usually has less than either. It is a page with an audio element on it.

Where the show isWho supplies textDuring the broadcast
YouTube LiveThe platformEnglish, if enabled
TwitchThe broadcasterUsually none
The show's own siteNobodyNone
A tag-aware podcast appEach appNot guaranteed

What the replay actually keeps

The natural plan is to wait. Watch it later, read the transcript then. Three facts make that plan weaker than it sounds.

The first is that live captions are not archived. YouTube says plainly that automatic captions shown during a broadcast do not stay on the video; the replay gets a separate track generated afterwards, and it can differ from what viewers saw live.

The second is that the edited version is not the broadcast. Live shows run long, repeat themselves, take unplanned questions, lose a minute to a technical problem. The episode that lands in your feed has had all of that removed — which is the point of editing, and also the reason the thing you missed is not sitting there waiting.

The third is language. A replay with a transcript is still one transcript, generated in one language, for one episode. If the reason you wanted captions was that you do not speak the language the show is in, the replay has the same problem the broadcast had, only later.

Where we sit

Our extension reads the audio of the tab you are already playing and puts the original line above the translation. It does not ask the page for a subtitle track, because on live audio there usually is not one — the page has sound, and that is all it has.

Which makes live a normal case for us rather than a special one. YouTube Live, Twitch, a StreamYard room, a show's own player: the tab is playing, so the tab can be read. Nothing needs to be switched on by the broadcaster, and no tag needs to be supported by an app.

The boundary is worth stating as plainly. All of this happens inside a browser tab, so a live show playing in a desktop or phone app is outside it — including the live audio inside a tag-aware podcast app, which is exactly where the format works best and where we cannot reach. The two halves of this problem are being solved in different places, by different people, for different reasons. Ours is the browser side.

Two checks

  1. Search the show's name inside your podcast app. If there is no upcoming or live entry for a broadcast the show has announced, your app does not read the tag — and no amount of refreshing will produce one.
  2. Open the live page and press CC. If the button is missing or greyed out, that stream has no text layer, and any tool that reads subtitle tracks has nothing to read. That tells you which kind of tool you need before you install anything.

Neither check requires trusting a vendor, including us.

What you actually wanted

The request underneath all of this is small: I want the thing I subscribe to and the thing that is happening now to be in the same place. Today they are not, and the gap has been filled from both sides by people who mostly did not notice the other side existed — production guides on one side, caption tools on the other.

That is not a ranking of anyone's work. It is a map, and maps have edges. The useful part is knowing which side of the edge you are standing on before the show starts.

If you want to try ours, it's called Tablingo — a browser extension that reads the tab you are already playing and puts the original line above the translation. The on-demand podcast case is here, the live-stream case here, and the episode that changes language halfway through is here.