Podcasting · RSS preflight

Podcast RSS feed validator.

Paste your feed XML or choose the file. Get well-formedness errors with line numbers, then the RSS 2.0 and Apple Podcasts checks that most often fail a submission.

Rules read from Apple and the RSS 2.0 spec · 30 September 2026Your XML never leaves the browser

How to validate a podcast feed

  1. Upload your .xml feed file or paste the XML.
  2. Press Check feed.
  3. Fix the XML errors listed with line numbers first, then the RSS and Apple Podcasts findings.

What gets checked

First comes XML well-formedness with line numbers: mismatched or unclosed tags, a bare ampersand, entities that XML does not define such as the HTML entity for a curly quote, unquoted attributes and undeclared namespace prefixes. Then RSS 2.0: an rss element of version 2.0 with one channel that has a title, link and description, and enclosures that each have a url, a length and a type.

Apple Podcasts requires the iTunes namespace, a show title, a description of up to 4000 bytes, an image, a language, a category and an explicit flag, with further checks on episodes such as unique GUIDs, valid dates and artwork. The validator does not fetch feed URLs or test whether your audio files exist, so it checks the file you give it, not the live hosting.

Read on your device

The validator runs in your browser, inside an isolated frame on this page that has no network access. Your file is read and written back by your own device, so it is not uploaded to TNAADO or anyone else, and nothing is stored. The advertising on this page sits outside the frame and cannot see what you choose. Unpublished feeds and show details are not uploaded.

What this checks

What it cannot check from pasted XML

Whether the feed URL is public, whether your host answers HTTP HEAD and byte-range requests, whether each enclosure really returns the file and matches its stated length, the artwork’s pixel size and colour space, the exact spelling of your category against Apple’s list, and whether the language is a real ISO 639 code (only its shape is tested). These are listed under the result as manual follow-ups. A clean result means the XML matches the rules above, not that Apple will accept the show: Apple also reviews content against its guidelines.

Sources

Checked 30 September 2026: Apple Podcasts for Creators: Podcast RSS feed requirements, Validate your podcast, A Podcaster’s Guide to RSS (required, recommended and situational tags), the RSS 2.0 specification and RFC 2822 section 3.3.

What a podcast RSS feed is, and why it gets rejected

A podcast is not a file you upload to Apple, Spotify or any other directory. It is an RSS feed, an XML document on your host’s server that lists the show and each episode, and directories read it on a schedule. That is why a single missing tag, an unescaped ampersand or a mismatched closing tag can stop a show from validating. Apple’s own guidance says validation errors can result from connection issues, incompatible or unsupported media files, or missing required tags. This validator tackles the last category, and the XML-syntax problems that cause it, without contacting your server.

The checks, in the order problems usually appear

  1. Well-formed XML. Every opening tag needs a closing tag, attributes need quotes, and a bare & must be written &. HTML entities such as ’ or © are not defined in XML and will break parsing; Apple’s guide shows numeric forms like © instead. The parser reports the line number so you can jump straight to the fault.
  2. RSS 2.0 structure. The root is <rss version="2.0"> containing one <channel> with a title, link and description, as the RSS 2.0 specification requires.
  3. Apple Podcasts tags. The itunes namespace must be declared, and the channel needs a title, description, itunes:image, language, itunes:category and itunes:explicit. At least one episode must exist.
  4. Episodes. Each item needs a title, an <enclosure> with url, length and type, and a globally unique identifier (GUID) that never changes. Apple will ignore duplicate enclosure URLs, so the tool reports repeats.
  5. Dates. pubDate must follow RFC 2822: for example Mon, 05 Oct 2026 08:00:00 -0400. The tool warns when the weekday does not match the date, a mistake that is easy to make when copying an old item.
  6. Case. XML is case-sensitive, so <itunes:Image> and <pubdate> are different tags from the correct lower-case or camelCase forms.

A worked example

Suppose you paste a feed with an episode whose title reads Q&A with Dana. The parser stops at the ampersand and reports the line, because XML needs Q&amp;A. After fixing that, the tool might warn that pubDate says “Tue, 05 Oct 2026” while 5 October 2026 is a Monday. Correct the weekday or the date, and run the check again. Finally, if two episodes share the same enclosure URL because you duplicated an item as a template, the duplicate check flags the second one; give each item its own file and its own GUID.

GUIDs: the field people regret changing

A GUID identifies an episode to every app that has already downloaded it. Apple requires it to be globally unique and unchanging. If you migrate hosts and your new feed generates new GUIDs, apps can treat every back-catalogue episode as new. The validator tests uniqueness within the pasted file (case-sensitive), but it cannot know whether the GUID matches the one you published last year, so compare a few by hand before switching feeds.

Checks that need your server, not just your XML

A clean result does not prove that the feed is reachable. Apple’s requirements and its validation page both call for hosting the feed, episodes and artwork on publicly addressable servers with HTTP HEAD and byte-range requests enabled; a server that does not support byte-range requests is a listed cause of failed validation. You also need to confirm manually that each enclosure returns the file, that its stated length matches the real byte count, that artwork meets Apple’s size rules (try the podcast cover art checker), and that your category spelling matches Apple’s list. The tool lists these manual steps beneath the result so they are not forgotten.

Limits and privacy

This tool does not fetch feed URLs, which is deliberate: it only reads the text you paste or the file you choose, locally in your browser, and nothing is logged. It does not check chapters, transcripts or the Podcasting 2.0 namespace, and passing does not guarantee approval because Apple also reviews content against its guidelines. If you add chapters, build the file with the chapters JSON generator, and estimate the enclosure length with the file-size calculator when you only have bitrate and runtime. For an external second opinion, Apple’s validation page names Cast Feed Validator and Podbase Podcast Validator as tools that may give more detailed insights.

Frequently asked questions

What is a podcast RSS feed?

It is an XML document hosted on your podcast host’s server that lists your show details and every episode with a link to its audio file. Directories such as Apple Podcasts read this feed, so correcting the feed is how you correct what listeners see.

How do I check whether my podcast RSS feed is valid?

Paste the XML or choose the file, press Check, and fix any well-formedness errors first, since the line numbers point to the exact tag. Then clear the required Apple and RSS 2.0 items, and finish by confirming hosting details that a pasted file cannot prove.

Which tags does Apple Podcasts require?

This tool checks the itunes namespace, show title, description, image, language, category and explicit flag, plus at least one episode with a title, enclosure and GUID. Apple’s current RSS requirements page is the authority, so confirm against it before submitting.

Why does my feed fail on an ampersand or an apostrophe?

XML only defines a handful of entities, so a bare & or an HTML entity such as &rsquo; makes the document invalid. Write & as &amp; and use numeric references or plain UTF-8 characters for other symbols.

What date format does pubDate need?

It needs RFC 2822: a weekday, day, month name, four-digit year, 24-hour time and a time zone, for example Mon, 05 Oct 2026 08:00:00 -0400. A weekday that does not match the date is flagged as a warning because players may display it wrongly.

Can two episodes share the same GUID or enclosure URL?

No. Each GUID must be unique and permanent, and Apple Podcasts ignores duplicate enclosure URLs. If you cloned an old item to start a new one, change the GUID, the enclosure URL and the title.

Does this tool fetch my feed URL or send my XML anywhere?

No. It only reads text you paste or a file you choose, and everything runs in your browser. Because it never contacts your host, it cannot test HTTP HEAD, byte-range support or whether your audio files actually load.

Sources and retrieval dates

Format check only

This tool checks the pasted XML against published rules. It does not contact your host or Apple, and passing does not guarantee approval. Nothing you paste is transmitted, stored or logged.

Advertisement
Advertisement