Explainers·6 min read

PDF Viewers Only Guarantee 14 Fonts Exist. That's Why Your Group Project Looks Different on Everyone Else's Laptop

Quick answer ✦A PDF stores text either by embedding the actual font data inside the file, or by just naming a font and assuming the reader's device already has it. When it doesn't, the viewer substitutes the closest match it can find, which can shift line breaks, page counts, and layout entirely. The only fonts every compliant PDF viewer is guaranteed to have without any embedding at all are the “standard 14”: Times, Helvetica, Courier, Symbol, and ZapfDingbats, in their regular, bold, italic, and bold-italic variants, per the PDF spec's own base font list. Anything else, including most Google Fonts and Canva picks, has to travel inside the file or it can break on someone else's machine.

It's a familiar shape of problem: the file looks perfect on the laptop that made it, then opens with shifted headings, wrapped tables, or an entirely different page count on your teammate's machine. Nothing corrupted. The font your document assumed was there simply isn't.

What “embedding” actually means

Embedding copies the font's own outline data into the PDF file itself, so the exact shapes render identically everywhere, at the cost of a larger file. Referencing just points at a font by name and trusts the viewer's system to supply it. Per Adobe's own documentation, a font can only be embedded if its vendor's license permits it, which is why some display and brand fonts refuse to embed at all even when you try.

Font familyNeeds embedding to look right elsewhere?
Times, Helvetica, Courier, Symbol, ZapfDingbats (the “standard 14”)No, guaranteed on every compliant viewer
Any Google Font (Roboto, Montserrat, Poppins, and so on)Yes
Any Canva, Adobe, or custom brand fontYes
Arial, Times New Roman, Calibri (Microsoft's defaults)Usually substitutes cleanly since Arial and Times New Roman are metric-compatible with Helvetica and Times, but it isn't guaranteed the way the standard 14 is

Where the embed toggle actually lives

  • Microsoft Word (Windows): File → Options → Save → check “Embed fonts in the file” before you export or print to PDF. It's off by default, per Microsoft's own support page.
  • Google Docs: there's no manual toggle. Custom fonts frequently fail to carry over on export, according to reports across Google's own Docs Editors Help community, so sticking to Docs' bundled font list is the safer bet when the file has to look identical everywhere.
  • Checking a PDF you already have: open it in Adobe Acrobat or Reader, go to File → Document Properties → Fonts tab, and it lists exactly which fonts are embedded and which aren't, per Adobe's own documentation.

The exception worth knowing: PDF/A

Some university and journal submission systems require PDF/A, an archival format. Under PDF/A, even the standard 14 fonts must be embedded, the usual exemption doesn't apply, per the same PDF font reference. If a submission portal rejects an otherwise-normal PDF, that's frequently why.

The last-resort fix: stop using fonts at all

When the deadline is now and there's no time to chase font settings, flattening the page to an image sidesteps the whole problem, since there's no font left to reference, just pixels.

  1. 1Export or print the file to PDF as normal first. The layout is still correct on your machine at this point.
  2. 2Convert each page to a high-resolution image with PDF to Image. This bakes the exact rendering, fonts included, into pixels.
  3. 3Rebuild a PDF from those images with Image to PDF. What comes out looks identical on every device, because there's no font left to substitute.
  4. 4Trade-off: the text is no longer selectable or searchable, and the file gets bigger. Use this for a final submission copy, not your working draft.

Fix the font settings

when you still have time before the deadline

  • Text stays selectable and searchable
  • Smaller file size
  • Fixes the problem for every future export, not just this one

Flatten to images

when the deadline is now and it just needs to look right

  • Guarantees pixel-identical layout everywhere
  • No font troubleshooting required
  • Costs you selectable text and a bigger file
Why does my PDF look fine on my computer but wrong on someone else's?

The document uses a font that isn't embedded in the file and isn't installed on the other person's device, so their PDF viewer substitutes the closest match it can find, which can shift layout, line breaks, and page count.

What are the “standard 14” PDF fonts?

Times, Helvetica, Courier, Symbol, and ZapfDingbats, each in regular, bold, italic, and bold-italic where applicable. Every compliant PDF viewer is guaranteed to have these without any embedding required.

Do I need to embed Arial or Times New Roman?

Not usually. They're metric-compatible with Helvetica and Times and tend to substitute cleanly, but unlike the actual standard 14, that behavior isn't formally guaranteed.

How do I check if a PDF's fonts are already embedded?

Open it in Adobe Acrobat or Reader and go to File → Document Properties → Fonts tab. It lists every font used in the document and marks which ones are embedded.

Does embedding fonts make my PDF file bigger?

Yes, since the font's outline data gets copied into the file itself. Most software offers a “subset” option that only embeds the specific characters actually used, which keeps the size increase small.

Try the tools ✦

Free browser tools that never upload your files.

Open Tools