RSS Namespace Extension for Podcast Transcripts

Transcripts for podcasts provide a lot of real-world benefits. They improve accessibility for the hearing impaired, improve search engine optimization, and provide the opportunity to read along while listening. Many podcasters provide transcripts for each episode. This namespace makes those transcripts available in various formats as part of the standard podcast RSS feed.

Episode Tag

Parent Tag: <item>

Episode Tag: <podcast:transcript>

Usage: Signifies that a transcript is available and provides a location and type.

Details and Examples

The <podcast:transcript> tag has two attributes: URL, and type:


      <podcast:transcript url="" type="application/srt" />
      <podcast:transcript url="" type="text/html" />
      <podcast:transcript url="" type="application/json" />

* All available transcript formats should be included.


RSS Feed with Transcript Tags
SRT Transcript
JSON Transcript
HTML Transcript

SRT Format and Example Code

The SRT format was designed for video captions but provides a suitable solution for podcast transcripts. The SRT format contains medium-fidelity timestamps and are a popular export option from transcription services. SRT transcripts used for podcasts should adhere to the following specifications.

Max number of lines: 2
Max characters per line: 32
Speaker names (optional): Start a new card when the speaker changes. Include the speaker's name, followed by a colon.

00:00:00,000 --> 00:00:02,760
Sarah: In today's episode,
you'll learn whether or not you

00:00:02,760 --> 00:00:06,090
should have a podcast trailer.
And if so, what should you

00:00:06,090 --> 00:00:11,610
include in one? Welcome to
Podcasting Q&A, where you learn

00:00:11,610 --> 00:00:15,750
the best tips and strategies to
launch, grow and monetize your

00:00:15,750 --> 00:00:18,630
podcast. This week's question
comes from Gillian.

00:00:19,080 --> 00:00:21,450
Gillian: Hi Buzzsprout, Gillian
here from breaking through

00:00:21,450 --> 00:00:25,350
careers podcast. My question is,
do we need a podcast trailer?
JSON Format and Example Code

The JSON representation is a flexible format that accomodates various degrees of fidelity in a concise way. This format for podcast transcripts should adhere to the following specifications.

Elements included in this representation:
<version>: The version of JSON transcript specification
<segments>: An array of dialogue elements (segments)
<speaker>: Speaker
<start_time>: Start time for the segment
<end_time>: End time for the segment (if available)
<body>: Dialogue content

  "version": "1.0.0",
  "segments": [
      "speaker": "Darth Vader",
      "startTime": 0.5,
      "endTime": 0.75,
      "body": "I"
      "speaker": "Darth Vader",
      "startTime": 1,
      "endTime": 1.25,
      "body": "am"
      "speaker": "Darth Vader",
      "startTime": 1.5,
      "endTime": 2.0,
      "body": "your"
      "speaker": "Darth Vader",
      "startTime": 2.25,
      "endTime": 2.50,
      "body": "father."
      "speaker": "Luke",
      "startTime": 2.75,
      "endTime": 3.0,
      "body": "Nooooo"

HTML Format and Example Code

The HTML transcript format provides a solution when a transcript is available but no or limited timecode data is available. HTML transcript files are considered low-fidelity and are designed to serve as an accessibility aid and provide searchable episode content. The HTML format used for podcast transcripts should adhere to the following specifications.

HTML tags used:
<cite>: Name of the speaker (if available)
<time>: Start time of monologue (if available)
<p>: Content of monologue

<p>We have an update planned where we would like to give the ability to upload an artwork file for these videos</p>
<cite>Alban :</cite>
<p>You're triggering Tom right now with a hey, here's a cool feature.</p>