Novus Convert
Convert files
Data format

JSONFEED converter

A .jsonfeed file is a JSON Feed: syndication expressed as a plain JSON object with a version, feed-level metadata and an items array, rather than as XML. It exists because most people building feed readers today would rather parse JSON than namespaced XML.

Private for supported formats — processed in your browser

Convert supported files

Runs on your device

Drop JSONFEED files here

Batch files can each use a different output. Nothing uploads for local conversions.

Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.

Where JSONFEED comes from

Manton Reece and Brent Simmons published JSON Feed in 2017, arguing that the difficulty of XML parsing was suppressing new feed tooling. Version 1.1 followed in 2020 with clarifications around authors. It has real but modest adoption — micro.blog, several static site generators and a number of readers — and its main contribution has been making feeds approachable again rather than displacing RSS.

How JSONFEED works

  • The version field is a URL, which doubles as documentation and as an unambiguous version marker.
  • Items carry an id that may be any string, plus optional url, title, content_text and content_html.
  • Dates use RFC 3339, matching Atom rather than RSS.
  • Attachments are a first-class array with mime_type and size_in_bytes, so podcasting needs no extension.
  • Being JSON, it parses with the standard library in every language and needs no namespace handling.

When to use JSONFEED

  • Feeds consumed by JavaScript clients that would otherwise need an XML parser
  • New reader and aggregator software where XML tooling is a barrier
  • Sites that already emit JSON APIs and want a feed with no new machinery
  • Converting a feed into XML formats for wider reader support

Strengths and limitations

Strengths

  • Parses with a standard JSON library — no namespaces, no entities, no XML pitfalls
  • Distinguishes plain-text and HTML content explicitly
  • Attachments are built in rather than an extension

Limitations

  • Far less widely supported than RSS or Atom
  • Most podcast clients will not read it
  • Being newer, it has a thinner ecosystem of tooling and validators

Compatibility

Supported by micro.blog, NetNewsWire, Feedbin and a number of static site generators; ignored by most older readers and by podcast clients. Novus Convert parses it locally and converts to RSS and Atom, which is the practical way to reach readers that do not speak it.

Feed and item fields — id, url, title, summary and publication date — are preserved. Attachments and typed HTML content are not represented in every target.

Convert JSONFEED to another format

Convert other formats to JSONFEED