Scroll to the top of the conversation so all messages load, collapse the sidebar, then press Ctrl+P or Cmd+P. Enable background graphics and set margins to minimum. For long conversations, generate a PDF from your data export first and print that, which avoids missing messages.
Short answer
Scroll to the top of the conversation so all messages load, collapse the sidebar, then press Ctrl+P or Cmd+P. Enable background graphics and set margins to minimum. For long conversations, generate a PDF from your data export first and print that, which avoids missing messages.
Step by step
Load the whole conversation: Scroll to the very first message. ChatGPT unloads distant messages to stay responsive, and the printer can only capture what is currently on the page.
Hide the sidebar: Collapse the conversation list so the printed page uses full width rather than leaving a column of dead space.
Open print and set options: Ctrl+P on Windows, Cmd+P on Mac. Turn on background graphics so message bubbles stay distinguishable, set margins to minimum, and reduce scale to about 80 percent if code lines are being cut off.
Verify the preview: Check the first and last pages of the preview against the actual start and end of the conversation. A page count that looks too low means messages did not load.
Print or save: Send to your printer, or save as PDF first if you want a copy on file as well as on paper.
Printing is one of the few tasks where the ChatGPT interface actively works against you. The design decisions that make the app fast, chiefly not rendering the whole conversation at once, are exactly the ones that break printing.
The truncation problem
ChatGPT keeps only a window of messages in the page at any time. Scroll away from a message and it is removed from the document; scroll back and it is re-inserted. When you print, the browser captures the document as it exists at that instant.
The consequence is that on any conversation longer than roughly thirty exchanges, printing without scrolling to the top produces a document that begins partway through. There is no warning, no error, and no indication in the print preview that anything is missing unless you are checking the page count against your expectations.
Scroll to the very first message, waiting for each loading spinner to resolve, before you open the print dialog.
Getting the settings right
Three settings make the difference between a usable printout and an unreadable one.
Background graphics must be on. ChatGPT distinguishes your messages from the assistant's largely through background shading. Print defaults strip backgrounds to save ink, which merges everything into one undifferentiated column of text.
Margins at minimum buys horizontal room, which matters because code blocks do not reflow when printed. Wide lines get clipped at the margin rather than wrapping.
Scale around 80 percent is the practical fix when code is still being cut off. It costs legibility but preserves content, which is the right trade.
When printing directly is the wrong approach
If the conversation contains substantial code, printing from the browser will clip it. If it contains images, they frequently print as empty boxes. And if you need more than one or two conversations, there is no bulk option; the interface prints one conversation at a time and you cannot select several.
In all three cases, generate the document from your data export instead and print that.
Printing from the export
Request the archive from Settings, then Data Controls, then Export Data. Load the resulting conversations.json into ChatExports and generate PDFs.
The PDFs are built for print rather than for screen. Pages break between messages instead of through them, code wraps rather than clipping, speaker labels repeat so you can tell who is talking on page seventeen, and the text stays selectable. Print those and the output matches what you expected.
You can also bulk-generate, turning an entire history into a folder of printable PDFs in one pass. Conversion runs in your browser, so nothing is uploaded.
Printing for a formal record
If the printout is going into a case file, an audit trail, or anywhere its completeness might be questioned, print from the export rather than the screen. An export-derived document contains the full conversation with original timestamps, and you retain the source JSON as corroboration. A browser printout has neither property, and its silent-truncation behaviour makes it genuinely unreliable for that purpose.
Frequently asked questions
Why does my printed conversation start in the middle?
Messages you have not scrolled past are not loaded in the page, so the browser cannot print them. Scroll to the first message and let it finish loading before printing.
How do I stop code from being cut off when printing?
Set margins to minimum and reduce print scale to around 80 percent. For conversations with a lot of code, generating a PDF from the export handles wrapping properly instead.
Can I print multiple ChatGPT conversations at once?
Not from the interface. Export your data and bulk-convert to PDF, then print those files together.
Should I print in colour?
Colour helps if you rely on background shading to distinguish speakers. If you are printing in black and white, use the export-derived PDF, which uses explicit text labels rather than colour alone.