Why your PDF fonts did not embed

A PDF that looks right on your machine and wrong on someone else's is nearly always a font embedding problem. The causes, in the order they actually occur.

21 September 2026 · Reference

If a PDF renders correctly for you and badly for the person you sent it to, the font is almost certainly not inside the file. Your machine has it installed, so the viewer finds it locally; theirs substitutes something else and the layout moves.

Check first, guess later

Before theorising, ask the file what it contains. In Acrobat: File → Properties → Fonts. On the command line, pdffonts document.pdf prints a table with an emb column — yes means the glyphs are in the file, no means the viewer will go looking.

A Type of Type1 or TrueType with emb no is the failure case. A name like ABCDEF+Helvetica with a six-letter prefix means a subset is embedded, which is normal and fine.

Why do PDF fonts get a random six-letter prefix?

That prefix marks a subset. Rather than embed a whole typeface, the producer embeds only the glyphs the document actually uses, and tags it with a unique prefix so two differently-subsetted copies of the same font do not collide when files are merged. It is a sign the embedding worked, not a problem.

The causes, roughly in order of frequency

1. The font licence forbids it. Font files carry an embedding permission flag: installable, editable, print-and-preview, or restricted. If a font is marked no-embedding, a well-behaved producer will refuse to embed it and silently substitute. Commercial foundry fonts and some system fonts do this. This is the most common cause and the least talked about.

2. The producer was told not to. "Optimise for size," "web-ready" and "minimal" export presets frequently drop embedding. Many "compress PDF" tools strip embedded fonts as a size win and do not warn you.

3. The base-14 assumption. PDF defines fourteen fonts every reader must provide — Helvetica, Times, Courier, Symbol, ZapfDingbats and their variants. Producers routinely skip embedding these on the theory that every reader has them. Readers then substitute their own interpretation, and metrics differ enough to reflow a tight layout.

4. The document used a font that was never really there. If an application requests a font the system does not have, the OS substitutes at composition time. The PDF then faithfully embeds the substitute. The file is correct; the document was wrong before it became a PDF.

5. It was merged or edited afterwards. Combining PDFs, stamping pages or running a "repair" pass can drop embedded font programs, particularly with older tooling.

How do I force fonts to embed?

It depends on the producer, but the setting is nearly always in the export dialog rather than the document. In InDesign and Illustrator it is part of the PDF preset; choose a Press or PDF/X preset, which mandate embedding. In Word, Save as PDF → Options → ISO 19005-1 compliant (PDF/A) forces it. From LaTeX, pdftex embeds by default unless \pdfmapline is configured otherwise. If the font's licence forbids embedding, no setting will override it — you have to change the typeface.

The reliable fix: export as PDF/A or PDF/X

Both standards require full font embedding, because both exist to guarantee a file renders identically elsewhere. Exporting to either will either embed everything or fail loudly and tell you which font it could not embed. That error is more useful than a silent substitution you discover a week later.

PDF/A is for archiving, PDF/X for print. Either will surface the problem.

Converting text to outlines

Turning text into vector shapes guarantees appearance and destroys everything else: the text is no longer selectable, searchable, extractable or accessible to a screen reader, and the file usually grows. It is a legitimate last resort for a licence-restricted display font on a cover page. It is a bad default for a document anyone needs to read or search.

Does outlining text make a PDF larger?

Usually yes, sometimes dramatically. An embedded subset stores each glyph once and references it; outlines store every occurrence as its own set of curves. A text-heavy page converted to outlines can multiply in size, and it loses searchability at the same time.

What this costs you beyond appearance

A non-embedded or outlined font breaks more than layout:

• Search — text that is outlines is not text, so nothing finds it
• Copy and paste — recipients cannot take a quotation out of the document
• Accessibility — screen readers have nothing to read, which fails PDF/UA and any Section 508 or WCAG obligation attached to it
• Extraction — any downstream automation reading the document gets nothing

If a document matters enough to send, it matters enough to run pdffonts over once before it goes.