On this page
Fonts influence pagination
Two fonts at the same nominal size can have different character widths and line heights. A substitute font can move words to another line and shift every page that follows.
Corporate and licensed fonts must be installed on the conversion host when their metrics are required. The font report identifies declared families but cannot guarantee identical glyph rendering.
Objects do not all behave like text
Floating images, charts, equations, text boxes and embedded Office objects use anchors and application-specific layout rules. Compatible renderers handle common cases, while complex layering should be checked after export.
- Review floating images.
- Inspect charts and equations.
- Check nested tables.
- Look at multi-column sections.
- Verify captions and cross-references.
Document view and markup matter
Tracked changes and comments can affect the view supplied to the renderer. If the active engine does not expose markup controls, the safest workflow is to choose the intended Word view and resolve changes before conversion.
Comments commonly do not appear in normal PDF output. The workspace reports their presence as an informational warning rather than pretending to control unsupported behavior.
Put the workflow into practice
Arrange source documents, select the pages you need, and create one PDF locally in your browser. Review the result before choosing any optional next step.
Try Word to PDFFrequently asked questions
Clear answers before you merge
Why did a page break move?
Font substitution, changed field output or renderer metrics can alter line and paragraph height.
Why is a comment missing?
Normal PDF rendering often excludes Word comments unless markup printing is explicitly supported.
Does DOC behave differently from DOCX?
Legacy DOC requires a compatible binary-format renderer and offers less practical browser-side analysis.