How to Export Google Gemini Conversations to Markdown

When you select and copy a Gemini answer, your browser takes the rendered HTML rather than the Markdown source behind it. Your editor then converts that HTML back to Markdown as best it can, and structure gets lost in translation — nested lists collapse, tables fall apart, and headings frequently come through as plain bold text.

Code blocks are the most frustrating part. They look fine in Gemini, but a straight copy often drops the triple-backtick fences and the language hint, leaving your snippet as a plain blob you have to re-fence yourself. For anything code-heavy, that’s the one thing you most needed to keep.

The clean route is to export rather than copy. Foldif, a free Chrome extension, adds Export → Markdown to Gemini. One click produces a single, well-formed .md file with both your prompts and Gemini’s replies, and the headings, lists, and fenced code blocks kept intact along with their language hints.

Because it reads the conversation’s structure instead of scraping the rendered page, the output drops straight into your notes or a repo without a formatting cleanup pass. No re-fencing code, no rebuilding lists, no stitching the thread back together message by message.

There’s a reason not to leave this for “later” with Gemini specifically. Unlike ChatGPT or Claude, Gemini stores your conversations in your Google account under Gemini Apps Activity, where they follow your auto-delete setting — possibly being removed after 3, 18, or 36 months without any notification.

So exporting a Gemini chat to Markdown isn’t only about reusing it; it’s also how you make sure the conversation is still around to reuse. If keeping your chats safe is the bigger worry, our guide on saving Gemini conversations goes into that side, including how a saved copy sidesteps auto-delete entirely.

Sometimes adding an extension isn’t an option — a locked-down work machine, a shared computer, a one-off you don’t want tooling for. You can still get usable Markdown out of Gemini, it’s just more hands-on. The trick is to lean on Gemini’s own per-message copy where it exists, which copies closer to the source than a raw drag-selection, then paste into a Markdown-aware editor rather than a plain text box.

For a whole conversation, work one message at a time: copy your prompt, then Gemini’s reply, into the editor in order, and check the code blocks landed with their fences. It’s tedious, and long threads are where it gets painful, but for a single important answer it’s perfectly workable. Paste into something that understands Markdown — Obsidian, a VS Code .md file, a Notion page — so you can see immediately whether the formatting survived and fix it while the original is still in front of you.

If the formatting arrives badly mangled anyway, a fallback is to paste into a Markdown editor, repair it there once, and save that file as your clean copy. It’s more effort than a one-click export, but it gets you a real .md file without installing anything — and if you find yourself doing it more than occasionally, that’s the signal the export route would pay for itself.

Markdown is the pick when you’ll keep working with the text. If you’re handing the conversation to someone who just wants to read it, a PDF is friendlier — our guide on exporting Gemini to PDF covers that. And for a quick share, a link skips the file entirely.

In Foldif it’s all one menu: Markdown, PDF, image, or link. Pick whichever matches where the Gemini conversation is actually going, from a single saved copy.

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.

For developers, the win is dropping a Gemini conversation straight into a repo — a debugging thread sits happily in a /docs folder or an issue, with the code still fenced and highlighted, exactly as you saw it. That only works if the export kept the fences, which is the part copy-paste tends to wreck. One gotcha worth knowing: some editors render Markdown tables a little differently, so a table Gemini drew may need a quick glance after pasting — the data survives, the column alignment might not.