Chat to Markdown
Paste a Claude / Grok conversation — or an exported JSON — and get clean Markdown with speakers labeled, code blocks intact, clutter removed.
Advertisement
Why convert chats to Markdown?
Chat UIs are built for chatting, not for keeping. The moment a conversation becomes documentation, a blog draft, or a bug report, you want plain Markdown: speakers clearly labeled, code blocks intact, no UI chrome, no timestamps. Paste it into Notion, GitHub, or your notes app and it just works.
What gets cleaned up
Speaker labels (Human:, You:, Grok:, Assistant:…) become ### headings. Timestamps like [10:23] or 2026-10-01 10:23 are stripped. Runs of blank lines collapse to one. Fenced code blocks pass through untouched.
FAQ
Which chat formats are recognized?
Pasted text with speaker labels (
Human:/Assistant:, You:/Grok:, User:/Assistant:), plus exported JSON with a messages array using role/content, sender/text, or author/message fields.Are code blocks preserved?
Yes — fenced blocks (
```) pass through untouched with their language tags, and inline code survives too.What if my JSON export has a different shape?
The tool searches the top level and common wrapper keys (
data, conversation, messages). If nothing matches, it falls back to plain-text parsing.Does my chat content leave my browser?
No. Conversion happens entirely in JavaScript on your device. Nothing is uploaded anywhere.
Advertisement