JSON to Markdown Table Converter

What it does

API responses, exports and configuration often come as JSON, but a table is much easier to read in a README, a pull request, a wiki page or a chat message. This tool turns a JSON array of objects into a GitHub Flavored Markdown table that renders on GitHub, GitLab, Notion, Obsidian and most documentation sites.

Each object becomes a row and each key becomes a column. Nested objects are flattened into dotted column names, pipes and line breaks in values are escaped, and the columns are padded so the raw Markdown lines up too.

How to use it

1. Paste JSON, upload a .json file, or click Sample.
2. Choose the Alignment: default, left, center, right, or Numbers right to right-align columns that contain only numbers.
3. Keep Flatten nested objects on to spread nested fields over columns, or turn it off to show them as JSON.
4. Switch off Align columns if you prefer compact rows without padding.
5. Copy the table or download it as a .md file.

If the JSON is invalid, the error shows the line and column so you can fix it quickly.

Example

This JSON:

[
  { "name": "ripgrep", "stars": 48000, "repo": { "owner": "BurntSushi" } },
  { "name": "fd", "stars": 34000, "repo": { "owner": "sharkdp" }, "tags": ["find"] }
]

becomes this Markdown table:

| name    | stars | repo.owner | tags     |
| ------- | ----- | ---------- | -------- |
| ripgrep | 48000 | BurntSushi |          |
| fd      | 34000 | sharkdp    | ["find"] |

The nested repo object becomes a repo.owner column, the tags array is written as JSON, and the first row gets an empty cell because it has no tags.

Tips

• Values are written as text: numbers and booleans appear as they are, and null becomes an empty cell.
• Very wide tables are hard to read; remove fields you do not need before converting.
• Inline Markdown in string values, such as **bold** or links, is kept and rendered by most viewers.
• For CSV data, or to produce an HTML table instead, use the related tools below.