Word to PDF

A Word document is a set of instructions for laying out content: this paragraph uses this style, this table has these columns, let the text flow where it will. Where the pages break is not stored in the file — it is computed on the fly, every time the document is opened, from the metrics of the fonts that happen to be installed. That is why the same .docx can paginate differently on two computers.

A PDF is the opposite. It records the finished result: this glyph, at this size, at this exact coordinate on this page, with the font it needs embedded alongside it. Converting is the act of freezing one into the other — running the layout once, definitively, and recording the outcome so it can never drift again.

This is the whole reason to convert. Anything you send to a client, submit to a portal, or file as a record should be a PDF, because it is the only version you can be certain will look on their screen exactly the way it looked on yours.

Nearly every layout surprise in this conversion traces back to a font. When a document asks for a typeface the converting machine does not have, a substitute is chosen — and substitutes are never metrically identical. Slightly wider characters push a line onto the next line, which pushes a paragraph onto the next page, and a document that was three pages becomes four with a heading stranded at the bottom.

The fix is to stop the substitution happening. Word can embed fonts directly in the .docx, under the save options, and an embedded font travels with the document and is used verbatim. It adds a little to the file size and removes the entire class of problem.

Where embedding is not possible — some fonts are licensed in a way that forbids it — the next best thing is to build the document in widely available typefaces from the start. A document set in a common system font converts identically everywhere, because there is nothing to substitute.

Real Word structures carry over as real PDF structures. Heading styles become outline levels a viewer can show as a navigation panel. Hyperlinks and cross-references become clickable link annotations. Tables keep their cells, alt text on images is retained for screen readers, and a table of contents built with Word's field remains navigable rather than becoming a list of dead text.

Formatting that only imitates structure carries nothing. A heading made by bolding a line and bumping it to 16pt looks like a heading and is, as far as the file is concerned, an ordinary paragraph — so it produces no bookmark and no outline entry. The same applies to lists built by typing hyphens and to tables built out of tab stops.

The practical advice is short: use the built-in styles. It costs nothing while writing, and it is the difference between a PDF that is navigable and accessible and one that is a flat picture of a document.

Two minutes in Word saves most of the round trips. Accept or reject any outstanding tracked changes, since the conversion prints the document as it currently reads and leftover markup can silently change what appears. Check that images are anchored the way you expect, because a floating image positioned relative to a paragraph can move when pagination shifts.

Check the page setup too — paper size and margins come across exactly, so a document laid out for Letter will produce a Letter PDF even if it is destined for A4 printing in Europe. Resize PDF can fix that afterwards, but setting it correctly beforehand is cleaner.

If the finished PDF needs to be locked down, converting is only the first step: Protect PDF adds a password and permission restrictions, and Sign PDF adds a signature. Both work on the converted file.