How to Export Claude Conversations to Markdown

When you select an answer and copy it, your browser grabs the rendered HTML — the formatted version on screen — not the Markdown source behind it. Your editor then has to guess how to turn that HTML back into Markdown, and it guesses badly. Nested lists collapse, tables come apart, and headings often arrive as plain bold text.

Code is the worst casualty. A fenced code block looks perfect in Claude, but a straight copy frequently drops the triple-backtick fences and the language hint, so your snippet lands as an undifferentiated blob you have to re-fence by hand. For the code-heavy answers Claude is good at, that’s exactly the part you can’t afford to lose.

Claude’s own copy button under a message does better than a raw text selection, because it copies closer to the original Markdown. If you only need one answer, that’s the move: click it, paste, done.

It still leaves you assembling the conversation yourself, though. You copy one message, then the next, then your prompt, and stitch them together in order. For a single reply that’s nothing; for a whole thread you want to keep, it’s fiddly busywork that’s easy to get wrong — and it does nothing for the back-and-forth that often holds the real answer.

The clean route is to export the conversation rather than copy it. Foldif, a free Chrome extension, adds Export → Markdown to Claude. One click gives you a single, well-formed .md file with both sides of the thread — your prompts and Claude’s replies — and headings, lists, and fenced code blocks preserved, language hints still attached.

It reads the conversation’s structure instead of scraping the rendered page, which is why the output drops cleanly into Obsidian or a README without a cleanup pass. No re-fencing code, no rebuilding lists, no reassembling the thread by hand.

Claude has one wrinkle the other AIs don’t: Artifacts. When Claude produces a document or a code canvas as a separate panel, that content lives a little apart from the chat bubbles. If you copy only the Artifact, you get the code or document but lose the surrounding conversation — the reasoning, the corrections, the “actually, change this” that gave it meaning.

When you export the conversation rather than grabbing the Artifact alone, the surrounding context comes with it, so the Markdown still makes sense weeks later. If an Artifact went through several revisions, exporting the thread keeps that trail intact instead of leaving you with a final blob and no memory of how it got there.

Clean Markdown matters because of what you do with it next, which is almost always pasting it somewhere specific. In Obsidian or a plain notes vault, an exported .md file just becomes a note — headings, links, and code already formatted, ready to link to your other notes. In Notion, pasting Markdown converts into proper blocks, so a code fence becomes a real code block instead of grey text you’d have to reformat.

For developers, the payoff is dropping a Claude conversation straight into a repo. A debugging thread or a planned refactor exported as Markdown sits happily in a /docs folder or a pull request, with each code block still fenced and its language intact, so a teammate reads it the way you saw it. That’s exactly the part a raw copy-paste tends to destroy, which is why the export route is worth the small setup.

A couple of gotchas are worth knowing. Some editors render Markdown tables a little differently, so a table Claude drew may need a quick glance after pasting — the data survives, the column alignment might not. And if you paste into something that doesn’t speak Markdown at all, like a plain email client, you’ll just see the raw # and * characters; in that case export to PDF instead, or paste into a Markdown-aware app first and copy the rendered version from there.

Markdown is the right pick when you’ll keep working with the text. If you’re instead handing the conversation to someone who just wants to read it, a PDF is friendlier — our guide on exporting Claude conversations covers PDF and the other formats. And for a quick “look at this,” a share link beats sending any file at all.

In Foldif these are all the same menu: Markdown, PDF, image, or link. Save the conversation once and export it however the moment calls for — and if you mostly just don’t want to lose it, our guide on saving Claude conversations starts one step earlier.