Skip to content
JSON to Markdown
JSON Array
5 lines · 149 chars
Markdown
6 lines · 110 chars
Ready

JSON to Markdown Table

Turn JSON arrays into tidy Markdown tables — free, private and running entirely in your browser

JSON to Markdown builds a GitHub-flavoured Markdown table from a JSON array of objects, or from a single object (treated as one row). Paste into the left pane; the sample is three people with id, name, and role. Left / Center / Right sets column alignment. Pipes in cells are escaped, nested values are stringified into the cell, and the .md download is named table.md. Parsing and conversion stay in this tab.

Last updated: 15 October 2026

Guide, examples, and FAQ

About JSON to Markdown

What it does

Keys across all rows are unioned into the header. Missing keys render as empty cells. Arrays or primitives that are not objects are wrapped as a single value column. An empty array produces no table and shows “Empty array: nothing to convert.” Invalid JSON shows the parser message on the output status.

Who it is for

For developers documenting API samples, maintainers filling README tables, and anyone pasting structured JSON into a GitHub issue or changelog without rebuilding columns by hand.

When to use it

Use it when the data is already JSON. If you still have a spreadsheet, convert with CSV to JSON first, then open this page.

Key features

  • Array or one object

    An array of objects becomes one row each. A lone object becomes a one-row table. Non-objects inside an array are placed under a value column.

  • Alignment

    Left writes :---, Center :---:, Right ---: in the separator row — the usual Markdown alignment markers.

  • Pipe escaping

    Each | in a header or cell becomes \|. Newlines inside a cell are flattened to spaces so the table stays one line per row.

  • Nested values

    Objects and arrays in a field are JSON.stringify’d into the cell (then escaped). They are not expanded into extra columns.

How to use JSON to Markdown

  1. 1Paste a JSON array of objects, or keep the sample (Ada / Grace / Linus).
  2. 2Fix any parser error shown on the Markdown pane before expecting a table.
  3. 3Choose Left, Center, or Right alignment for every column.
  4. 4Copy the Markdown, or Download table.md for a README, issue, or PR description.
  5. 5If a cell shows a mini JSON blob, that field was nested — flatten upstream if you need separate columns.

Example

Before

[{"lang":"TS","stars":9},{"lang":"Go","stars":8}]

After

| lang | stars |
| :--- | :--- |
| TS | 9 |
| Go | 8 |

With Left alignment the separator uses :---. Center would use :---: and Right ---:. Keys missing on a later row still appear as empty cells under the shared header.

Supported formats

Input
JSON array of objects, or one object
Output
GitHub-flavoured Markdown table (table.md)

Common problems and fixes

  • Invalid JSON on the output status

    Fix trailing commas, single quotes, or truncated paste. The table is not built until parseJson succeeds.

  • Expected a JSON object or an array of objects

    A bare string or number at the root is rejected. Wrap rows in [ … ] or pass one { … } object.

  • Empty array: nothing to convert

    [] has no rows. Add at least one object, or paste a non-empty array.

Benefits

  • Unioned columns

    If row two adds a key row one lacked, that key still appears in the header and earlier rows leave the cell blank.

  • Safe for Markdown pipes

    Literal | characters in data do not break the table because they are escaped before the row is joined.

Common use cases

  • README feature matrix

    Paste a small JSON list of features or versions and drop the Markdown table under a ## section in the README.

  • API response in docs

    Take a trimmed array from an API sample and publish it as a table in internal docs without rebuilding columns in a spreadsheet.

  • GitHub issue inventory

    Paste id / title / owner rows into an issue body so reviewers can scan the list as a table.

  • Changelog comparison

    Convert a JSON list of package / from / to version rows into a Markdown table for the release notes.

Tips & best practices

  • Prefer a flat array of objects. Nested objects become a single escaped JSON string in one cell.
  • Trim huge payloads before pasting; the table is rebuilt on each edit after a short debounce.
  • Use Center only when the rendered preview benefits — many READMEs stay on Left.

Common mistakes to avoid

  • Pasting a raw CSV string. This page expects JSON; convert with CSV to JSON first.
  • Expecting nested objects to become extra columns. They are stringified into one cell.
  • Leaving an empty array [] — the output stays blank with an empty-array notice.
  • Forgetting that newlines inside values are turned into spaces, which can join sentences in a cell.

Frequently asked questions

What happens to nested objects or arrays in a field?

They are JSON.stringify’d into that cell, then pipe-escaped. They do not create child columns. Flatten the JSON first if you need one column per nested key.

Can I convert an array of arrays or primitives?

Non-object items are wrapped as { "value": … }, so you get a single value column. Prefer an array of objects with named keys.

How are pipe characters handled?

Every | in headers and cells is escaped as \| so Markdown table parsers keep the column count stable.

Will a large JSON file work?

Conversion runs in the browser after a short debounce. There is no upload size cap, but very large arrays are limited by memory and will make the Markdown pane heavy to scroll.

What do Left, Center, and Right change?

Only the separator row: :---, :---:, or ---:. All columns share the same alignment choice.

What if rows have different keys?

Headers are the union of all keys, in first-seen order. A row missing a key leaves that cell empty.

Can I start from a single object?

Yes. One object becomes a one-row table. An empty array shows a notice and no Markdown.

Does the table keep multi-line cell text?

No. Newlines inside a cell are replaced with spaces so each Markdown row stays on one line.

When another tool fits better

  • CSV to JSON. Your source is still a spreadsheet export. Convert to a JSON array here first, then return for the Markdown table.
  • JSON Formatter. The paste will not parse, or you need to inspect nested structure before flattening keys for a clean table.
  • JSON to TypeScript. You need interfaces for the same payload, not a Markdown table for docs.

Conclusion

Paste a flat array of objects, pick alignment, and copy a pipe-safe Markdown table for READMEs, issues, and changelogs — without uploading the JSON.

Ready to try JSON to Markdown?

Scroll back up to start now, or continue with another free developer tool.

Guides and glossary

Learn and reference material connected to JSON to Markdown.