Why the PDF sometimes looks different from your Word file
A Word to PDF converter renders a .doc or .docx file into a fixed-layout PDF, so that fonts, spacing and page breaks appear the same on every device rather than reflowing to the reader’s software.
A Word document is a set of instructions for laying out text; a PDF is a record of where everything ended up. That distinction explains almost every question people have about this conversion — why a document sometimes repaginates, why a heading font changes, and why sending a PDF is the right move when the layout matters.
This page explains the conversion engine used here, which elements carry over reliably, which ones need checking, and what to verify before a file goes to a client, a submission portal or a printer.
The conversion, specified
- Engine
- Conversion runs on our server using LibreOffice in headless mode — the same rendering engine behind LibreOffice Writer, driven from the command line.
- Accepted formats
- Modern .docx and legacy .doc files. The upload is validated by file type, so a renamed file will be rejected rather than producing a corrupt PDF.
- Size limit
- 20 MB per document. Most text documents are far below this; files that exceed it are usually carrying uncompressed images.
- Timeout
- Conversion is allowed up to two minutes. A long document with many images takes longer than a two-page letter, but almost everything finishes in seconds.
- File handling
- Your file is uploaded over HTTPS, converted in a temporary working directory and returned. It is not kept afterwards — the privacy policy sets out the detail.
- What you get back
- A standard PDF with selectable, searchable text — not an image of your pages. It can be indexed, copied from and read by screen readers.
What converts cleanly, and what to check
Direct answer: body text, headings, lists, tables and images convert reliably. Anything that depends on a specific font or on Word-only features deserves a look before you send the file.
| Element | Fidelity | What to watch for |
|---|---|---|
| Body text, headings, lists | Reliable | Structure and numbering carry over as written. |
| Tables | Usually reliable | Very wide tables and nested tables can repaginate differently. |
| Images and charts | Reliable for embedded images | Charts linked to an external spreadsheet may not render — embed them first. |
| Fonts | Depends on availability | A font that is installed on your machine but not on the conversion server is substituted with the closest match, which changes line lengths and can shift page breaks. |
| Headers, footers, page numbers | Reliable | Confirm the page count if your document references a total. |
| Track changes and comments | Not included | Accept or reject changes and remove comments before converting — this is a feature, not a gap, since a delivered PDF should be clean. |
| Macros, form fields, embedded objects | Not carried over | PDFs cannot execute Word macros. Interactive forms need to be built as PDF forms. |
| Hyperlinks | Usually preserved | Check that long URLs did not get broken across a line. |
The font substitution problem, and how to avoid it
This is the single most common reason a converted PDF looks slightly different from the document on your screen — and it applies to every server-side converter, not just this one.
Why it happens
A .docx file names the fonts it wants but does not usually contain them. If the converting machine does not have that font installed, it picks the nearest available substitute. Different metrics mean different line breaks, which can cascade into different page breaks.
How to prevent it
Use widely available fonts for documents that will be converted elsewhere. If you must use a licensed brand font, export the PDF from Word itself on the machine that has the font installed.
How to detect it
Compare the page count first — it is the fastest signal. Then check the last line of each page: substituted fonts show up as text that has moved across a page boundary.
Non-Latin scripts need attention
Arabic, Hebrew, Devanagari, Thai and CJK text depend on fonts with the right glyph coverage and shaping. Always open and read the converted PDF rather than assuming it is fine.
Complex layouts drift most
Text boxes, absolutely positioned images, multi-column sections and SmartArt are where differences concentrate. Simple linear documents convert essentially perfectly.
This converter vs. exporting from Word yourself
Use whichever removes the most risk for the document in front of you.
| Option | Best for | Trade-off |
|---|---|---|
| This online converter | A quick conversion on a machine without Word, a Chromebook, or a phone | Server-side font substitution applies, so verify layout-critical documents. |
| Word’s own Save as PDF | Anything where layout is critical or a brand font is used | Requires Word on a machine with the fonts installed. |
| Google Docs export | Documents already living in Google Drive | Google’s own font substitution applies to anything uploaded from Word. |
| Print to PDF | A last resort that always works | Loses hyperlinks and document structure, and can produce a larger file. |
Confidential material — contracts, medical records, unpublished manuscripts — should be converted locally rather than uploaded to any online service, including this one.
Before you send the PDF
- Compare the page count against the original document — a mismatch means the layout moved.
- Open the PDF and try selecting text; if you cannot, something went wrong in the export.
- Check that headings, page numbers and any table of contents still line up.
- Confirm comments and tracked changes are gone. Reviewers can read them, and they routinely leak internal discussion.
- Verify the file against any length requirement using the word counter before conversion, since a PDF cannot be edited afterwards.
- Need the file back in an editable form later? Keep the .docx — PDF to Word conversion is never a perfect round trip.
How this page is maintained
The engine, accepted file types, 20 MB limit and two-minute timeout described here were read from this tool’s server implementation. The font-substitution behaviour is inherent to server-side conversion and is documented rather than glossed over, because it is the difference people actually notice.
Written and reviewed by the ToolsRacks editorial team. Last reviewed: .