Why the Same Word Document Looks Different in Word, Pages, LibreOffice, Google Docs, and WPS

Nov 9, 2026

DocCrisp

You open a .docx file in Microsoft Word and it looks right. Then a colleague opens the same file in Google Docs, Apple Pages, LibreOffice Writer, or WPS Office, and a line wraps in a different place, a table moves to the next page, or a font looks wrong.

The file is usually not broken. The apps simply read and display it in slightly different ways. This article explains why that happens and what you can do about it.

DOCX is a standard, but a very large one

DOCX is part of Office Open XML (OOXML). The format was standardized as ECMA-376 in December 2006 and then as ISO/IEC 29500 in early 2008 (Library of Congress, OOXML family). It was designed by Microsoft to match the features of the older binary Office formats and to stay compatible with existing documents.

ISO/IEC 29500 defines two conformance classes. They share one markup language. They are not two unrelated formats:

Strict is the variant defined by Part 1. The Library of Congress says this variant disallows the legacy markup specified in Part 4, so it keeps less of the old compatibility markup. It is not a file that contains only ordinary paragraphs.
Transitional allows that Part 4 markup in addition to Part 1. Part 4 is a supplement to Part 1, titled Transitional Migration Features, kept for compatibility with older documents (DOCX Transitional, DOCX Strict).

Microsoft explains that Transitional is almost identical to the first edition of ECMA-376, and that edition 2 of ECMA-376 matches the Strict version of ISO/IEC 29500 (Microsoft Learn). The Library of Congress notes that DOCX has been Word's default format since Word 2007 and that the standards documents behind it run to over six thousand pages (DOCX Transitional).

Because the specification is so large and includes many legacy features, every app other than Word has to decide which parts to support and how to map them onto its own features. Small differences in those decisions show up as small differences on the page.

Each app has its own layout engine

A DOCX file describes content and formatting: paragraphs, styles, fonts, spacing, tables, and page settings. It does not store the final position of every line. Each app calculates line breaks, spacing, and page breaks with its own text layout engine when it opens the file.

Google Docs, Pages, LibreOffice, and WPS were built independently from Word, so their engines don't calculate layout in exactly the same way. A tiny difference in how a line is measured can move one word to the next line, and that change can carry through the rest of the page.

Word's own compatibility settings

Word itself does not always lay out documents the same way. When Word opens a document created in an older version, it can open it in Compatibility Mode. Microsoft's support article, using Word 2016 as the example, says Compatibility Mode temporarily disables newer features so people on the earlier version can still edit, and it preserves the layout of the document. The Convert command clears the compatibility options so that the document layout appears as it would if it had been created in that newer Word (Microsoft Support).

In other words, a DOCX file can contain settings that tell Word to imitate older layout behavior. Other apps may support only some of these settings, which is another source of differences. The mode names differ by Word version.

Missing fonts and font substitution

Fonts are one of the most common causes of layout changes. If a document uses a font that isn't installed on the computer or available in the app, the app replaces it with another font.

Apple Pages: Apple's compatibility page states that fonts available for download are imported and unsupported fonts are substituted (Apple).
WPS Office: WPS notes that if a font is not installed on another computer, it "may not display correctly" (WPS Office Academy).
LibreOffice: LibreOffice has a font replacement table under Options (or Preferences) → LibreOffice → Fonts. You choose which font replaces another. The replacement changes what you see on screen or in print. It does not rewrite the font name saved in the file (LibreOffice Help).

A replacement font with different character widths changes where lines break, which can push paragraphs, tables, and images onto different pages. To reduce this problem, open-source projects provide metric-compatible fonts, designed so their character widths match the fonts they stand in for. Common examples are Carlito for Calibri, Caladea for Cambria, and Liberation Sans and Liberation Serif for Arial and Times New Roman (Carlito, Document Foundation). The Document Foundation also points out that Calibri and Cambria are proprietary fonts that are not freely available outside Microsoft Office (TDF Community Blog).

Matching widths often keeps line breaks closer, and the letters may still look slightly different. It does not make two layout engines wrap every line in the same place.

Features that some apps don't fully support

Some Word features have no exact equivalent in other apps. The apps' own documentation lists several of them. These are import and display limits. They are not a claim that every copy of an app, on every version, drops the same feature.

LibreOffice says that some layout features and formatting in complex Microsoft Office documents are handled differently or are unsupported, and that the amount of reformatting needed depends on the complexity of the document. For Word files, its help lists AutoShapes, revision marks, OLE objects, certain controls and form fields, indexes, tables, frames, multi-column formatting, hyperlinks and bookmarks, WordArt, and animated text as a general overview of features that may cause conversion challenges (LibreOffice Help).

Apple Pages publishes a feature-by-feature list (Apple). Examples include:

SmartArt graphics are imported as shapes.
WordArt text is preserved, but formatting may not be maintained.
Tables in headers and footers are not supported.
Stylized bullets are replaced with plain bullets, and some tiered numbered lists may look different.
Not all table of contents styling is preserved.
File hyperlinks are removed. Web, email, and bookmark hyperlinks are supported.

Google Docs lets you open, edit, and save Office files in Drive, with changes saved in the original Office format (Google Docs Editors Help). On a computer, a document in pages format can mix portrait and landscape pages. You apply the orientation to the current section, to this section forward, or to the whole document (Change page settings). Google's December 2020 Workspace update also said Docs can edit, import, and export Word documents that contain both orientations (Workspace Updates). Those page settings are not available in pageless format. Older community posts that say Docs cannot mix page orientations describe the product before this change.

In general, the more a document relies on floating objects, text boxes, complex tables, fields, and special graphics, the more likely it is to look different in another app.

Page size and margins

Page settings are another simple but common cause. A document set to A4 and a document set to US Letter have different page shapes, so text breaks across pages differently. If someone opens a file and then changes the page size, or an app uses a different default for new documents, page breaks will move. Check Page Setup (or the equivalent setting) to confirm the page size and margins before you compare two versions of a document.

How to keep your documents consistent

Use common fonts or embed your fonts. In Word for Windows, font embedding is under File > Options > Save > Embed fonts in the file (Microsoft Support). WPS Office Academy describes a similar option under Menu > Options > General and Save > Embed True Type. That menu can differ by WPS version (WPS Office Academy). Not every font is allowed to be embedded, and not every app uses embedded fonts, so widely available fonts are the safest choice.
Install metric-compatible fonts in LibreOffice. If you use LibreOffice, install Carlito, Caladea, and the Liberation fonts so that documents using Calibri, Cambria, Arial, or Times New Roman keep closer line lengths. Expect similar widths, not identical pages.
Check the page size and margins. Make sure everyone is using the same page size (A4 or Letter) and margins.
Avoid floating objects when possible. Place images and tables in line with text instead of using floating text boxes or wrapped objects. Inline content is easier for every app to position.
Use built-in styles and native tables. Real heading styles and Word tables are standard elements that other apps can usually map to their own features.
Export to PDF when the pagination must stay put. PDF records a paginated layout instead of asking each word processor to reflow the text. Use DOCX for editing and PDF for sharing a finished version. A PDF is not a promise that every viewer paints the same pixels, especially when fonts are not embedded.
Open the file in Microsoft Word for the closest match. DOCX is Word's native format, so Word usually displays it most accurately. If a document looks wrong in another app, check it in Word before you reformat it.

How DocCrisp output fits in

When you convert a JPG, PNG, or WebP image with DocCrisp, the result is a DOCX file. DocCrisp aims to keep paragraphs, heading levels, and table rows and columns as editable content. Multi-column layouts, text boxes, and pictures inside the page are flattened into a single column. Those are ordinary document parts, which other apps can usually map more readily than a page of floating boxes.

Even so, the differences described in this article apply to any DOCX file. For the closest match to the original image, open the converted file in Microsoft Word. Export a PDF if you need the pagination to stay put, with the limit in the list above.

You can convert one image at a time for free, with no sign-up, on the DocCrisp Image to Word converter.

Conclusion

The same DOCX file can look different across apps because each app interprets a very large standard in its own way, uses its own layout engine, substitutes missing fonts, and supports a different set of Word features. Using common fonts, inline content, and standard styles helps. PDF is the better choice when the pagination has to stay put, without promising identical pixels in every viewer.

Convert your image to Word for free