RSS to JSON

updated 20 August 2026 · RSS 2.0 · RSS 1.0 · Atom 1.0

Paste feed XML and get JSON with consistent field names, whether the source is RSS 2.0, RSS 1.0/RDF, or Atom. Titles, links, dates, authors, categories and enclosures are mapped to one shape, so downstream code does not care which flavour it came from.

feed → json Output: Item limit: include descriptions Indent:

Drop a feed file here, or

ready

RSS to JSON

The feed type is detected from the root element — <rss>, <rdf:RDF>, or <feed> — and each flavour's fields are mapped onto one normalised set: title, link, guid, published, author, categories, and optionally description and content.

— S., [email protected]

How to use it

Paste the feed XML, or drop a saved .xml / .rss file on the pane.
Choose feed + items for the channel metadata plus entries, or items array only when you just want the list.
Set an item limit to sample a long feed, and untick descriptions if you only need the headlines.
Copy the JSON or download it.

How the flavours are mapped

RSS 2.0 — channel/title, link, description, language, lastBuildDate; items from <item> with pubDate as the date and <guid> as the identifier.
Atom 1.0 — title, subtitle, updated, and the rel="alternate" link as the feed link; entries use published (falling back to updated), <id> as the identifier, the author's <name>, and term attributes for categories.
RSS 1.0 (RDF) — treated like RSS 2.0, since the item fields carry the same names.
Enclosures — an <enclosure> becomes an object with url, type and length, which is what podcast feeds put the audio file in.

Dates are passed through, not parsed

RSS uses RFC 822 dates (Tue, 19 Aug 2026 14:00:00 +0000) and Atom uses ISO 8601 (2026-08-19T14:00:00Z). Both are copied through as the strings the feed contained rather than normalised, because reformatting a date means guessing a timezone when one is missing. Parse them in the consumer, where you know what you want.

Why paste rather than fetch a URL

A browser cannot fetch an arbitrary feed URL from a page on a different origin — the cross-origin rules forbid it, and routing the request through a server would mean uploading what you are reading. So this tool takes the XML you already have: use View source on the feed, or save it and drop the file in.

FAQ

Can I give it a feed URL?

No — browsers block cross-origin fetches, and proxying the request through a server would break the no-upload promise this site is built on. Paste the XML or drop the file.

Which fields are included per item?

Title, link, guid, published date, author, and categories always; description and content only with include descriptions ticked. Enclosures appear when the item has one.

What about namespaced extensions like iTunes or Dublin Core?

They are not mapped into the normalised output. If you need them, use XML to JSON for a faithful full conversion of the whole feed, prefixes and all.

Does it handle HTML inside descriptions?

Yes — the text is extracted as-is, escaped entities decoded by the parser. The JSON string may therefore contain HTML markup, which is exactly what the feed contained.

Is the feed uploaded?

No. Parsing and mapping happen in your browser.

Related tools

XML to JSON — a faithful conversion when you need every extension field
XML Tree Viewer — inspect an unfamiliar feed
Sitemap Validator — the other XML file every site publishes
XML Validator — check a feed is well-formed before debugging it
XML to CSV — feed items as spreadsheet rows

Privacy

100% client-side. The feed you paste is parsed in the page. See the privacy policy.