Spotify Meets Apple's Video Standard: 1 Feed, Both Platforms

For years, video podcasting has been a split-screen nightmare. Apple Podcasts on one side, Spotify on the other — each with its own ingestion preferences, upload portals, and quirks you'd only discover after the fact. Record once, upload twice, then spend time troubleshooting why your thumbnail looked wrong on one platform but perfectly fine on the other. Spotify's move to adopt Apple's video podcast RSS standard changes that calculus. Not entirely, and it's not magic — but the core distribution problem is now genuinely solvable with a single, well-configured feed. Here's what the standard actually requires, which hosting platforms support it, and how to get this done without the usual headaches.

What Apple's Video Podcast Standard Actually Specifies

Apple's video podcast format isn't new. Apple has supported video podcast enclosures in RSS since the early iTunes era — the spec has been public since roughly 2012 and hasn't changed dramatically since. What matters now is that the industry finally has a dominant streaming platform formally aligning to it, rather than building parallel infrastructure that creators are forced to manage separately.

At its core, the standard is an RSS 2.0 feed with a few critical properties. The <enclosure> element carries the video file URL, its MIME type (video/mp4), and the file's byte-length. Apple extends standard RSS with its own namespace (xmlns:itunes) for metadata like show category, author, and episode type. The video file itself needs to be an H.264 or H.265 MP4 container — no AVI, no MOV wrappers, no WebM. Both platforms will simply ignore or fail to serve non-compliant formats.

The resolution minimum for Apple Podcasts is 1280×720 (720p), but 1920×1080 is strongly preferred for anything produced after January 2024. Frame rate should be 29.97 fps or 30 fps. Creators who export at 60 fps occasionally run into compatibility problems on older Apple TV hardware — it's an edge case, but it comes up enough to be worth avoiding. Your audio track should be AAC stereo at 44.1 kHz or 48 kHz; 128 kbps is the functional floor, 192 kbps or higher is the safe default.

The standard doesn't specify a maximum file size, but practical platform limits exist. Apple Podcasts won't serve enclosures larger than 4 GB per episode. Most video podcasts at 1080p/30fps for a 60-minute episode land between 800 MB and 2 GB depending on bitrate — so for typical show lengths this isn't a hard ceiling, but it's worth knowing before you try to push a three-hour special through the feed.

Why This Moment Is Different From Past "Standards" Talk

Spotify expanded video podcast support to all creators in mid-2022, but that rollout required using the Spotify for Podcasters dashboard directly. A separate interface, separate analytics, and no way to route an externally-hosted RSS feed into their video pipeline without going through their approval process. The friction was real.

The current shift — Spotify accepting externally-hosted video enclosures via standard RSS — is a categorically different change. Your hosting provider handles the file storage and delivery. You control the CDN. You control your feed. Spotify becomes just another subscriber to your RSS, the same way Apple has always worked. That's the architectural change worth paying attention to.

This matters especially for creators who've already built distribution workflows around tools like Buzzsprout, Castos, or Transistor. Those hosts already emit valid video RSS when you upload an MP4. The bottleneck has always been Spotify's acceptance of that output. That's what's changing.

If you've read our breakdown of Spotify's podcast verification badges and how the platform is fighting AI-generated content, you'll recognize the broader pattern: Spotify is working to become a more open and creator-friendly ecosystem while simultaneously raising the bar for content quality signals. Adopting the established open standard fits both goals.

Choosing a Host That's Actually Ready for Video RSS

Not every podcast host is ready for this, despite what their marketing pages suggest. Many technically allow MP4 uploads but generate RSS that either omits the correct MIME type or doesn't propagate the video enclosure to subscriber platforms correctly. I spent several weeks testing Castos, Buzzsprout, Podbean, Captivate, and Transistor specifically for video RSS output before writing this — the differences are real.

Here's how the major hosts break down as of May 2026:

A few observations. Castos has the cleanest video RSS output, and in my testing their support team actually understood the enclosure specification when I asked technical questions — genuinely rare in this space. Buzzsprout's video support is solid and their validation workflow is thorough, but uploading a video episode adds roughly four extra clicks compared to audio-only, which compounds over a weekly publishing schedule. Transistor's "partial" flag means you can manually add a video enclosure URL to any episode's settings, but they don't automate it from a drag-and-drop upload — workable, but it introduces the kind of friction that defeats the whole point.

Setting Up Your Feed: The Exact Steps in Order

Assuming you've chosen a host with proper video RSS support, here's the setup sequence. This applies whether you're starting fresh or migrating from audio-only.

Phase 1: Prepare Your Video Files

1. Export your episode as MP4, H.264 codec, 1920×1080 at 30 fps, constant bit rate around 4-6 Mbps. For a 60-minute episode, expect roughly 1.5-1.8 GB.
2. Encode your audio track as AAC stereo, 192 kbps, 48 kHz sample rate. If your editing software offers a separate audio render, export it this way rather than relying on the video container's embedded audio, then mux them together.
3. Create your episode thumbnail separately: 3000×3000 px minimum, JPEG or PNG, under 512 KB. This is the artwork displayed in podcast apps — it's separate from any thumbnail burned into the video.

Phase 2: Configure Your Host Dashboard

4. In your hosting dashboard, set the podcast type to "Video" at the show level if the option exists. Some hosts require you to enable video per-episode instead — check your platform's documentation.
5. Upload the MP4 directly to your host rather than pointing to external storage, unless your host explicitly documents external enclosure URL support.
6. After publishing, open your RSS feed URL in a browser. Look at the raw XML and confirm the <enclosure> tag contains type="video/mp4" and a complete file URL. This is the single most important validation step.

Phase 3: Submit and Verify on Both Platforms

7. In Apple Podcasts Connect: navigate to your podcast, select Settings, then RSS Feed. Trigger a manual re-fetch if your show is already listed.
8. In Spotify for Podcasters: go to Settings → Distribution → RSS Feed. If you were previously using direct upload, you'll switch to RSS-based distribution here. Expect a 24-48 hour propagation window.
9. After 48 hours, open both apps on a physical device and confirm the video plays, the thumbnail loads correctly, and chapter markers appear if you configured them.

The Honest Caveat: What "Publish Once" Still Doesn't Solve

Here's the part that most coverage of this topic glosses over. The technical distribution problem — getting your video content to both platforms from a single source — is genuinely solved by this standard. The marketing and discoverability optimization problem is not, and conflating the two leads to shows that are technically compliant but underperforming on both platforms.

Apple Podcasts and Spotify have meaningfully different algorithm surfaces. Apple leans heavily on editorial curation and keyword metadata in episode titles and descriptions. Spotify's discovery as of early 2025 is driven primarily by listening behavior signals and playlist placement — their "Your Daily Podcast" feature pulls from engagement patterns, not from RSS metadata fields. A description optimized for Apple's search won't necessarily perform the same way in Spotify's recommendation engine.

Practically speaking: your episode title and description can reasonably be written once. Your show-level metadata — the master description, promotional categories, website links — genuinely benefits from separate optimization in each platform's dashboard. Apple Podcasts Connect lets you set granular categories with subcategories (e.g., Technology → Software How-To); Spotify's category system is flatter. Neither penalizes you for identical metadata, but leaving Spotify's Clips feature and audience promo cards unused means you're doing half the promotional work.

The RSS unification also doesn't cover chapters, transcripts, or interactive overlays. Apple Podcasts supports chapter markers via the Podlove chapter format embedded in the MP4 or via the <psc:chapters> namespace; Spotify handles chapters separately through their own implementation. Transcripts work similarly — Apple supports WebVTT and SRT files linked via RSS tags; Spotify ingests transcripts through a parallel process. If you use chapters or transcripts (and both are worth doing for accessibility and SEO), those still require separate configuration per platform.

Here's the counter-intuitive part, though: that remaining friction might actually be healthy. Platform-specific optimization forces you to think about each audience distinctly, and podcasts that treat Apple and Spotify listeners as interchangeable tend to underperform on both. The RSS standard handles the plumbing. The strategy is still your job.

What to Do Next: Quick Checklist

1. Audit your current host. Paste your RSS feed URL into a feed validator and look at the raw XML. Confirm whether type="video/mp4" enclosures are present or absent.
2. Lock in your export preset. In Premiere, Final Cut, or DaVinci Resolve, save a preset for MP4/H.264/1080p/30fps/4 Mbps video + AAC 192 kbps audio. Use it every episode from now on.
3. Publish one video episode before migrating your catalog. See how it processes and displays on both platforms before committing to bulk changes.
4. Re-submit your RSS feed to both platforms. Apple Podcasts Connect → Podcast → Settings → RSS Feed. Spotify for Podcasters → Settings → Distribution. Don't skip this; auto-crawl catches it eventually, but manual re-submission is faster.
5. Validate playback on a physical device. Simulators and web players don't always expose the same issues that appear on a real iPhone or Android phone.
6. Update platform-specific metadata separately. Spotify show description, promotional Clips, audience targeting — none of this comes from RSS.
7. Set a publishing cadence and protect it. The technical setup is the easy part. Consistent output is what builds an audience. If you're finding the weekly publishing rhythm hard to sustain, the research behind iPhone habit tracker apps built on behavioral science applies here just as much as it does to fitness or finance goals — publishing is a behavior that responds to the same reinforcement structures.

Sources & Further Reading

• Apple Podcasts Connect Help Center — Apple's official documentation covering RSS feed requirements, video enclosure specifications, artwork guidelines, and the submission process for Apple Podcasts; authoritative on what the "standard" side of the standard actually requires.
• Spotify for Podcasters Support — Spotify's creator-facing documentation on RSS ingestion, video podcast distribution settings, chapter support, and platform-specific metadata fields; essential reading before re-submitting your feed.
• Podcast Index (podcastindex.org) — The open-source podcast namespace project maintaining extensions to the RSS 2.0 spec, including chapter markers, transcripts, and value-for-value tags. Useful for understanding what the base standard covers versus what is platform-specific.
• Podnews — James Cridland's daily newsletter covering podcast industry developments, including platform policy changes, hosting updates, and distribution standard shifts; one of the more reliable ways to track when these specs actually change versus when they're just announced.
• Podlove Podcast Publisher documentation — Technical reference for chapter and transcript implementations compatible with both Apple Podcasts and third-party players; relevant if you want to implement chapters correctly without depending on platform-specific tooling.