How to Export Your Claude Conversations

The no-install option is your browser’s print dialog. Open the conversation, press Ctrl or Cmd+P, and save as PDF. It captures the full thread and costs nothing, which is the entire appeal.

What you give up is control over the result. Claude’s interface elements usually print with the text, and Claude’s longer answers — the whole reason you’re exporting — are the ones most likely to break across pages awkwardly. It’s a fine emergency option for one conversation. It’s not something you’d want to lean on.

The other manual route is to select the conversation and paste it into a document. Quick, but it tends to flatten exactly the structure that made Claude’s answer useful. Headings turn to bold text, nested lists collapse, and code blocks lose their fences on the way over.

You can clean it up by hand, of course. For a short answer that’s a minute; for a detailed plan or a long technical reply it’s a chore, and it’s easy to introduce mistakes while you’re reformatting.

Foldif, a free Chrome extension, adds the export Claude is missing. Open a conversation and you can send it out as a clean PDF, a well-formed Markdown file, an image, or a share link — one click each, with just the content and its formatting intact.

The format you choose depends on where it’s going. PDF for someone who wants a file to read or archive. Markdown when you’re dropping it into notes, a doc, or a repo and want to keep editing. A share link when you just want to point someone at it without sending an attachment. Because it reads the conversation rather than the page, you don’t spend any time fixing the output afterwards.

Share links are worth calling out because they solve a different problem from files. When you just want a colleague to see what Claude said, sending a PDF makes them download something; a link lets them open it and read. The file exports (PDF, Markdown, image) are generated locally, and share links are opt-in, so you decide what leaves your machine.

If your main goal is keeping conversations rather than sending them, start one step earlier — our guide on saving Claude conversations covers filing and searching them, and exporting is always a click away once they’re saved.

Claude gives you more format choices than you strictly need, so a quick rule of thumb helps. Reach for PDF when the conversation is finished and someone just needs to read or keep it — a client, a teacher, your own archive. PDFs are frozen, which is a feature here: nobody’s going to accidentally edit your record of what was said.

Pick Markdown when the conversation is an input to something else. Dropping Claude’s plan into a doc you’ll keep refining, pasting an explanation into your notes, committing a worked solution to a repo — anything where you’ll keep editing the text wants Markdown, because PDF would lock it.

Use a share link when the goal is “let someone see this,” not “give someone a file.” It saves them a download and saves you an attachment, and it’s the fastest way to get a second pair of eyes on what Claude produced. One more thing worth knowing: if a Claude answer includes an artifact — a document or a code canvas Claude rendered separately — export the conversation rather than copying the artifact alone, so the surrounding context comes with it and the result still makes sense later.

If you’re genuinely unsure which format you’ll need, the easy default is to save the conversation first and decide later. Once a Claude chat is saved you can export it as any of these formats on demand, so you’re never locked into a choice you made in the moment — send a colleague a link today, pull a PDF for your own records next week, all from the same saved copy. That order has a side benefit too: you don’t have to break your train of thought to file things. One click to save, and the format question can wait until you actually need the file.