If Copilot's export menu offers Word directly for that conversation, use it. Otherwise, scroll to load the full conversation, print it to PDF with Ctrl+P or Cmd+P, and convert that PDF into a .docx file. This is the most reliable path since Copilot's export options are inconsistent across its different surfaces.
Short answer
If Copilot's export menu offers Word directly for that conversation, use it. Otherwise, scroll to load the full conversation, print it to PDF with Ctrl+P or Cmd+P, and convert that PDF into a .docx file. This is the most reliable path since Copilot's export options are inconsistent across its different surfaces.
Microsoft Copilot exists across several distinct products, and its ability to export a conversation directly to Word depends on which one you're using and which update your account currently has. Because of this inconsistency, there's a fallback route that works everywhere.
When a direct export exists
On some versions of copilot.microsoft.com and the Edge sidebar, a three-dot menu on a conversation includes an Export or Save option that can produce a Word file directly, sometimes framed as "export chat" rather than explicitly labeled Word. Where this is present and produces a properly formatted document, it's the fastest route: use it.
Why the option is inconsistent
Microsoft has iterated heavily on Copilot's interface across web, Edge, Windows, and Microsoft 365, and export features have appeared in one release and been repositioned or removed in the next. There isn't a stable, universally documented export flow the way there is for ChatGPT's Data Controls, so what you see in your account may differ from another user's.
The universal fallback
Since the built-in option can't be relied on, the print-then-convert method works regardless of Copilot surface or update version:
Open the conversation and scroll to the very first message so the entire thread has rendered
Print to PDF with Ctrl+P or Cmd+P, enabling background graphics so Copilot's citation cards and any formatted content stay visible
Load the PDF into ChatExports and convert it to Word
The output uses genuine Word styles: speaker turns as Heading 2, code in a monospaced font with proper wrapping, native lists rather than paste-mangled paragraphs, and the conversation title as Heading 1. Because these are real Word constructs, restyling, generating a table of contents, and using track changes all work normally afterward.
Handling citations
Copilot often cites web sources inline with numbered references, similar to Perplexity. When converting, check that citation numbers stayed attached to their source list; if a printed PDF separated them across a page break, a well-built converter should still preserve the association since it reads the document structure rather than just re-flowing text.
Copilot inside Microsoft 365 apps
If your Copilot conversation happened inside Word, Excel, or Outlook rather than the standalone chat interface, the conversation itself is typically treated as scaffolding for editing the document you were already in, rather than a separate transcript. In that case, there often isn't a distinct "chat to export" — the useful output is already in your document. This workflow is specifically for standalone Copilot chat conversations on the web or in Edge.
Why this matters for records
A Word document is the right target when a Copilot conversation needs to be reviewed, annotated, or included in a larger report with your own commentary layered in — something a fixed PDF or a screenshot can't support well.
Frequently asked questions
Does Copilot always let me export a chat to Word directly?
Not consistently. Some versions of copilot.microsoft.com and Edge expose an export option, but it has changed across interface updates. The print-then-convert method works regardless of which version you have.
Does this apply to Copilot inside Word or Excel?
Not directly. Copilot chat inside Microsoft 365 apps is generally scaffolding for editing your document rather than a separate transcript to export. This guide covers standalone Copilot chat conversations.
Will Copilot's inline citations survive conversion to Word?
Yes, when converted properly, citation numbers stay associated with their source references even if a printed PDF happened to separate them across a page break.
What's the most reliable way to get a Copilot chat into Word?
Scroll to load the full conversation, print it to PDF, then convert that PDF to Word. This works the same way regardless of which Copilot surface or interface version you have.