Why must the enclosure length match the audio file size byte for byte?

Platforms like Apple Podcasts use byte-exact lengths to verify media integrity and handle HTTP byte-range streaming requests without fetching entire files.

Are audio files or RSS feeds uploaded to an external server?

No. All XML parsing, audio probing, and metadata cross-checks occur entirely within your browser.

What audio requirements does Apple Podcasts enforce?

It requires MP3 or AAC (in MP3 or M4A containers), a 44.1 kHz or 48 kHz sample rate, and a minimum bitrate of 64 kbps.

Why are HTML-named entities like ’ flagged as errors?

Strict XML parsers only recognize standard XML entities like ' and ". Named HTML entities cause feed parsing crashes.

Can I check audio files without uploading an RSS feed XML?

Yes. You can supply audio files alone to validate container health, sample rates, and bitrates against your target platform profile.

Elysia Tools

Navigation

Media

Podcast RSS Enclosure Checker

Validate podcast episode audio against hosting expectations and cross-check it with your RSS feed: enclosure URL / length / type attributes, itunes:duration, GUID uniqueness, RFC 2822 dates, platform codecs and bitrates — byte-exact enclosure lengths included.

Details

What this tool helps you do

A podcast episode is a contract between three things: the audio file, the RSS that points at it, and the platform that fetches both. This checker audits all three. The feed side follows RSS 2.0 and the Apple Podcasts requirements: every episode needs a unique with all three required attributes — url (http/https), length in bytes, and a MIME type — plus a globally unique that never changes; Apple ignores duplicate enclosure URLs, so duplicated media URLs are flagged. Dates must parse as RFC 2822, only '/" entity escapes are accepted (HTML-named ones like ’ break strict XML parsers), filenames should be ASCII, and should agree with the audio. The audio side checks each file against the target platform profile (Apple Podcasts: MP3/AAC in MP3/M4A at 44.1 or 48 kHz, at least 64 kbps; Spotify: MP3/M4A/OGG/OPUS/FLAC, at least 96 kbps; generic RSS 2.0: container sanity only). When you provide both the feed and the audio, the two are cross-validated: enclosure length must equal the real file size byte for byte, the declared MIME type must match what the container actually is, and must track the measured duration. Files and feeds are only read; nothing is uploaded or fetched.

Execution

Run this tool

Fill in the form, run the tool, and review the result in one place.

Samples

Podcast RSS Enclosure Checker

What this tool helps you do

Run this tool

Examples that match this tool

Continue with connected tools and hubs

Learn when to use this tool, what it supports, and how real users apply it.

Key facts

Overview

When to use

How it works

Use cases

Examples

1. Pre-Release Feed and MP3 Cross-Validation

2. Diagnosing Feed Ingestion Errors for Spotify

FAQ

XML Viewer Samples

Nginx Log Parser Samples

Android Serialization Java Samples

Android Serialization Kotlin Samples

Genre Classifier AI

Accessibility Checker

Data URI Generator

Podcast Chapter Marker Builder

Podcast Episode Audio and RSS Publication Preflight