← All articles

Podcast image tag: formats, sizes, and purposes

Explore this article with AI

Open a source-aware analysis with this article as the primary source.

ChatGPTClaudePerplexityGeminiGrokGoogle AI
Follow Podder on Google

Add us to your Preferred Sources.

The podcast image tag is RSS metadata for delivering one or more visual or video assets with information about their shape, size, accessibility text, format, and intended use. Written as <podcast:image>, it expands beyond square show or episode artwork while remaining cross-compatible with <itunes:image>.

How the podcast image tag works

The official Podcast Namespace image specification allows the tag under <channel>, <item>, or <podcast:liveItem>. Multiple copies are allowed, which lets a feed offer different art directions or formats for the same show, episode, or live item.

Only href is required. It contains the asset URL.

<podcast:image
  alt="An antenna emanating signal waves"
  purpose="artwork"
  type="image/jpeg"
  aspect-ratio="1/1"
  width="1200"
  href="https://example.com/images/episode-square.jpg"
/>

The parent defines whether the asset belongs to the show, an episode, or a live item. For other episode-level metadata, see the podcast episode tag.

Podcast image tag attributes

Each optional attribute gives a receiving app more context:

AttributeStatusWhat it communicates
`href`RequiredURL of the delivered media
`alt`RecommendedConcise text replacement for the asset's content
`aspect-ratio`RecommendedShape written with CSS-style syntax, such as `1/1` or `16/9`
`width`RecommendedAsset width in pixels
`height`OptionalAsset height in pixels
`type`OptionalMedia type, such as `image/jpeg` or `video/mp4`
`purpose`OptionalSpace-separated tokens suggesting intended uses

When a tag contains no aspect ratio or purpose, the specification says the image is assumed to be square. Supplying aspect-ratio and width helps an app decide how the asset may fit its interface. height can add the second pixel dimension, though it is less critical when width and aspect ratio are already present.

Use alt to describe what the image contains rather than repeating its filename. This gives an accessibility-focused text replacement to apps that support it. Keep the description concise and tied to the visible content.

The type attribute can identify a familiar image format or another delivered media type. The specification includes video/mp4 examples, so the tag's role extends beyond static JPG or PNG assets.

Using purpose and aspect ratio together

The purpose attribute accepts a case-insensitive, space-separated set of tokens and should remain within 128 characters. Tokens are display hints. Apps may choose whether to honor them, and anyone may define a token with its own requirements.

The specification suggests generic tokens including artwork, social, canvas, banner, publisher, circular, and poster. For example, artwork indicates show or episode art, while social indicates an asset prepared for social previews. A single asset can carry more than one token.

<podcast:image
  purpose="artwork"
  aspect-ratio="1/1"
  href="https://example.com/images/episode-square.jpg"
/>
<podcast:image
  purpose="artwork social"
  aspect-ratio="16/9"
  href="https://example.com/images/episode-landscape.jpg"
/>

This pair gives an app a square artwork option and a landscape option intended for artwork or social use. The app still controls selection and presentation. The tag communicates the publisher's intent and asset properties.

A platform can also define a namespaced token for a specific placement. Follow that platform's current asset guidelines before adding such a token. The Podcast Namespace document permits these tokens but does not make every app recognize them.

How to verify image entries

Open each href and confirm that it returns the intended asset. Then compare the actual dimensions, aspect ratio, and media format with the XML attributes. A copied URL or stale export can leave otherwise valid metadata pointing at the wrong file.

Before publishing, list each intended placement and match it to one asset entry. This makes omissions easier to spot when a feed contains square artwork, landscape social art, and a live-item asset. Check that reused files carry attributes that describe the file itself, not another version from the same export. If an asset changes, review the tag again rather than assuming the replacement has the same dimensions or format.

Inspect the raw feed after publishing. Confirm that every tag sits under the intended parent, each asset has an href, and each purpose value uses spaces between tokens. Check the result in apps that document support because valid XML alone does not guarantee a particular crop, layout, or asset choice.

Images attached to a live item can sit beside other live metadata. The podcast chat tag covers chat locations, while the podcast content link tag can send listeners to labeled external content. Those elements solve separate feed jobs.

To review episode delivery alongside your feed and artwork checks, start with Podder Analytics.

FAQ

What is the podcast image tag?

The podcast:image tag is Podcast Namespace RSS metadata that delivers one or more media assets for a channel, item, or live item, along with optional display hints.

Which podcast:image attribute is required?

Only href is required. The specification recommends alt, aspect-ratio, and width, while height, type, and purpose are optional.

Can a feed include more than one podcast:image tag?

Yes. Multiple tags can offer different aspect ratios, formats, dimensions, or intended uses so an app can select a suitable asset.

Put it into practice

See who's actually listening.

Podder gives you audience demographics, per-episode analytics, and chart tracking. The Chartable alternative that goes deeper.

Start free