How to convert an rss or atom xml feed to json
- Step 1Fetch the feed XML — Navigate to the feed URL (e.g. https://example.com/feed.xml) in your browser and save the page source, or run curl -o feed.xml https://example.com/feed.xml from a terminal.
- Step 2Upload or paste the XML — Drop the .xml file or paste the feed content. The converter auto-detects RSS 2.0 (rss root element) vs Atom 1.0 (feed root element) and normalizes the fields accordingly.
- Step 3Review the normalized JSON output — Each feed item becomes a JSON object with consistent keys regardless of input format. Check that published dates are valid ISO-8601 strings and that HTML in descriptions is handled as you expect.
- Step 4Use in your application or workflow — Copy the JSON into a Next.js data/ folder for getStaticProps, paste it into your no-code automation tool's JSON source, or save as a .json file for pandas.read_json() ingestion.
Frequently asked questions
How are Atom entry links handled, since they use elements rather than text nodes?+
Atom <link rel="alternate" href="..."/> elements are normalized to a link string field matching the RSS link convention. The tool picks the href attribute of the element with rel="alternate" (or the first link element if no rel is set) so the output JSON is consistent for both RSS 2.0 and Atom 1.0 inputs.
What happens to media:content or media:thumbnail elements in the feed?+
Media elements from the Media RSS namespace are preserved under a media key in each item object — useful for podcast episode thumbnails, news article featured images, and video enclosures. The media key contains url, type, and medium sub-keys where present.
Is the feed content sent to JAD Apps?+
No. The XML parsing runs entirely in your browser using fast-xml-parser. Feed content — including any private Intranet feeds accessed with a session cookie — never reaches JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.