Drop a .json file, get clean Markdown back. Free, in-browser, no sign-up. Nested objects become headings and lists, so the output reads like a document instead of a wall of braces.
JSON is great for machines and painful for humans to read at scale. Converting JSON to Markdown turns API responses, config files and structured exports into a readable document — perfect for documentation, code review, or feeding to an LLM that handles narrative better than nested braces.
t0md walks the JSON tree and emits Markdown: object keys become headings, primitive values become text, arrays become bullet lists. Deeply nested structures use heading depth to match nesting, so the document reads top-to-bottom in the original order.
t0md exposes a remote MCP (Model Context Protocol) server. Add it once and any MCP-compatible agent can convert JSON to Markdown without leaving the conversation.
claude mcp add --transport http t0md https://t0md.com/mcpThen ask the agent: "convert /path/to/api-response.json to markdown". The MCP server returns the converted Markdown plus a 10-minute download link. Full setup details on the MCP page.
Drop your .json file on this page (or click to choose). t0md walks the structure and emits Markdown. Copy or download as a .md file. No sign-up.
Object keys become headings, primitive values become text, arrays become bullet lists. Deeply nested keys use deeper heading levels. The result reads as a document, not a code block.
No, by default the JSON is restructured into Markdown prose. If you want the raw JSON pretty-printed inside a fenced code block, that's a single-line manual paste — let us know if you'd like a toggle for it.
Yes. Add the t0md MCP server (`claude mcp add --transport http t0md https://t0md.com/mcp`) and Claude Code, Cursor, or any MCP-compatible agent can call convert_to_markdown on any .json file directly.
25 MB per upload. JSON is very compact, so this is rarely a constraint. Files are processed in memory and discarded after conversion.