Convert Markdown to JSON
Convert Markdown to JSON in your browser: load your Markdown, choose JSON as the target, and download the result. The converter reports exactly what it could not carry across, and nothing is uploaded to a server.
Convert Markdown to JSONRuns in your browser. Nothing uploaded.
When you need this
Pulling the tables out of documentation into data — a pricing table into a config, a matrix from a spec into fixtures, a checklist into something a script can iterate. The useful framing is extraction, not conversion.
How to convert Markdown to JSON
- Load your Markdown
- Drag the .md file in, or paste just the table you want. There is no need to strip the surrounding prose — only the tables are read. Nothing leaves your browser at this or any later step.
- Choose the target format
- Press Ctrl+Shift+K (Cmd+Shift+K on a Mac) to open the conversion panel, then pick JSON as the target. The source and the result sit side by side.
- Read the loss report
- The panel shows whether the conversion is lossless for your particular data, and lists every value it had to transform. Adjust indentation, key sorting and null handling if you need to.
- Take the JSON
- Download the .json file, copy it, or open it as a new tab to keep working on it in the JSON views.
What survives the conversion
Markdown to JSON cannot be lossless, because the two formats express different things. Converts the tables to arrays of objects; the rest of the document is not represented.
- Only the tables are converted. Prose, headings, lists and code blocks have no place in an array of objects and are not represented — this is the caveat to read first, because it is the one that surprises people.
- Each table becomes an array of objects keyed by its header row.
- A document with several tables produces several arrays. A document with none produces nothing, and the converter says so rather than returning an empty array as though the input had been empty.
A worked example
A table extracted; the heading and prose around it are not:
## Limits
Some prose.
| key | max |
| --- | --- |
| size | 50 |[
{
"key": "size",
"max": "50"
}
]Privacy
The conversion runs in your browser — in a Web Worker for anything above a quarter of a megabyte, so the page stays responsive. Your data is not uploaded, not logged and not stored. There is no account, and the whole thing works offline.
Questions
Where did the rest of my document go?
It was not converted, and that is by design rather than an omission. A heading, a paragraph and a fenced code block have no representation in an array of objects — anything invented for them would be noise you then had to filter out. Only the tabular parts of a document are tabular data.
Is converting Markdown to JSON lossless?
No, and no tool can make it so. Converts the tables to arrays of objects; the rest of the document is not represented. The converter lists every affected value rather than silently dropping it.
Is my Markdown uploaded to a server?
No. The file is read and converted by your browser. Nothing about its contents is sent anywhere, which you can verify in your browser’s network panel or by using the tool with the network disconnected.