Convert Apple Pages to DOCX: Send an Editable Word Copy Without Guesswork

What Apple Pages exports to Word, which Microsoft Office features change at the boundary, and how to test the copy before it leaves your control.

  1. Add a file Choose or drop it here
  2. Pick the format Change it whenever needed
  3. Download the result After conversion completes

A Pages file is an Apple working document, while DOCX is the Office handoff copy

A file ending in .pages comes from Apple Pages on a Mac, iPhone, iPad, or iCloud.com. It is not a Microsoft Word document with a different name. Modern Pages files are packages containing Apple iWork data, including binary IWA records rather than the Office XML parts Word expects. A DOCX file is an Office Open XML document: Word and other compatible editors use its separate package parts for document text, styles, relationships, media, comments, and more. Changing .pages to .docx changes only the label, so Word still has nothing meaningful to read.

Apple provides a real conversion route because these formats describe some document features differently. In Pages on Mac, use File > Export To > Word; on iPhone or iPad, use the Share control and choose Export; in Pages for iCloud, open the document and choose Download a Copy. Apple’s February 2026 support guidance names the Word output as Office Open XML, or DOCX. Export creates a new file. Apple says changes made to the exported copy do not affect the Pages original, and changes to the original do not update the DOCX. That separation is useful for delivery, but it means there is no live two-way document.


The export rewrites document objects; it does not turn a Pages package into Word

During a Pages-to-DOCX export, ordinary paragraphs, character formatting, lists, tables, inline pictures, headers, footnotes, and supported hyperlinks are written as Word-compatible objects. The important limit is that a similar-looking feature is not always the same feature underneath. A Pages text box, chart, shape, comment thread, font choice, or change record has to be represented in Word’s model. The conversion can preserve useful content while changing how that content is edited later. An export is therefore a translation of the finished document state, not a way to make Pages and Word share one editable source.

Apple’s own Office compatibility table identifies the edges worth knowing before the export. Unsupported fonts are substituted when a document is brought across; some tab settings can look different; and WordArt text is preserved but its formatting may not be. A table of contents can transfer, but Apple says not all styling is preserved. Web, email, and bookmark hyperlinks are supported, while file hyperlinks are removed. Word Citation Manager citations and bibliographies keep their text but cannot be managed in Pages, whereas EndNote bibliographies are supported. Those facts explain why a clean letter often travels well while a carefully styled template, reference-heavy report, or document that links to local files needs a deliberate check.


What the Word recipient gains, and what the converted copy can no longer promise

  • A widely accepted editable file: DOCX is the format Apple names for Word export, so the recipient can open and revise a true Word document rather than an Apple package.
  • The Pages master stays untouched: export produces an independent copy, so the original remains available if the DOCX needs correction.
  • Usable text comments: Apple lists text comments as supported in its Office compatibility information, but review the actual comment positions after export.
  • Possible line and page movement: Apple specifically warns that text-layout differences can change page count, table layouts, and special typographic features.
  • Different font results: an unavailable font is substituted; because a substitute has different character widths, a single replacement can push a heading or table onto another page.
  • No local-file links: file hyperlinks are removed, even though web, email, and bookmark links have support.

The practical choice follows from that list. Export DOCX when the next step is Word editing, form completion, comments, or a system that asks specifically for a Word file. Export PDF as well when page appearance must be frozen for reading or printing. Apple notes that PDF preserves the fonts used in the Pages document and exports hyperlinks, including links for table-of-contents entries, footnotes, endnotes, web pages, email addresses, and bookmarks. A PDF is not a replacement for an editable DOCX; it is a visual reference that makes the review of an editable handoff much less ambiguous.


Named compatibility limits matter more than a successful open command

Word can open a DOCX without reporting an error and still show a document that requires attention. Apple documents that Pages can open and edit Word .doc and .docx files, while its compatibility page lists the boundaries of that exchange. In the reviewing tools area, text comments are supported, ink annotations are imported as shapes, and tracked changes have a narrow rule: changes to body text continue to be tracked, but all other changes are accepted on import. That means a review document should not be judged by a single paragraph with a small insertion. Check changed tables, objects, headers, and other non-body content separately.

References and rich layout deserve the same care. Apple says table-of-contents styling is not all preserved, and Word Citation Manager entries remain text but cannot be managed as Word Citation Manager data in Pages. If the DOCX will be returned to Pages later, retain the DOCX version that holds the active Word-side review and reference information. If it will remain in Word, open it in the actual Microsoft Word version used for the next edit rather than relying on a browser preview. A browser preview is good for spotting a missing page, but it does not prove that editable fields, comments, links, or page layout will behave as they do in Word.

There is also a browser route for people who have the Apple file but no Mac. Apple supports Pages for iCloud on a Mac or PC in Safari 13.1 or later, Google Chrome, or Microsoft Edge. Open the Pages document after signing in with an Apple Account, then download a copy as Word. This is a conversion option, not a promise that the Windows computer can natively open the original Pages package. Keep the original in iCloud Drive or another safe location until the downloaded DOCX passes a review.


Extra pages, shifted tables, missing fonts, and review history each have a different cause

An exported DOCX that has an extra page is usually not proof that words were lost. Apple warns that text-layout differences can produce a different page count and table layout. Start by comparing the first page where the count diverges, then inspect the font in that paragraph, line spacing, tab stops, page breaks, and the width of adjacent pictures or text boxes. Do not repair the whole document by inserting blank lines or repeated returns; that can make the next font substitution create a new problem. Make the relevant break explicit, resize the object, or choose a font installed in the recipient’s environment, then export again.

When text reflows around a missing font, find the actual font before editing margins. Apple says unsupported fonts are substituted, and a substitute changes line length. Install the licensed font where appropriate, or replace it intentionally in Pages and inspect all headings, tables, headers, and footers before making the DOCX. When a hyperlink to a local folder or file disappears, that is expected: Apple’s compatibility table says file hyperlinks are removed. Replace it with a web URL, add the file separately, or state a location in plain text if that is the available route.

For review work, use a simple order: finish and accept the Pages changes that must become the delivery text; export the DOCX; open it in Word; then let Word create the next round of Word revisions. Avoid repeatedly editing the Pages original and an exported DOCX as though they were synchronized. Apple explicitly says they are independent copies. This prevents a common version mismatch in which a text fix was made in Pages after the Word copy was sent, leaving the recipient with a valid but older document.


Pages and DOCX at the points that affect a real handoff

Handoff detailPages sourceDOCX export result
Native editorApple Pages on Apple devices or iCloud.comMicrosoft Word and compatible DOCX editors
Proper conversion routeFile > Export To > Word on MacOffice Open XML (DOCX) copy
Original after exportRemains unchangedSeparate file; later changes do not sync back
Page count and tablesPages layout rulesMay differ because of text-layout differences
FontsUses available Pages fontsUnavailable fonts can be substituted
Local file hyperlinksCan exist in the sourceRemoved; web, email, and bookmark links are supported
Tracked changesPages review modelBody-text changes track; other imported changes are accepted

Questions that prevent a Pages export from becoming a Word-side surprise

Can I rename a Pages file to DOCX?
No. A Pages file and a DOCX use different package structures. Use Pages’ Word export or Pages for iCloud to create an Office Open XML copy.

Does exporting change my original Pages document?
No. Apple says an exported or sent copy is independent. Changes made in the DOCX do not affect the Pages original.

Why does the DOCX have another page?
Apple warns that text-layout differences can change page count, table layout, and special typography. Check fonts, tabs, line spacing, objects, and explicit page breaks at the first changed page.

Will all links survive?
Web, email, and bookmark hyperlinks are supported in Apple’s compatibility table. File hyperlinks are removed, so provide the linked file separately or use a web address.

Should I send only DOCX when layout is important?
Send the editable DOCX when editing is required, but also keep or send a PDF reference when the recipient must compare page appearance. PDF is the safer format for a fixed visual record.