How to Save Google AI Mode Conversations to PDF

A normal Google search result is a URL — you can bookmark it, share it, and come back to it. AI Overviews, the summary boxes that appear above regular results, are already hard to pin down because they regenerate on every search.

AI Mode is a different beast entirely:

• It is a conversation, not a page. You ask follow-up questions in a running thread, so there is no single URL that captures the whole exchange.
• The thread can include images, tables, and source cards woven into the answers, not just text.
• Google does not expose a public API for AI Mode that you could use to pull a conversation out after the fact.
• Nothing survives a refresh. The conversation state lives in the page session, not in a retrievable history.

That last point is why screenshots and copy-paste fail so badly here. A long AI Mode thread scrolls across several screens, the images shrink to thumbnails, and the sources become unreadable. You end up with fragments — and no record of the questions that produced them.

Only the last method produces a real document that records the questions, the answers, the images, and the sources in one file.

Screenshots feel like progress, but an AI Mode answer routinely runs longer than one screen. The scrolling screenshot tools stitch fragments together and mangle tables and source cards. The citation links — the entire point of saving a research answer — become flat images you can’t click. And if the answer includes an image or a chart, it’s usually cut off or tiny.

Select the text, paste into Google Docs or Word, export PDF. This keeps the prose but destroys everything that makes an AI Mode answer useful: the layout, the source chips, the images, and the mapping between a claim and where it came from. It also requires manual bookkeeping — you have to remember which question each paragraph answered.

Press Ctrl+P (Windows) or Cmd+P (Mac) and save to PDF. The print stylesheet was never built for a conversational thread. Long answers clip mid-sentence, images fall out of the flow, and the organic search links print alongside your AI answer whether you want them or not.

Step 1 — Install XWX AI Chat Exporter. Search for it in the Chrome Web Store and click Add to Chrome. No account, no signup, nothing to configure.

Go to google.com/aimode, type your question, and build your thread with follow-ups. Ask as many questions as you need — the export captures the entire conversation, not just the last answer.

The value of AI Mode is the follow-up chain. Each question refines the previous one, and each answer carries its own sources. Keep the thread open — everything you see here is what the export will preserve.

Click the floating XWX button in the bottom-right corner of the AI Mode page, then choose PDF. The extension reads the live conversation — every turn, image, and source — and renders it into a print-ready document.

The PDF is a faithful record of the conversation:

• Your query written in the document header, so the file says what you asked
• Every turn of the AI Mode thread, in order — no clipped answers
• Images and charts from the answers, rendered in place
• Source references kept where they appear, with titles, domains, and links
• Search timestamp recorded in the metadata

PDF is for keeping and sharing. But the same AI Mode thread can also become:

• Markdown — dropped straight into Obsidian or Logseq with the query in YAML frontmatter
• Word (.docx) — for editing and folding into a report
• Notion — pushed into your workspace as a structured page

This matters if you research across multiple sessions: the file format determines whether your saved answers become part of a searchable knowledge base or just another folder of documents.

• Export before you refresh. AI Mode state lives in the page. Once you navigate away, that exact thread is gone.
• Let images load fully before exporting — an answer that’s still lazy-loading may export placeholders.
• Keep the tab open while the PDF renders. The export reads the live conversation, so switching tabs mid-export can interrupt it.
• Export in long sessions in one go. A very long thread exports faster and more reliably as a single PDF than as several short ones.