Step 1 / source
Choose the source
Drop one file here
Choose the one markdown table you want to turn into json record array.
Checking publication status...LOCAL TABLE CONVERTER / MARKDOWN TABLE TO JSON
Markdown Table to JSON
Convert exactly one rectangular Markdown table into a JSON record array with explicit empty-cell handling.
Processed in this browserOne UTF-8 .md or .markdown file up to 5 MB containing one table with up to 50,000 data rows, 200 columns, 1,000,000 cells, and 20 MB output.
MD - one record table
No file upload
This operation runs with browser APIs. Nirmion receives catalogue requests, not the selected source bytes.
Original stays unchanged
The converter creates a separately named output. It never writes back into the source file.
Bounded work
One UTF-8 .md or .markdown file up to 5 MB containing one table with up to 50,000 data rows, 200 columns, 1,000,000 cells, and 20 MB output.
Plain-language method
How Markdown Table to JSON works
Nirmion validates one header and delimiter row, parses escaped pipes and backslashes, decodes generated HTML entities and br line breaks, normalizes duplicate headers safely, maps each data row to an object, and serializes one JSON array.
- 01Choose a valid source
Provide only the table. Every data row must contain the same number of cells as the header.
- 02Review the conversion choices
Omit removes blank properties; Null keeps a stable shape. Every non-empty cell remains a JSON string.
- 03Inspect the separate result
The result ends in _nirmion_tools.json. Markdown alignment and inline formatting syntax are not data types.
Useful when
Practical jobs this tool handles
- Turn documentation tables into API fixtures.
- Move a maintained matrix into application data.
- Review table records with JSON tooling.
Before converting
Check the source and destination rules
- Check escaped pipes and row widths.
- Choose the empty-cell contract.
- Convert numbers explicitly downstream if required.
Know the boundary
Know what the destination format cannot keep
The tool parses table source rather than rendering Markdown. Inline links, emphasis, and code markers remain literal text, and scalar types are not guessed.
Quick answers
Questions before you convert
The conversion contract is deliberately explicit.
Why are numbers strings?
Markdown tables do not declare reliable data types.
What happens to duplicate headers?
Stable suffixes prevent overwritten properties.
Can prose surround the table?
No. Requiring exactly one table prevents accidental extraction from unrelated content.