Why Word Documents Lose Formatting When Shared
Short answer
The recipient does not have your fonts, so Word substitutes the nearest match and every line reflows. Either stick to fonts installed everywhere, embed yours under File → Options → Save → Embed fonts in the file, or send a PDF when the layout matters more than editability. Compatibility mode and a different default printer driver cause most of the remaining cases.
On this page
You spent an hour getting the document right, sent it, and the reply is a screenshot where the headings are a different typeface, the table runs off the page and what was four pages is now five.
Nothing is corrupted. Word does not store your document as a picture of a page. It stores text, structure and instructions, and then recreates the layout on whatever machine opens it, using the fonts and printer that machine happens to have. Change those inputs and you change the output. That is the design, not a bug, and most of the fixes follow from understanding it.
Which of the four causes is yours?
| What changed | Cause | Fix |
|---|---|---|
| Typeface looks different, everything reflowed | Font not installed on their machine | Embed fonts, or use common ones |
| Page count differs, layout nearly right | Printer driver metrics | Usually harmless; send PDF if it matters |
| New features behave oddly, ribbon says Compatibility Mode | Old file format | Convert the document |
| Tables and text boxes collapse entirely | Opened in Google Docs or Pages | Export to PDF instead |
Font substitution accounts for the overwhelming majority. Start there.
Fonts: the main event
When Word opens a document calling for a font that is not installed, it does not stop and ask. It picks a substitute, and every character’s width changes slightly. Those differences compound across a line, a paragraph, a page, and by page three your carefully placed heading is sitting in the wrong place.
This bites hardest with Microsoft 365’s cloud fonts. Fonts that arrive with a Microsoft 365 subscription are available to subscribers and not to someone running an older perpetual-licence Office or a different platform entirely. A document that looks perfect on your machine can be substituting on theirs with no warning shown to either of you.
Option one — use fonts that exist everywhere
The genuinely safe set is smaller than people assume. Arial, Times New Roman, Courier New, Georgia, Verdana and Tahoma are present on Windows and macOS and have been for a long time. Calibri and Cambria ship with Office on both platforms, so they are safe between Office users and less safe elsewhere.
Anything you downloaded, bought, or acquired with a design tool is not safe.
Option two — embed the fonts
Go to File → Options → Save and tick Embed fonts in the file. Two sub-options appear:
- Embed only the characters used in the document reduces file size substantially but prevents the recipient editing with that font properly, because the characters you never typed are not there.
- Do not embed common system fonts is worth ticking. There is no point carrying Arial around.
Two limits to be honest about. Embedding adds weight — a few hundred kilobytes to several megabytes depending on the font. And many commercial fonts set a licensing flag that forbids embedding, in which case Word skips them without telling you. The only reliable test is opening the file on a machine that does not have the font.
Embedding also only works for Word opening a .docx. It does nothing if the
recipient uses Google Docs, Pages or a web viewer.
Option three — send a PDF
If the document is finished and the recipient only needs to read, print or sign it, PDF removes the problem completely. The fonts travel inside the file and the page geometry is fixed.
Use File → Save As and choose PDF rather than printing to a PDF driver, which preserves headings as bookmarks and keeps links working. Our guide on converting Word to PDF without losing formatting covers the options that matter.
Compatibility mode
If the title bar says Compatibility Mode, the document is in an older format and Word is deliberately disabling features so it behaves the way the older version did. Layout engines changed between Word versions, so a document authored in the new engine and saved to the old format can shift.
Go to File → Info → Convert to bring it up to the current format. Save afterwards and check the document, because conversion can itself move things — that is the point of it, but it means you need to look.
If the recipient is running genuinely old software, conversion makes things worse for them rather than better. In that case, PDF again.
Printer drivers, the cause nobody guesses
Word lays out text partly according to the metrics reported by the current default printer driver. Different printer, slightly different metrics, slightly different line breaks. A machine with no printer installed at all uses a generic driver with its own characteristics.
You cannot control the recipient’s printer, so this is mostly something to recognise rather than fix: if the formatting is nearly right and only the page count differs, this is usually why, and it is harmless unless the document is being printed against an exact page specification.
Tracked changes, comments and styles
Three smaller causes worth checking before you blame fonts.
Tracked changes left on. The recipient opens the document in All Markup view and sees a mess of balloons and coloured text that looks like broken formatting. Go to Review → Accept → Accept All Changes, and delete comments, before sending anything final.
Direct formatting over styles. A document where every heading was made bold and 16pt by hand, rather than using the Heading styles, has no structure for Word to re-apply consistently. It is also impossible to fix globally. Styles are the single biggest improvement most people can make to documents that travel.
Different style definitions. If the recipient’s Normal template defines Heading 1 differently and the document is set to update styles from the template, their definitions can win. This lives under File → Options → Add-ins territory and is rare, but it explains the case where only the headings change and the body text is untouched.
Google Docs and Pages
Google Docs does not run Word’s layout engine. It imports a .docx by
reinterpreting it, and complex features are approximated or dropped. Text boxes,
precisely positioned images, nested tables, section breaks with different page
setups, and custom numbering are the usual losses.
Round-tripping is worse than a one-way trip. Each conversion degrades the document a little further, and after three or four passes between Word and Docs a complex file is genuinely damaged.
If a document must be collaboratively edited by people on different platforms, pick one platform and author it there. Mixing them and hoping is how documents end up rebuilt from scratch at the worst possible moment.
What to expect
Switching to common fonts and sending a PDF for anything final eliminates essentially all of this. Embedding fonts handles the case where the document must stay editable and the typeface matters, with the caveat that some fonts will refuse.
What you cannot fix is a recipient on an unsupported platform opening a complex
document. A twelve-page report with text boxes, custom fonts and floating
images will not survive Google Docs intact, and no setting in Word changes that.
Send the PDF and a .docx together — the PDF for how it should look, the
.docx for anyone who needs to edit, with the explicit warning that the two
will not match on their screen.
If the file is also large enough to bounce off an email attachment limit, that is a separate problem with its own fixes, covered in reducing PDF size.