When you export a Copilot Page to Microsoft Word, you expect the layout, headings, tables, and images to appear exactly as they do in the Copilot workspace. However, the export process does not preserve every formatting element. Some styles collapse, certain interactive elements are removed, and complex tables may shift. This article explains exactly which formatting elements survive the export, which are lost, and how to work around the most common discrepancies.
Key Takeaways: What Happens When You Export Copilot Pages to Word
- Copilot Page > Export > Word (.docx): Retains text, basic formatting, and static images but removes interactive Copilot widgets and live data connections.
- Heading styles and list numbering: Map to Word’s built-in Heading 1, 2, 3 and list styles, though spacing may change slightly.
- Table borders and cell shading: Preserved in most cases, but merged cells and nested tables may lose alignment and require manual adjustment in Word.
How Copilot Pages Export to Word Handles Formatting
Copilot Pages are web-based documents that support rich text, embedded Copilot responses, tables, images, and hyperlinks. The export to Word feature converts the page into a standard .docx file. The conversion engine maps Copilot’s internal HTML-based formatting to Word’s Open XML structure. This mapping is not one-to-one. Some visual properties such as font family, font size, bold, italic, and underline are transferred directly. Color highlighting and background shading are also preserved in most cases.
The export process removes all Copilot-specific widgets. These include the “Ask Copilot” inline prompts, dynamic data panels, and any live Copilot-generated content that updates in real time. The exported Word document contains a static snapshot of the text that was visible at the moment of export. Any Copilot-generated text that was collapsed or hidden inside expandable sections is not included.
Text Styles and Fonts
When you apply a heading style in a Copilot Page, the export assigns the corresponding Word heading style. Heading 1 in Copilot becomes Heading 1 in Word. The font face and size are inherited from the Copilot Page theme. If the page uses a custom font that is not installed on the computer opening the .docx file, Word substitutes a default font. The substitution can alter line spacing and page breaks.
Tables and Layout
Tables are the most sensitive element during export. Simple tables with uniform rows and columns export cleanly. Tables that contain merged cells, nested tables, or varying row heights may lose their structure. Cell borders are preserved, but the width of columns may adjust to fit the Word page width. If the original Copilot Page table was wider than the Word margins, columns shrink proportionally. This can make text wrap unexpectedly inside cells.
Images and Embedded Objects
Static images such as PNG, JPEG, and GIF files are embedded in the .docx file. Their position relative to the surrounding text is preserved. Copilot Pages that contain SVG graphics may convert those to PNG during export, which can reduce sharpness. Embedded video or audio links are stripped. Only the hyperlink text remains as clickable text in Word.
Steps to Export a Copilot Page to Word and Check Formatting
Follow these steps to export a Copilot Page and then verify that the formatting meets your requirements.
- Open the Copilot Page you want to export
Navigate to the Copilot workspace in Microsoft Edge or Chrome. Locate the page in your list of recent pages or use the search bar. Click the page title to open it in the editor. - Open the export menu
Click the three-dot menu icon in the upper-right corner of the page editor. Select Export from the dropdown list. A submenu displays available export formats. - Choose Word (.docx)
Click Word (.docx). The browser downloads the file to your default download folder. The file name is the page title with a .docx extension. - Open the exported file in Word
Double-click the downloaded file. It opens in Word desktop or Word for the web. Review the first page for heading styles, list numbering, and table borders. - Compare the original page layout with the Word output
Keep the Copilot Page open in a separate browser tab. Scroll through the Word document and look for differences in font size, line spacing, table column widths, and image placement. Note any misaligned elements. - Adjust formatting in Word if needed
Use Word’s Layout tab to adjust margins or table properties. Use the Home tab to reapply heading styles if the export changed them. Resize images manually if they appear too large or too small.
Common Formatting Problems and Workarounds
Heading styles are not applied in the exported Word document
This happens when the Copilot Page heading was created using manual bold and font size changes instead of the built-in heading dropdown. The export only maps true heading styles. To fix this, edit the original Copilot Page and apply the Heading 1, Heading 2, or Heading 3 style from the formatting toolbar before exporting again.
Tables lose column alignment and cells overflow
If the Copilot Page table was built with fixed column widths that exceed the Word default page width of 6.5 inches, columns shrink. To work around this, set the Word page orientation to Landscape before opening the exported file. Alternatively, in the original Copilot Page, reduce the width of wide columns or split the table into two smaller tables.
Images appear stretched or pixelated
Images that were resized in the Copilot Page using percentage scaling may not retain the same aspect ratio after export. The export embeds the original image file and applies the same width and height attributes. If the original image was low resolution, it will appear pixelated in Word. Upload a higher-resolution version of the image to the Copilot Page before exporting.
Hyperlinks are not clickable in the exported document
Hyperlinks that were inserted as plain text URLs in the Copilot Page remain plain text in Word. Only hyperlinks created using the Insert Link button in the Copilot Page toolbar become clickable in Word. After export, select each plain URL in Word, press Ctrl+K, and paste the URL into the Address field to make it clickable.
Copilot Pages Export vs Word Native Formatting: Key Differences
| Item | Copilot Page (Source) | Exported Word Document |
|---|---|---|
| Heading styles | H1, H2, H3 with theme fonts | Maps to Word Heading 1, 2, 3 |
| Inline Copilot widgets | Interactive, live | Removed entirely |
| Table merged cells | Supported with visual alignment | Preserved but may shift |
| Image resolution | Original resolution | Same resolution; no compression |
| Hyperlinks | Clickable with URL tooltip | Clickable only if inserted via toolbar |
| Background color | Full page and cell shading | Cell shading preserved; page background lost |
The table above summarizes the main differences between the source Copilot Page and the exported Word file. Use this as a checklist before distributing the Word document to colleagues or clients.
You can now export Copilot Pages to Word with a clear understanding of which formatting elements survive the conversion. To minimize post-export cleanup, apply true heading styles and use the Insert Link button for all hyperlinks before exporting. If you frequently export tables, test a sample table with merged cells first and adjust column widths in the Copilot Page to stay within standard Word margins.