JSON to Markdown Table Converter.
Convert JSON to a GitHub-flavored Markdown table in one click. Escape pipes automatically, align columns, stringify nested JSON, and copy clean Markdown for README files, docs, issues, and pull requests.
No signup · No uploads · Copy or download Markdown
Markdown output
// Paste JSON and press "Convert JSON to Markdown table".
Convert JSON to Markdown table online - free and private
A JSON to Markdown table converter turns structured JSON into copy-ready pipe table syntax for GitHub, GitLab, README files, docs, issues, and static site content. Paste a JSON array of objects above, choose alignment and nested-data options, then copy the generated Markdown table. Everything runs client-side, so your JSON is never uploaded.
How to convert JSON to Markdown table in three steps
- Paste your JSON, ideally a JSON array of objects.
- Choose Markdown options - nested JSON handling, column alignment, optional row numbers, and cell trimming.
- Copy or download the GitHub-flavored Markdown table.
GitHub-flavored Markdown with pipe escaping
Markdown tables use pipes to separate columns, so a value like
Engineer | Writer can break a table if it is not escaped.
This tool automatically escapes pipes as \| and converts
line breaks to <br>, producing safer
GitHub-flavored Markdown table output.
Column alignment and nested JSON handling
Choose auto, left, center, or right alignment. Auto mode detects numeric columns and right-aligns them with Markdown separator markers. For nested JSON, use stringified cells for compact docs, flatten nested objects into dot-notation columns, or join arrays into readable values.
What you get
A JSON array becomes a GitHub-flavored Markdown table:
| id | name | role |
| -- | ----- | ----- |
| 1 | Ada | admin |
| 2 | Alan | dev |Paste that into a README, a pull request description, an issue comment, or your docs, and it renders as a real table. No HTML, no screenshots — just text that stays diffable in git.
The pipe problem — why hand-written tables break
Markdown uses the pipe character to separate columns. So a value that contains a pipe terminates the cell early and shatters the entire table's alignment — a row that should have two columns suddenly renders as three, and every row below it is misaligned.
The pipe has to be escaped with a backslash. This is the single most common way Markdown tables get mangled, and it is handled automatically here. It bites hardest with shell commands, regular expressions, and TypeScript union types — all of which are full of pipes.
Column alignment
Markdown encodes alignment in the separator row, using colons:
| Name | Qty | Price |
| :---- | --: | :---: |
| Cable | 12 | 3.00 |Left, right, then centre. Right-align your numeric columns. It costs nothing and makes a table of figures dramatically easier to scan, because the digits line up by place value.
Where these tables render
GitHub, GitLab, Notion, Obsidian, Slack, and virtually every static site generator. One caveat worth knowing: tables are not part of the original Markdown specification — they are a GitHub-Flavored Markdown extension — so a strictly CommonMark renderer may show the raw pipes instead. In practice, almost everything supports them.
Why use this JSON to Markdown table tool?
It is private, fast, and built for docs workflows. Use it to turn API samples, changelog data, config lists, package metadata, or analytics exports into clean Markdown. Need web markup instead? Try JSON to HTML Table, or use JSON to Table for sortable previews. Learn more in our guide on how to convert JSON to Markdown table.
FAQ
JSON to Markdown table, answered.
How do I convert JSON to Markdown table online? +
Paste a JSON array of objects into the JSON to Markdown table converter and press Convert JSON to Markdown table. The tool turns object keys into column headers, rows into GitHub-flavored Markdown table rows, and gives you copy-ready Markdown.
Does this generate GitHub-flavored Markdown tables? +
Yes. The output uses standard GitHub-flavored Markdown table syntax with a header row, separator row, and pipe-delimited body rows, so it works in GitHub README files, issues, pull requests, docs, and many static site generators.
Can it escape pipes in Markdown table cells? +
Yes. Pipe characters inside JSON values are escaped automatically as \| so they do not split a cell into extra columns. Line breaks are converted to <br> so multiline values stay inside the same Markdown table cell.
Can I control Markdown table column alignment? +
Yes. Choose automatic alignment, left, center, or right. Auto alignment right-aligns numeric columns and left-aligns text columns by generating the correct separator markers such as :---, :---:, and ---:.
How are nested JSON objects and arrays handled? +
Nested objects and arrays can be stringified into cells, flattened into dot-notation columns, or joined for compact output. Stringifying nested JSON is often the safest option for GitHub-flavored Markdown tables.
Is my JSON uploaded when converting to Markdown? +
No. The JSON to Markdown table conversion happens entirely in your browser. Your data is never uploaded, stored, logged, or seen by any server.
How do I make a Markdown table from JSON? +
Paste a JSON array of objects and the tool builds a GitHub-flavored Markdown table — a header row from your keys, a separator row, and one row per record. Copy it straight into a README, a pull request description, an issue comment, or any documentation that renders Markdown.
What happens if my data contains a pipe character? +
It gets escaped to \|, which is essential — an unescaped pipe inside a cell terminates the column early and shatters the whole table's alignment. This is the single most common way hand-written Markdown tables break, and it is handled automatically here.
Can I control column alignment? +
Yes. Markdown encodes alignment in the separator row using colons: :--- is left, :---: is centre, and ---: is right. Right-aligning numeric columns makes a table far easier to read, and the tool writes the correct separator syntax for you.
Does the Markdown table work on GitHub, GitLab, and Notion? +
Yes. The output is GitHub-flavored Markdown, which GitLab, Notion, Obsidian, Slack, and most static site generators all support. Note that tables are not part of the original Markdown specification — they are a GFM extension — so a very old or strictly CommonMark renderer may not display them.