Sarah Chen, SEO Content Strategist
What This Tool Does
Developers constantly need to turn JSON — an API response, a database query result, a config block — into a human-readable table for documentation, a pull request, or an issue. This tool does exactly that: paste JSON, and it produces a GitHub-Flavored Markdown pipe table with a live preview, updating as you type.
It is built for real payloads, not just toy examples. It handles arrays of objects with differing keys, deeply nested wrappers, and values that are themselves objects, all without leaving the browser.
How to Use It
- Paste or upload JSON. Use the Prettify button to reformat it if it arrived minified.
- Set the array path if your records are nested — for example
data.itemsorresult.rows. - Review the table in Markdown or Preview mode and set per-column alignment.
- Copy or download the resulting
.md.
Supported JSON Shapes
- Array of objects → columns are the union of all keys, in first-seen order.
- Array of arrays → the first inner array becomes the header row.
- Array of primitives → a single
Valuecolumn. - Single object → a two-column
Key/Valuetable.
Working With Nested Data
Real API responses rarely put the array you want at the top level. The dot-path selector lets you navigate into the structure — data.items walks into the data object and then its items array. Values that remain nested inside a cell are serialized as compact JSON so nothing is silently dropped; if you need those fields broken out, simply point the path at the nested collection.
Common Use Cases
- API documentation: turn a sample response into a readable field table.
- Database results: paste JSON exported from a query tool and document the rows.
- Config references: render a settings object as a key/value table.
- Test fixtures: document the shape of mock data in a test README.
Tips
- If the table looks empty, check the array path — it may be pointing at an object instead of an array.
- Use Prettify to catch invalid JSON quickly; the error message shows where parsing failed.
- For consistent columns, ensure your objects share key names (the union still works, but uniform keys read best).
