Export a ChatGPT conversation to Word

The point of a .docx is that you can keep working in it, so the structure of the conversation survives the trip:

• Who said what — user and ChatGPT turns stay labelled and in order.
• Headings — the #, ## and ### levels ChatGPT uses.
• Lists — bulleted and numbered.
• Code blocks — kept as code, in a monospace face, not reflowed into prose.
• Inline formatting — bold, italic and inline code.
• The conversation title and date, as a header on the first page.

And what it does not, so you are not surprised by it later. Markdown tables come through as plain text rather than real tables, links keep their address but are not clickable, and images and LaTeX formulas are not carried over. Native tables and lists are on the roadmap; everything above is what the converter does today.

Text is stored as text, so any language survives — Cyrillic, Greek, Arabic, Chinese, Japanese and Korean all open correctly as long as your editor has a font for them.

Selecting a long conversation in the browser and pasting it into Word usually costs you the structure: headings arrive as ordinary bold lines, code blocks lose their formatting and the boundary between your question and the answer disappears. A screenshot keeps the look but gives you an image you cannot edit or search.

A generated .docx is an actual document: you can edit it, comment on it, quote from it, hand it to someone who does not use ChatGPT, or drop it into a report as-is.

There is nothing to install, either. Browser extensions need permission to read your ChatGPT pages; this works from a public share link that you paste yourself, so it never touches your account.

The same share link can be exported as PDF when you need a fixed, shareable copy, or as Markdown, HTML and JSON from the main page — Markdown for docs and repositories, HTML for a self-contained page, JSON when you want to process the messages yourself.