JSON to Markdown

Render JSON as a Markdown table or nested list. Ready for GitHub, Notion, Obsidian, and any GFM target. 100% in-browser.

FORMAT
JSON INPUTarray or object
MARKDOWN OUTPUT
<!-- Markdown appears here -->

Two formats, two purposes

Tables are unbeatable for arrays of records — API responses, query results, benchmark data. Every modern Markdown renderer supports GFM tables, and they survive copy-paste into Notion, Obsidian, and Linear.

Lists are better for everything else. A single config object, a deeply nested response, a structure where rows have different keys — all of these read poorly as a table but cleanly as an indented list with bold keys.

Safe escaping

Pipes inside cells are escaped, underscores and asterisks in strings are preserved without becoming bold or italic. The output drops into a README without surprises.

Privacy first

Conversion runs locally. Paste a production API response, copy the Markdown, paste it into your team's wiki — nothing crosses the network.

Common questions

What kind of Markdown does this produce?
GitHub-Flavored Markdown (GFM) — the same dialect used by GitHub, GitLab, and most modern Markdown renderers. Tables use the pipe-and-dash syntax that GFM standardised; lists use standard hyphen bullets.
Should I use table or list mode?
Table mode for arrays of flat objects with the same keys — the most common API-response shape. List mode for single objects, nested structures, or arrays of mixed shapes. Switch and see which output reads better for your data.
How are nested objects handled?
In table mode, nested objects and arrays are JSON-stringified into the cell. In list mode they become indented sub-lists, preserving the structure. For deeply nested data, list mode reads better.
Does it escape Markdown special characters?
Yes. Pipe characters in cell values are escaped, and underscores or asterisks in strings are preserved without becoming bold or italic. The output is safe to paste directly into a README, an issue comment, or a Notion page.
Where do I paste the output?
Anywhere GFM is supported — GitHub issues and PRs, GitLab, Bitbucket, Notion, Obsidian, Bear, most static site generators (Hugo, Jekyll, Next.js MDX), and the comment fields of Linear, Jira (with the Markdown plugin), or Slack.
Is my data private?
Yes. JSON parsing and Markdown generation both run in this browser tab. No upload, no log, no server.