TL;DR
Gemini has a built-in export, but it only sends single responses to Google Docs — not the whole thread. For a full conversation as a PDF, the two reliable options are Chrome's Ctrl+P print dialog (works, sometimes clips code blocks) or a dedicated extension like Convert: Web to PDF that captures the whole scrollable page as a single file. Screenshot stitching is the fallback when nothing else works. Pick by length: short chats print fine, long ones need an extension.
Method 1: Gemini built-in export
Gemini has an export button, but calling it a "chat export" oversells it. What it actually does is send one response at a time to Google Docs or Gmail — not the conversation.
To use it:
- Open your Gemini conversation at
gemini.google.com - Hover over any response — a share icon and a three-dot menu appear
- Click the share icon → Export to Docs (or Draft in Gmail)
- Once the response is in Docs, use File → Download → PDF Document (.pdf)
That works well for a single answer you want to file away or share. It falls apart for anything else:
- No thread export. Your prompts don't come along. Neither do the surrounding responses. You get one Gemini answer, floating without context.
- No batch mode. If you want the whole conversation, you're exporting each response one by one, then manually pasting them into a Doc in the right order with your own prompts sandwiched between. For a 20-turn conversation that's an hour of copy-paste.
- Images sometimes drop. Generated images and image inputs are hit-or-miss in the Docs export. Diagrams from Gemini's canvas feature usually make it; inline generated images sometimes don't.
- Code blocks lose their frame but keep their monospace font. Syntax highlighting is gone. Long lines wrap unpredictably.
Google's own documentation on the export feature confirms the single-response scope — they call it "share and export a specific response," and there's no bulk option in the roadmap that they've announced.
When to use it: you want to keep one specific answer, edit it lightly, and share it. Not for archiving a conversation.
Method 2: Ctrl+P > Save as PDF
Chrome's built-in print dialog is the most obvious answer, and for short chats it works fine. Hit Ctrl+P (or Cmd+P on Mac), pick Save as PDF as the destination, and click Save.
What you get:
- The entire visible conversation in one PDF
- Your prompts and Gemini's responses in the correct order
- Reasonable text formatting
What you don't get, or get badly:
- Code blocks often clip. Wide code lines get cut off at the right edge of the page rather than wrapping. This is Gemini's CSS, not Chrome — the
preblocks haveoverflow-x: autoand print doesn't force wrap. You'll lose the ends of long lines. - Some inline UI leaks in. The composer at the bottom, the sidebar, and the "New chat" buttons sometimes render into the PDF depending on your zoom level and window width.
- Very long threads may only partially render. Chrome has to lay out the whole page for print. If Gemini uses virtualized scrolling on a 100+ turn conversation (it does for very long ones), messages that haven't been scrolled into view can be missing from the PDF entirely.
- Dark mode = bad PDF. If Gemini is in dark mode, you get white text on a black background, which uses a lot of ink and looks terrible. Switch to light mode first.
Two tweaks that help:
- In the print dialog, click More settings and turn Background graphics ON. Otherwise the message backgrounds vanish and you lose the visual distinction between your turn and Gemini's turn.
- Set Scale to about 80% — this shrinks the layout enough that most code blocks fit without clipping.
For a longer walkthrough of when the print dialog is enough and when it isn't, we compared it to extensions in Chrome Print to PDF vs Extension.
Method 3: Convert: Web to PDF
For anything longer than a page or two, or anything with code, the print dialog isn't reliable. This is where a purpose-built extension earns its place. Convert: Web to PDF captures the entire scrollable page — every message in the thread — into a single PDF.
The mechanic that makes this work: instead of asking the browser to lay out the whole page for print (which Gemini's UI fights), the extension programmatically scrolls the conversation from top to bottom, waits for content to load, and stitches the rendered output into a PDF. This works around the virtualized-scrolling problem that eats messages in Ctrl+P mode.
Steps:
- Install the extension from the Chrome Web Store
- Open your Gemini chat and scroll to the top (this helps the extension get the full context)
- Click the extension icon
- Choose Full page as the capture mode
- Save
What you get with an extension approach that you don't get with Ctrl+P:
- Full conversations, including virtualized parts — the scroll-and-stitch pass forces every message to render
- Code blocks stay intact — the extension captures the rendered DOM including code frames, syntax colors, and copy buttons (though the copy button itself is inert in a PDF)
- Images preserved — both your uploaded images and Gemini's generated images render as they appear on screen
- No sidebar or composer leakage — good extensions detect and hide fixed-position UI chrome before capture
Trade-offs to know:
- Not instant on long chats. A 50-turn conversation with images can take 20-40 seconds to capture.
- Local processing. The extension does the work in your browser rather than uploading your chat to a server, which is the point — but it also means the capture is bound by your device's memory. Very long chats (200+ turns) may hit browser limits.
- You still want light mode. Dark mode captures cleanly but produces the same ink-heavy PDF as the print dialog.
For the general case of any long webpage, we go into more depth in How to Save a Webpage as a PDF.
Method 4: Screenshot stitch
The fallback for when everything else fails or when you specifically need images (not text) — for example, you're archiving a design conversation and the visual layout of Gemini's responses matters as much as the words.
Options:
- Built-in browser screenshot. Chrome DevTools has a "Capture full size screenshot" hidden in the command menu (
Cmd+Shift+PorCtrl+Shift+Pinside DevTools). It captures the whole scrollable page as a PNG. Convert to PDF after. - macOS
Cmd+Shift+5for regional or window screenshots, then combine in Preview. - A screenshot stitching extension for Windows.
Then either:
- Import the PNG into Preview (Mac) or Photos (Windows), then File → Export as PDF
- Or use a converter like Convert Anything to PDF to turn the image file into a PDF
Why anyone would choose this: sometimes the DOM-based capture methods (both Ctrl+P and extensions) misrender something subtle — a math formula, a hand-drawn Gemini diagram — and a pixel-perfect screenshot is the only way to get the exact appearance.
Why it's a fallback: the resulting PDF is not searchable text, it's an image. You can't copy anything out of it, screen readers can't read it, and file sizes get big fast.
Common problems (missing code, cut-off content)
A few things go wrong often enough to call out:
Code blocks missing or clipped. Almost always the print dialog with wide lines. Fixes: switch to an extension, or in Ctrl+P set scale to 70-80% and turn on Background graphics. Very long code responses (over ~200 lines) are the hardest — even extensions can end up with awkward page breaks. Copy the code out separately into a text file if the exact code is what matters.
Missing messages in the middle of a long conversation. Gemini virtualizes messages that scroll far off-screen. The print dialog captures only what's currently in the DOM. Fix: scroll from top to bottom of the conversation first (which forces Gemini to render everything), then immediately hit Ctrl+P or run the extension. Do not scroll back to the bottom before printing.
Composer, sidebar, or "New chat" buttons in the PDF. These are fixed-position elements. Options: use an extension that suppresses fixed UI, or use Chrome's DevTools to display: none those elements before printing (right-click → Inspect, find the element, delete it — it comes back on reload).
Images not appearing. For uploaded images, they usually render. For Gemini-generated images, sometimes the image is loaded via a signed URL that expires. If the export is slow enough that the URL expires mid-capture, the image slot renders blank. Fix: run the export immediately after the images generate, or right-click each image and "Save image as" first.
Formatting looks broken. Gemini's response formatting (headers, bullets, tables) uses standard HTML. It should render fine. If tables come out messy, it's usually because the table is wider than the page — landscape orientation in the print dialog fixes most cases.
PDF is huge. Long conversations with images can produce 20-50 MB PDFs. If you need to share, use a PDF compressor after — the Convert Anything to PDF extension can also flatten and reduce output on export.
Comparison table
| Method | Full thread | Code blocks | Images | Speed | Best for |
|---|---|---|---|---|---|
| Gemini built-in export | No (one response) | Partial | Unreliable | Fast | Filing one answer |
Ctrl+P Save as PDF | Short threads only | Often clipped | Yes | Fast | Quick save, short chats |
| Convert: Web to PDF | Yes | Yes | Yes | Medium | Any real conversation |
| Screenshot stitch | Yes | Yes (as image) | Yes | Slow | Visual fidelity, unusual layouts |
The pattern most people land on: use the built-in export when you want a single answer in Google Docs, use Ctrl+P for anything under a screen or two, install an extension the first time you need to save something longer.
Frequently asked questions
Does Gemini have a built-in PDF export?
Not directly. Gemini has an Export to Docs feature that sends a single response to Google Docs, from which you can then download as a PDF via File → Download → PDF Document. But there is no built-in option to export a full conversation, and no bulk mode for exporting multiple responses at once. Every method that captures a full Gemini thread as a PDF uses either the browser's print dialog, a browser extension, or screenshot stitching — Gemini itself does not offer that feature as of August 2026.
How do I save a long Gemini conversation as PDF?
Scroll from the top to the bottom of the conversation first — this forces Gemini to render every message (it virtualizes messages that are far off-screen). Then use an extension like Convert: Web to PDF that captures the full scrollable page. The Chrome Ctrl+P dialog often misses virtualized messages in long threads. If the conversation is over 100 turns, expect the capture to take 20-40 seconds and produce a file in the 10-30 MB range depending on images.
Why is my Gemini PDF missing code formatting?
Two causes. First, the built-in Docs export strips syntax highlighting and the code block frame — Docs doesn't have a native equivalent, so you get monospaced plain text. Second, the Chrome print dialog often clips wide code lines because Gemini's pre blocks use horizontal overflow that print doesn't force-wrap. Fixes: for the print route, set the scale to 70-80% and enable Background graphics; for full fidelity, use an extension that captures the rendered DOM; for exact code preservation, copy the code separately into a .txt file.
How do I save Gemini images in PDF?
Uploaded images (what you sent Gemini) render reliably in every method. Generated images (what Gemini created) are more fragile — they load from signed URLs that can expire, and if the PDF capture is slow the URL may time out mid-render. Best practice: right-click each generated image and Save image as... before running the PDF capture. That way if the image slots render blank in the PDF, you still have the source files. Extension-based capture generally handles images better than the print dialog because it waits for images to load before rendering.
Can I save a Gemini share link as PDF?
Yes. When you share a Gemini conversation, it produces a public URL at g.co/gemini/share/... that opens a read-only view of the conversation. That page can be captured with any of the four methods above — often more reliably than the live chat, because the share view doesn't have the composer or sidebar chrome. Open the share link in your browser and treat it as any other webpage. The Ctrl+P route works especially well on share links because there's less UI to fight with.
Bottom line
Save a Gemini chat as PDF depending on what you actually want. One answer? Use Gemini's built-in export to Docs, then download as PDF. A short conversation? Ctrl+P with Background graphics on and scale at 80%. Anything real — long threads, code-heavy responses, mixed images — install an extension purpose-built for full-page capture like Convert: Web to PDF. Runs locally, captures the full scrollable page, keeps your code blocks intact, doesn't ship your conversation to a server. Free, and installs in ten seconds.