Why your PDF looks different on someone else's computer

The entire point of the format is in its name. A Portable Document Format file is supposed to arrive looking exactly as it left. So it is genuinely disorienting when a colleague opens your carefully arranged document and reports that the headings are in the wrong typeface, the columns have shifted, and a table now runs onto a second page.

This is not random. There are three causes, they can be told apart from the symptoms, and two of them are entirely preventable at the moment you create the file.

Cause one: the font never travelled

A PDF can either carry its fonts inside the file or simply name them and hope. When a font is embedded, the actual glyph shapes are stored in the document, and every reader draws the text using those exact shapes. When it is merely referenced, the file says something like use Calibri here, and the reader looks for Calibri on the machine it is running on.

If that font is missing, the reader substitutes something it considers close enough. Substitutes are never identical. A replacement face has different letter widths, so a line that fitted neatly now wraps early or runs long, and everything below it shifts. One missing font can cascade through an entire document.

This is why the problem so often appears when a file moves between Windows and macOS, or reaches someone reading on a phone. Fonts that feel universal because they arrived with your operating system are frequently absent on someone else's.

• Headings in an unexpected typeface: a font was substituted
• Text that used to fit now wrapping onto an extra line: substitution changed the letter widths
• Tables and columns misaligned: knock-on effect of the same shift
• Boxes, question marks or blank squares in place of characters: the substitute has no glyph for them

Cause two: form fields and annotations

Interactive elements are not part of the page. Form fields, comment boxes, stamps and signature widgets are stored as a separate layer above it, and each reader renders that layer according to its own idea of styling.

The practical result is that a form filled in one application can appear empty in another, or show the values in a different typeface and size than you saw. Signature stamps sometimes vanish entirely in readers that do not support the annotation type used.

Flattening solves this. Flattening merges the interactive layer permanently into the page content, so filled values become ordinary page content and every reader draws them the same way. The trade is that the form is no longer editable, which is usually exactly what you want when sending a completed one.

Cause three: the reader itself

Browsers, phone viewers and desktop applications do not implement the specification identically. Built-in browser viewers are the usual suspects: fast and convenient, but implementing a subset of PDF, and the place where transparency effects, unusual colour handling and layered graphics most often go wrong.

There is a quick diagnostic here. If the file looks correct in a full desktop PDF application and wrong in a browser tab, the document is fine and the viewer is the limitation. If it looks wrong everywhere except on the machine that produced it, the document is at fault and a font is almost certainly missing.

How to make a PDF that travels

1. Embed all fonts when exporting. Most applications offer this in the export or print dialog, and it is not always switched on by default.
2. Prefer widely available typefaces for body text, so a substitution is less damaging if one happens anyway.
3. Flatten completed forms and annotations before sending.
4. Check the result on a device that did not create it, ideally running a different operating system.
5. For documents that must survive for years, convert to PDF/A, which requires embedding by design.

That last option is worth knowing about even outside archiving. PDF/A forbids anything that depends on the reader's environment, which means fonts must be embedded and external references are not allowed. A file that passes PDF/A validation is a file that will render the same in a decade.

When you are on the receiving end

If someone sends you a document that looks wrong, you cannot embed a font that was never included. What you can do is open it in a different reader, since a full application often makes a better substitution than a browser. If the file matters, ask the sender to export it again with fonts embedded. That request usually fixes it in one attempt.

And if you need to work with the content rather than just read it, converting to Word lets you re-apply fonts you actually have, at the cost of the layout being reconstructed rather than preserved.