Grok to Word

Grok has no direct Word export on grok.com or in X. Scroll the conversation to the top so it fully loads, print it to PDF with Ctrl+P or Cmd+P, then convert that PDF into a .docx file. Pasting straight into Word carries over web page styling and mangles code blocks and lists.

Short answer

Neither grok.com nor Grok's presence inside X currently offers a Word or docx export. Getting a Grok conversation into an editable document means going through an intermediate step, since there's no structured export file to read from directly.

Why pasting directly into Word doesn't work well

Copying text out of Grok's chat interface and pasting it into Word brings along the web page's HTML formatting: background shading on message bubbles, inconsistent fonts, and broken code block layout where line breaks and indentation get flattened. Lists frequently convert into plain paragraphs prefixed with a hyphen instead of real Word list items. For anything beyond a short exchange, cleaning this up by hand takes longer than it's worth.

The print-then-convert workflow

Open the Grok conversation, on grok.com or within X, and scroll to the very first message. Long threads only keep recently-viewed messages rendered, so this step is necessary before capturing the whole thing.
Print to PDF with Ctrl+P or Cmd+P, enabling background graphics so the visual distinction between your prompts and Grok's responses is preserved.
Load that PDF into ChatExports and convert it to Word.

The resulting .docx uses real Word constructs rather than imitating a web page: speaker turns as Heading 2 so the navigation pane shows an outline, code in a monospaced style with wrapping, native numbered and bulleted lists, and the conversation title as Heading 1. Because these are genuine Word styles, a table of contents will generate correctly, track changes will behave normally, and the document merges cleanly into a larger report.

Common reasons to do this

Research write-ups. If Grok's real-time X search or reasoning contributed to an analysis, a clean Word transcript makes it easy to attach as a reference or appendix.

Comparing model outputs. People who compare Grok's answers against ChatGPT or Claude on the same prompt often want all three in the same document format so they read consistently side by side.

Editable records. A Word document can be annotated with comments and tracked changes, which a plain screenshot or PDF cannot.

Formatting caveats

Because the source is a printed web page rather than a structured data file, occasional interface elements (button icons, avatar thumbnails) may appear in the PDF before conversion. A proper conversion strips these, but it's worth reviewing the output once, since Grok's interface changes periodically.

Editing afterward

Since the output uses genuine Word styles rather than manual formatting, you can restyle the whole document at once — change the Heading 2 style to alter every speaker label, or change the code style to update every code block in one action.

Frequently asked questions

Is there a way to export Grok conversations directly to Word?

Not currently. Neither grok.com nor X offers a docx export. The workflow is to print the conversation to PDF and then convert that PDF into Word.

Will code Grok generated stay readable in the Word document?

Yes, when converted properly. Code appears in a monospaced font with preserved line breaks, rather than the mangled formatting you get from a direct paste into Word.

Can I merge a Grok conversation with a ChatGPT one in the same Word document?

Yes. Convert each separately, then use Insert, then Object, then Text from File in Word to combine them while preserving formatting.

Does this work for Grok used inside the X app, not just grok.com?

Yes, the same print-then-convert approach works for Grok conversations accessed within X, since the fallback relies on the browser's print function rather than a platform-specific export API.