What Word-to-PDF Conversion Keeps, and What It Drops

There are two ways to turn a Word document into a PDF, and they produce noticeably different files. One preserves the page exactly as Word drew it. The other reads the document's structure and rebuilds it cleanly.

Neither is wrong. But if you pick the second and expected the first, the result looks like someone reformatted your document — because something did.

Two Approaches to the Same Job

Rendering means running Word's own layout engine, laying the document out page by page exactly as it appears on screen, and capturing that. This is what "Save as PDF" inside Word does. It is pixel-faithful because it is literally the same engine that drew your screen.

Structural conversion means reading the document's content and semantics — this is a heading, this is a list, this is a table — and building a fresh PDF from that description. This is what a browser-based converter does, because it does not have Word's layout engine available.

The distinction explains everything below. A structural converter knows your text is a Level 2 heading. It does not know, and cannot reproduce, that the heading was Calibri Light 14pt in dark blue with 6pt of space above it.

What Comes Through

Headings. Heading levels are read from the document structure and rendered at proportional sizes, so the hierarchy of your document is intact.

Paragraphs and body text. All of it, in order, with word wrapping recalculated for the new page width.

Bulleted and numbered lists. Both kinds, with their numbering.

Tables. Cell contents are preserved. When a table runs past a page break, the header row repeats on the next page.

Code and preformatted blocks. Rendered in a monospaced font.

Horizontal rules and paragraph spacing. The structural separators survive.

What Does Not

Fonts. The output uses a standard typeface throughout rather than the fonts in your document. This is the most visible difference, and the one people notice first.

Colours. Coloured text and shaded backgrounds are not carried across.

Images. Pictures embedded in the document do not appear in the converted PDF. If your document depends on figures, this is the one that matters most — check the output before sending.

Headers, footers and page numbers. These are page-furniture defined at the section level in Word. The converted document reflows into a fresh layout and does not reproduce them.

Manual page breaks and column layouts. Content reflows continuously. Where your page breaks fall in the PDF is determined by the new layout, not by where you put them.

Comments, tracked changes and footnotes. These live in Word-specific structures and are not represented.

Exact margins and spacing. Output uses an even A4 layout with consistent margins.

Which One to Use

Use Word to PDF in the browser when:

• The content matters more than the styling — a draft, a text submission, a reading copy
• You need it done without opening Word, or you do not have Word
• The document is text, headings, lists and tables
• The file is confidential and you would rather it never left your device

Export from Word itself when:

• The document contains images you need
• Visual fidelity is the point — a designed CV, a branded proposal, anything a client sees
• Headers, footers or page numbering carry required information
• The document has a specific paginated structure that must be preserved

This is not a limitation we are working around quietly; it is a genuine architectural difference. A browser cannot run Word's layout engine, so a browser-based converter reads meaning rather than reproducing appearance. Knowing that lets you pick correctly.

Getting a Better Result

If you are using the structural converter, a few habits improve the output considerably.

Use real heading styles. A heading created with Word's Heading 1 style converts as a heading. A line you made big and bold by hand converts as a paragraph that happens to be a paragraph. This is the single biggest factor.

Use the list buttons. Real lists convert as lists. Lines starting with a manually typed hyphen convert as ordinary text.

Use real tables. Columns created with tab stops become runs of spaces.

Deal with images separately. If your document has a handful of figures, convert the text and add the images another way — or export from Word.

Check the output. Open the PDF before sending it. Thirty seconds tells you whether the conversion did what you needed.

The Round Trip

A related question: can you convert Word to PDF and back again without damage? No — and not because of any tool's shortcomings.

PDF describes a finished page: put these glyphs at these coordinates. It does not record that a line was a heading or that a block was a table. Converting back means inferring that structure from position and size, which is PDF to Word's job and which it does well, but it is reconstruction rather than recovery.

Keep the DOCX as your editable original, and treat the PDF as output. Round-tripping through PDF as a working practice loses a little structure each time.

Frequently Asked Questions

Why does my converted PDF use a different font? Structural conversion reads your document's content and rebuilds it with a standard typeface. Reproducing the original fonts requires Word's layout engine, which a browser cannot run.

Where did my images go? Images are not carried into the converted PDF. If your document depends on figures, export to PDF from Word instead.

Do my headers, footers and page numbers carry over? No. Those are defined at the section level in Word, and the converted document reflows into a fresh layout without them.

Will my tables survive? Yes. Cell contents are preserved, and a header row repeats if the table runs past a page break.

Does .doc work, or only .docx? Both are accepted. Modern .docx files convert more reliably because the format carries structure more explicitly.

Is my document uploaded anywhere? No. Conversion runs in your browser, so the file never leaves your device — which is the main reason to use it for anything confidential.