Comments URL: https://news.ycombinator.com/item?id=49653422

Points: 3

# Comments: 0

Good extension.

Code blocks collapse into plain text. Tables fall apart. Bold and italic disappear. I went through every option available and documented exactly what breaks and what doesn't.

1. Manual copy-paste (everyone's default)

Paste into Word: gray backgrounds, broken tables, lost structure.

Paste without formatting (Ctrl+Shift+V): bold, code, tables — all gone.

Either way, formatting loses.

2. Print to PDF (Ctrl+P → Save as PDF)

Exports the entire browser UI — menus, avatars, input box included.

Long code blocks get cut mid-page. Looks nothing like a clean document.

3. Gemini's built-in "Export to Docs" button

Only exports single responses, not the full thread.

Useless for long research sessions. Tables still shift on complex layouts.

4. Share link

Creates a read-only public URL — not a file.

Doesn't solve the export Gemini chat to document problem at all.

5. Google Takeout

Exports full history as raw HTML or JSON.

Technically complete, practically unreadable for day-to-day work.

6. Chrome extension (the only one that actually works)

After going through all of the above, I built Gemini Exporter — a Chrome extension that exports Gemini chat to Word, PDF, Google Docs, or Notion while preserving everything: code blocks, tables, headings, math notation, full conversation structure.

One click. Nothing leaves your browser for Word and PDF exports.

More info: https://backrun.co/gemini-exporter

The main problem I ran into was that copying content from Gemini into documents was more tedious than it should be. Long chats, lists, code blocks, and structured answers often needed cleanup before they could be shared or reused.

So I made a tool that lets you export either selected messages or an entire Gemini chat in a few clicks. The output can be saved as PDF, Word DOCX, Google Docs, or Notion, depending on what you want to do next.

I also added a few basic formatting controls like font family, font size, and text color, since I often wanted exports to look a bit more consistent before sending them to someone else or keeping them as internal notes.

A few workflows I had in mind:

- exporting a full Gemini thread to PDF for sharing or archiving

- turning Gemini output into an editable Word document

- sending a conversation to Google Docs for collaboration

- moving useful chats into Notion for documentation or knowledge management

The extension supports both partial export and full-thread export, so it works whether you want to save a small part of a conversation or need a gemini export entire chat workflow without copy-paste.

>> Website: https://backrun.co/gemini-exporter >> Chrome extension: https://chromewebstore.google.com/detail/gemini-exporter-save-gemi/lgipeakgdkcgnkdljeagconfbfeolidj

I’d love feedback on:

- formatting quality for longer conversations

- handling of code blocks, lists, and headings

- which export destination is most useful in real workflows

Comments URL: https://news.ycombinator.com/item?id=47345280

Points: 4

# Comments: 0

Gemini Exporter came from the exact same frustration, so it is great to hear it helped you. For anyone who wants to try it, here is the extension: https://chromewebstore.google.com/detail/gemini-exporter-sav...

Really appreciate the support, and I would love to hear any feedback as you keep using Gemini Exporter, especially on longer chats or code-heavy conversations.

For DOM changes, I try not to couple the parser too tightly to fragile selectors. The extraction layer leans more on structural patterns in the rendered chat tree, and I keep the export pipeline separate from the Gemini-specific parsing so I can update that layer without rewriting the whole exporter.

For tricky formatting cases:

nested markdown is normalized into an intermediate representation first, then mapped to Word, PDF, Google Docs, or Notion

code blocks are preserved as their own block type so they do not get flattened into regular paragraph text

large tables are probably the weakest area right now, especially when Gemini renders them inconsistently or with wrapped cells

I am also building a small regression set from real chats, so when Gemini changes something in the UI I can catch breakage faster instead of fixing issues one by one.

Still early, so I would not claim every edge case is solved yet. The goal is to fail gracefully: preserve the content first, then keep as much structure as possible.

If you have a nasty sample with nested markdown, wide tables, or code-heavy output, I would genuinely love to test against it.