ToolLineup

RSS to JSON Converter

This RSS to JSON converter reads all three feed vocabularies — RSS 2.0, Atom and RSS 1.0 (RDF) — and maps them onto a single shape, so you can write one piece of code against any feed instead of branching three ways. The formats disagree on almost every element name: an entry date is pubDate in RSS 2.0, published in Atom, and dc:date in RDF. The normalised output gives every entry the same fields — title, link, published, author, categories, summary — and reports which format was detected and how many items it found. Normalising can be switched off to return the raw parsed structure, keeping namespaced elements a common shape does not cover.

How it works

RSS 2.0, Atom and RSS 1.0 describe the same thing with different element names. This reads all three and gives every feed the same field names — title, link, published, author, categories, summary — so you can write one piece of code against any of them.

Turn normalising off to get the raw parsed structure instead, which keeps custom namespace elements the common shape does not cover.

The conversion runs entirely in your browser — nothing you paste or upload is sent to a server.

Feed XML input
Paste the contents of an RSS or Atom feed…
JSON output

How to convert an RSS feed to JSON

  1. Open the feed URL in your browser and copy the XML, or upload a saved .xml / .rss file.
  2. Paste it into the input on the left.
  3. The JSON appears on the right, with the feed's own format detected automatically.

One shape for three formats

RSS 2.0, Atom and RSS 1.0 (RDF) all describe a list of dated entries, but they disagree on almost every element name: an entry's date is pubDate in RSS 2.0, published in Atom, and dc:date in RDF. This converter reads all three and maps them onto the same field names — so you can write one piece of code that handles any feed instead of three branches.

Common fieldRSS 2.0Atom
titletitletitle
linklinklink[@href]
publishedpubDatepublished
authorauthor / dc:creatorauthor.name
summarydescriptionsummary

When to turn normalising off

Some feeds carry extra namespaced elements — podcast durations, media thumbnails, custom publisher metadata — that no common shape covers. Switch off Use common field names and you get the raw parsed structure with every element intact.

Common use cases

  • Prototyping a feed reader without writing an XML parser first.
  • Checking what a feed actually publishes when entries are not showing up.
  • Turning a blog or podcast feed into JSON for a static site build.

Frequently asked questions

How do I convert an RSS feed to JSON?

Open the feed URL in your browser, copy the XML it returns, and paste it into the left panel — or upload a saved .xml or .rss file. The JSON appears on the right with the feed format detected automatically.

Which feed formats are supported?

RSS 2.0, Atom and RSS 1.0 (RDF). The format is detected from the root element, so you do not need to tell the tool which one you have.

What does normalising the field names do?

The three formats name the same things differently — an entry date is pubDate in RSS 2.0, published in Atom and dc:date in RDF. Normalising maps them all onto one set of names, so code that reads the output works with any feed.

When should I turn normalising off?

When the feed carries extra namespaced elements — podcast durations, media thumbnails, publisher metadata — that a common shape does not cover. Switching it off returns the raw parsed structure with every element intact.

Can it fetch a feed from a URL directly?

No. Everything runs in your browser with no server, and browsers block cross-origin requests to most feed URLs, so paste the feed contents or upload the file instead.

Is the feed I paste sent anywhere?

No. Parsing happens entirely in your browser, so nothing you paste or open is transmitted or logged.

Related tools