How to convert Word to PDF (and actually keep the formatting)
Word-to-PDF is one of those things that 'just works' 90% of the time and creates disasters the other 10%. Here's what breaks and how to avoid it.
Why formatting breaks
Word documents are not really documents — they're instructions for laying out a document, and the layout depends on the fonts and printer drivers installed on the machine doing the rendering. Convert a Word file on a computer that doesn't have your fonts, and the PDF you get back will have substituted fonts, wrong line breaks, wrong page counts, and often broken tables.
Three specific things trip people up most:
- Custom fonts that aren't installed on the conversion server. The service falls back to a similar font, which is usually the wrong width, and every line reflows.
- Linked images and embedded objects. OLE objects (embedded Excel charts, Visio diagrams) don't survive most conversions unless the tool has Office installed.
- Bookmarks and cross-references. Automated "See page X" text often becomes "See page ??" in the PDF because the numbering was regenerated during conversion.
The most reliable way
Open the .docx in Microsoft Word itself and use File → Save As → PDF. Word has all the fonts installed locally, all the objects properly linked, and knows how it wanted the document to look. Nothing else will match this fidelity.
If you don't have Word installed, LibreOffice's export is the next best thing — same principle, all the fonts are local, all the objects render before the PDF is generated.
When to use an online converter
Two situations where an online tool is genuinely the right choice:
- You're on a device that can't install Word or LibreOffice — a Chromebook, a locked-down work laptop, a phone.
- You need to convert a bunch at once and don't want to open each in Word manually.
Word to PDF on DashConvert runs the conversion in your browser using a pure-JavaScript layout engine. The formatting fidelity is close to Word's own on standard fonts (Arial, Times New Roman, Calibri, common Google Fonts). Custom or exotic fonts may substitute — the tool will use a fallback.
Fonts: the one setting that matters
If your document uses a font that's not on the machine doing the conversion, it will substitute. This applies to server-based converters and to browser-based ones. The workaround:
- For truly critical documents, convert using Word or LibreOffice on a machine with the fonts installed.
- For everything else, use standard web-safe fonts (Arial, Times New Roman, Georgia, Verdana, Calibri, Cambria) or the standard Google Fonts. These are handled correctly by essentially every converter.
Common gotchas
- Header images vanish or shift. Usually means the image is anchored to a specific text position that reflowed. Fix in Word: right-click image → Wrap Text → In Line with Text before converting.
- Numbered lists restart or renumber wrong. Custom list styles don't always survive. Fix: use Word's built-in Numbered List style rather than manual numbering.
- Table borders disappear. Usually a display setting; make sure borders are set on the table itself, not on individual cells.
- Fonts render at wrong size. Almost always a font substitution issue — see above.
After the conversion
Once you have the PDF, common follow-ups:
- Merge PDF if the doc needs to be combined with other PDFs (e.g., appendices).
- Compress PDF if the document is huge because of embedded images.
- Protect PDF if you need to password-protect it before sending.
All of these run locally too, so a document you started in Word never has to touch a server anywhere in the pipeline.