Why imports don't auto-fill episode artwork with show cover art

Modified on Tue, 24 Mar at 7:59 AM

Short answer: Apple Podcasts now displays episode art as a smaller image overlaid on top of your show cover art. If they're the same image, you get two identical thumbnails nested inside each other, which hurts your visual presence.



What changed in Apple Podcasts


Apple redesigned how episode artwork is displayed. On Home and show pages, episode art appears as a smaller square overlaid on your show cover. The intent is to help listeners visually distinguish individual episodes at a glance.


Depending on the combination of episode and show art, you may have:

  • Unique episode art (a guest photo, a topic illustration): looks great, the small square stands out against the larger show cover.
  • Same image as your show cover: you get two identical squares, one large and one small. It looks broken and adds no visual information.


Apple's own guidance is clear: episode art should "highlight an episode's content, such as a specific theme or guests." They recommend avoiding your podcast logo in episode artwork, since titles are displayed separately by the app.


How we treat (duplicated) episode art (and why)


When you publish an episode without uploading episode-specific artwork, RSS.com intentionally leaves the <itunes:image> tag empty in your RSS feed. Apple Podcasts handles this gracefully, it simply falls back to your show cover art, with no duplication or visual glitch.



What you should do


- Upload unique episode art (recommended): feature guests, topics, or episode-specific visuals. Apple's template is 3000×3000px, PNG or JPG.

- Or don't upload episode art at all: Apple Podcasts will use your show cover as the fallback and display it correctly.


The one thing to avoid: using your show cover art as episode art. That's what causes the broken nested-thumbnail effect.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article