JSON to Markdown
Turn JSON into GitHub-flavored Markdown tables—no manual mapping. Accepts an object, an array of objects, or a primitive array; optional flatten turns nested fields into dot-path columns (e.g. user.address.city) for docs, Notion, and LLM prompts.
The rendered Markdown preview will appear here after conversion.
JSON to Markdown
Turn JSON into GitHub-flavored Markdown tables—no manual mapping. Accepts an object, an array of objects, or a primitive array; optional flatten turns nested fields into dot-path columns (e.g. user.address.city) for docs, Notion, and LLM prompts.
All conversion runs in your browser. Your JSON is not uploaded or stored on our servers.
Frequently Asked Questions
What JSON shapes are supported?
Root object → two-column Key | Value table (nested values as JSON in cells unless you enable Flatten). Array of objects → one row per object. Array of strings/numbers/booleans/null → two columns (# and Value). Mixed arrays (objects and primitives together) are not supported.
How are nested objects handled?
By default, nested objects or arrays are JSON.stringify’d into one cell so the table stays valid. Turn on “Flatten nested objects” to expand nested plain objects into dot-path columns; arrays in data are still stringified in cells.
When should I use flatten?
Use it for API payloads with nested records when you want spreadsheet-style columns (user.name, address.city) for READMEs, wikis, or feeding columnar context to an LLM—without losing values to a single JSON blob cell.
Is my data uploaded?
No. Parsing and table generation run entirely in your browser.
How is column order chosen?
For tables, columns follow first-seen key order across rows. Enable “Sort column names” for A–Z headers. Single-object Key | Value mode follows key order (or sorted when enabled).