JSON to Markdown Table

Why convert JSON to a Markdown table?

Markdown tables are the standard way to present structured data in GitHub, GitLab, docs sites, and static blogs — but writing the pipes and dashes by hand is tedious and error-prone. Pasting a JSON sample and getting a formatted table instantly saves time when documenting an API response, a config, or a dataset.

How the table is built

For an array of objects, the columns are the union of every object's keys (in first-seen order) and each object becomes a row. Missing keys render as empty cells, nested objects and arrays are shown as compact JSON, pipe characters are escaped, and newlines are converted to <br> so cells stay on one line.

• Header from the union of keys across all rows
• One row per object; missing keys become empty cells
• Pipes escaped, newlines converted to <br>
• Single object renders as a key/value table

Where it fits

Drop the output straight into a README, a PR description, a GitHub issue, or any Markdown-aware editor. Because GitHub-Flavored Markdown is widely supported, the same table renders in Notion, Obsidian, Slack previews, and most static-site generators.

Tips for clean tables

Markdown tables work best with flat rows, so flatten deeply nested JSON first (try the JSON Flattener) or pick the fields you care about. For very wide data, consider fewer columns — Markdown tables don't scroll, so narrow, focused tables read better.