Audio & Podcast Publishing · THE NO-PANIC PLAN
Prepare a Podcast Episode for Apple Podcasts RSS
An RSS podcast release depends on a clean audio master, a format accepted by your host and destination, correct episode metadata, and a reachable RSS enclosure. Apple?s requirements distinguish episodes distributed through RSS from subscriber audio uploaded directly through Apple Podcasts Connect. This workflow covers the RSS route only. Compressing or normalizing audio can change sound quality, so preserve the master and listen to the final file before publishing. Nirmion?s audio tools can help with bounded technical changes; they do not approve the episode, validate all feed fields, or submit it to Apple.
MISSION Prepare, encode, validate, and publish a podcast episode through an RSS host for Apple Podcasts using current technical, metadata, and rights requirements.
Check Apple Podcasts audio and RSS requirements before uploading the episodeTHE REAL-WORLD BIT
What happens outside this browser tab?
Confirm rights and the RSS distribution path; finalize and preserve a high-quality master; review loudness and true peak; encode only if needed for the host and Apple's supported formats; listen to the delivered file; publish it through the host with unique episode identity, metadata, and an accessible enclosure; test and validate the RSS feed; submit/confirm the show and monitor errors or review status.
YOUR CHECKLIST, WITH FEWER DRAMATIC SIGHES
One step at a time.
Follow the order below. If a step names a Nirmion tool, its link is right there with it.
- 01
Confirm rights and choose the RSS delivery route
Identify the show, episode, hosting provider, target release time, and whether the episode is a public RSS release or subscriber audio. This workflow covers public distribution through a host-generated or self-managed RSS feed; Apple Podcasts Connect subscriber-audio upload has a separate file workflow and specifications. Before editing, confirm you own or have permission for every voice, interview, music track, sound effect, and excerpt, and check the relevant licenses and guest releases. Mark explicit content accurately and disclose AI-generated audio where Apple's current guidelines require it. Keep the original recording and project files in protected storage so that later corrections can be made without repeatedly encoding an already-compressed copy.
- 02
Finish the edit and preserve a clean master
Complete the editorial cut, remove only approved mistakes and noise, check beginning/end fades, and confirm the episode is complete rather than a rough sample. Export a high-quality master from the editing project before making any smaller distribution copy. Apple's RSS guidance accepts MP3 or AAC; it recommends AAC for the same bitrate, while sample rate, channel count, and bitrate affect sound and file size. Do not force a mono recording into stereo or downsample merely to hit a smaller file. Write down the master?s duration, sample rate, channel count, format, and file size, and make a separate working copy for any normalization or compression so the master remains intact.
- 03
Review loudness and peak level before encoding
Listen for clipping, abrupt level jumps, excessive silence, missing audio, and channel problems on headphones and speakers. Apple's current audio guidance recommends preconditioning around -16 dB LKFS with a +/-1 dB tolerance and a true peak no higher than -1 dB FS, calculated under ITU-R BS.1770-5; treat this as guidance for a natural listening level, not a substitute for editorial review or a requirement to make every program sound identical. If a measured adjustment is still needed, use a copy and note the chosen target. Recheck the output and listen again, because normalizing can alter dynamics and cannot repair clipping already baked into a recording.
- 04
Apply an optional loudness pass to the reviewed copy
If the reviewed master still needs level adjustment, Audio Volume Normalizer can target a loudness and bounded true-peak ceiling on a working copy. Use the Apple guidance as a reference for this RSS release, retain the original master, and compare the normalized version at a matched playback level. Inspect whether quiet passages, music transitions, speech dynamics, and peaks still sound intentional; a numeric target does not detect every distortion, edit, or speech-quality problem. If the master already meets the intended listening level and sounds clean, skip this tool. Do not process a confidential or unreleased recording unless the tool's current privacy and processing terms are acceptable.
- 05
Encode a smaller supported delivery file only when needed
Check the hosting provider's current file limits and Apple's RSS format guidance before re-encoding. If an MP3 copy is suitable for the host and needed for delivery, Audio Compressor can reduce it using a selected bitrate; Apple recommends 64?128 kbps for mono or 128?256 kbps for stereo at 44.1/48 kHz for RSS audio, with AAC generally giving better quality at the same bitrate. Keep the original, select a bitrate appropriate to the episode's channel count, and do not repeatedly compress the same file. After conversion, inspect the actual format, bitrate, sample rate, channel count, duration, and size, then listen to the complete result for artifacts, missing endings, or playback faults. The tool does not test Apple's feed or host limits.
- 06
Add accurate episode metadata and publish through the host
In the podcast host, add an accurate episode title and description, release date/time, episode type and number where applicable, language, and correct explicit-content setting. Use the original episode identity consistently and ensure the RSS item has a unique stable GUID and enclosure URL. Check that the host points the enclosure to the final audio file, reports the correct length and media type, and makes the feed and episode publicly addressable for the distribution route. Apple's RSS requirements include unique enclosure URLs and GUIDs and require a feed that supports streaming requests; host controls and feed fields vary, so follow its current instructions. Do not place passwords or private listener-only audio in a public directory feed.
- 07
Test the feed and resolve technical validation issues
Open the RSS feed through Apple's recommended test path and confirm the show artwork, episode title, description, release date, and playback appear as intended. Run Apple Podcasts Connect feed validation when available and review errors for unsupported media, missing required tags, unreachable enclosure URLs, duplicate GUIDs, or server behavior. Correct the source in the hosting provider or feed generator, then validate again; a successful technical validation checks feed requirements but does not mean Apple has approved the show under its content guidelines. If a host controls the feed, use its support channel for enclosure, byte-range, or feed-update problems instead of editing a generated RSS file without understanding the effects.
- 08
Submit or monitor the show and verify publication
If this show is not yet listed, use Apple Podcasts Connect to submit the public RSS feed and confirm show rights, contact details, availability, and other current submission fields. Follow the status in Connect and respond to any warning or review request; technical validation and editorial review are separate. Once the episode is available, play it from the Apple listing and from the host's feed, confirm the final audio and metadata, and note the release date and feed URL. If it is missing, first check host processing, Connect status, release time, feed errors, and duplicate identifiers. For an update, replace the original episode through the host rather than submitting a duplicate episode.
THE HELPER CREW
Tools for the fiddly bits.
These are the currently published Nirmion tools matched to this guide. Open a tool page for its accepted inputs and limits.
RECEIPTS, PLEASE
Sources & review notes
Each source is linked to the steps it supports. Open it to check its scope and current guidance.
Source checked 2026-10-10