RSSFeeds.com

RSS vs Atom vs JSON Feed

Three formats do the same job. RSS 2.0 is everywhere, Atom is precise, and JSON Feed is the easiest to work with. Every modern reader supports all three, so the choice matters less than you might think – but it isn't meaningless.

Updated

Illustration comparing three feed formats side by side

The Short Answer

  • Podcast? RSS 2.0. Apple Podcasts and most directories require it.
  • Blog, news site or shop? RSS 2.0 is the safe default. Atom is equally good if your software produces it.
  • Developer audience, or you build the feed by hand in code? JSON Feed is pleasant, ideally next to RSS.
  • Need strict semantics, multiple languages or a publishing API? Atom.

Publishing two formats is fine; announce both with autodiscovery and readers pick one.

Side-by-Side Comparison

Comparison chart of RSS 2.0, Atom 1.0 and JSON Feed 1.1: syntax, required fields, dates, IDs and podcast support
RSS 2.0, Atom and JSON Feed compared.
RSS 2.0Atom 1.0JSON Feed 1.1
SyntaxXMLXMLJSON
Standardised byRSS Advisory Board (frozen spec)IETF, RFC 4287Independent spec by its authors
Year200220052017 / 2020
MIME typeapplication/rss+xmlapplication/atom+xmlapplication/feed+json
Required feed fieldstitle, link, descriptionid, title, updated (+ author)version, title, items
Required item fieldstitle or descriptionid, title, updatedid, content_html or content_text
Unique IDguid (optional)id (required)id (required)
DatesRFC 822RFC 3339RFC 3339
Published vs updatedpubDate onlypublished and updateddate_published and date_modified
Content type statedNo, assumed HTMLYes: text, html, xhtmlYes: separate fields
Summary and full contentdescription + content:encodedsummary + contentsummary + content_html
AuthorsEmail only; names via dc:creatorPerson with name, email, URIObjects with name, url, avatar
Media filesOne enclosure per itemAny number of enclosure linksAny number of attachments
Podcast directoriesRequiredNot acceptedNot accepted
ExtensionsXML namespacesXML namespacesKeys starting with _
Languagelanguage elementxml:lang on any elementlanguage field
Reader supportUniversalUniversalMost modern readers

The Same Item in Three Formats

RSS 2.0
<item>
  <title>Hello world</title>
  <link>https://example.com/hello</link>
  <guid isPermaLink="true">https://example.com/hello</guid>
  <pubDate>Wed, 11 Nov 2026 09:00:00 +0000</pubDate>
  <description><![CDATA[<p>My first post.</p>]]></description>
</item>
Atom 1.0
<entry>
  <id>https://example.com/hello</id>
  <title>Hello world</title>
  <link rel="alternate" href="https://example.com/hello" />
  <updated>2026-11-11T09:00:00Z</updated>
  <content type="html">&lt;p&gt;My first post.&lt;/p&gt;</content>
</entry>
JSON Feed 1.1
{
  "id": "https://example.com/hello",
  "url": "https://example.com/hello",
  "title": "Hello world",
  "date_published": "2026-11-11T09:00:00Z",
  "content_html": "<p>My first post.</p>"
}
PlatformFormat
WordPressRSS 2.0 by default, Atom and RSS 1.0 also available
Substack, Medium, GhostRSS 2.0
BloggerAtom by default, RSS with ?alt=rss
YouTube, GitHub, RedditAtom
Shopify blogsAtom
Mastodon, BlueskyRSS 2.0
HugoRSS 2.0
Jekyll (jekyll-feed)Atom
Micro.blogJSON Feed and RSS
Every podcastRSS 2.0

Readers don't care: they accept all of them. The choice usually comes from your software. Check what yours produces with the Feed Validator.

Strengths and Weaknesses

RSS 2.0

For: universal support, the only option for podcasts, a huge ecosystem of extensions, and the format people mean when they say "RSS". Against: ambiguities – is description HTML or text? Is a guid a URL? Author must be an email. Dates use an old email format that developers often get wrong.

Atom

For: precise and unambiguous, mandatory IDs and update times, explicit content types, proper internationalisation, multiple enclosures, and a standard publishing protocol. Against: a bit more verbose, requires an author, and podcast platforms don't accept it.

JSON Feed

For: trivial to generate and parse in any language, no XML escaping or CDATA, separate HTML and text fields, multiple attachments. Against: younger and less universal; some aggregators, automation tools and enterprise systems only accept XML feeds.

Switching Formats

Changing format means changing the feed URL, so redirect the old URL with a 301 to keep subscribers. Make sure IDs stay identical across formats – use the same permalink as guid, Atom id and JSON Feed id – so readers don't show your posts twice. The Feed Converter shows what your feed looks like in each format.

Sources and Further Reading