JSON to Markdown converter

What a JSON actually stores

JSON is machine-readable but token-expensive: every brace, quote and repeated key is charged for on every record. Converting it removes that overhead and often makes the shape of the data clearer to a model at the same time.

API responses and exports arrive as JSON, and asking a model about the data is usually easier once the syntax is out of the way.

What survives the conversion

All values. The structure is inspected first — an array of flat objects is a table in disguise and is rendered as one, while anything nested becomes headings with nested lists.

What does not

Types are flattened to text, so the distinction between the number 1 and the string "1" is lost. Deeply nested structures become deeply nested lists, which are harder to read than the original past a few levels.

Saying so plainly is deliberate. A converter that quietly drops half a document is worse than one that tells you which half, because you can work around a limit you know about.

Questions

When does it make a table?

When the top level is an array of objects whose values are all simple. That shape is a table, and reads far better as one.

Is JSON not already fine to paste?

It works, but you pay tokens for every brace, quote and repeated key. On a large array that overhead is a substantial share of the bill.

What if my JSON is invalid?

You get the parser error rather than a silent empty result, so you know what to fix.

Converting a different format

The same engine handles eighteen formats in total, all of them in your browser.

Token rates checked 2026-08-31. See the cost on all 35 models →