A PDF is a rendering, not a copy of Word’s layout engine
DOCX stores instructions: styles, font names, section sizes, floating anchors and line-breaking rules. A converter must interpret those instructions. Microsoft Word and LibreOffice can make different choices even when both outputs are valid.
A one-character difference in a line can push a paragraph, image or table onto another page. Compare the whole document, not just the first page.
Stabilise the source before conversion
Accept or reject tracked changes, update the table of contents and save the final DOCX before uploading.
- Use fonts likely to exist on the conversion server, such as Liberation Sans or Noto families.
- Prefer fixed image sizing over floating placement when exact flow matters.
- Set explicit section paper sizes and margins.
- Avoid using repeated spaces or blank paragraphs to position content.
Worked example: a heading moves to the next page
Suppose page 3 ends with a heading and two lines of body text. A substitute font is slightly wider, so the second line wraps and Word’s ‘keep with next’ rule moves the heading and paragraph to page 4.
Reduce ambiguity by embedding an allowed font where licensing permits, adjusting the preceding spacing, or inserting an intentional page break. Then save and convert again.
Know the limit
No independent Office renderer guarantees pixel-identical output for every Word feature. For a legally fixed layout, create and approve the PDF in the authoring environment rather than treating public conversion as final prepress.
Use the relevant tools
These guides are general information, not legal, security or records-management advice. Follow your organisation’s policies for sensitive files.