What table format does it expect?

Standard GitHub-flavored markdown — a header row of pipe-separated cells, a separator row of dashes, then one or more data rows. Leading and trailing pipes are optional and handled automatically.

How are escaped pipes handled?

A backslash-escaped pipe inside a cell is treated as literal text, not a column separator, so values like "10 \| 20" stay in one cell and are unescaped in the output.

What happens to inline markdown like bold or links?

Cell text is preserved as-is, so "**Active**" stays "**Active**". This keeps the conversion lossless; strip formatting downstream if you need plain values.

Is my data sent anywhere?

No. Parsing happens entirely in your browser with no network calls, so you can safely convert tables containing private data.

Markdown Table → JSON Converter

Markdown table to JSON

LLMs love returning tabular data as markdown, but markdown tables are awkward to use in code. This tool parses the table syntax — header row, separator, and data rows — and produces a clean JSON array of objects keyed by the header labels, ready to paste into a script, a spreadsheet importer, or a database seed.

How it works

Each line of the input is treated as a table row and split on pipe characters, respecting backslash-escaped pipes inside cells. The first row becomes the set of object keys; the dashed separator row (cells made only of dashes and colons) is detected and skipped. Every subsequent row is zipped against the headers to build an object, with missing trailing cells filled as empty strings and extra cells dropped. Whitespace around each cell is trimmed and escaped pipes are unescaped.

Tips and notes

Include the header row. The keys come from the first row, so paste the whole table — header, separator, and data — not just the body.
Ragged rows are tolerated. Rows with fewer cells than headers get empty strings; rows with more cells are truncated to the header count.
Formatting is preserved. Bold, italics, and links inside cells are kept verbatim so the conversion is lossless.
Everything is local. No data leaves your browser, so converting private tables is safe.