A PDF that looks different from the document it was created from — using a different font, with different spacing, or with text that doesn't quite align — has a font embedding problem. Understanding why it happens leads directly to the fix, whether you're dealing with your own PDF or one you received.
What Font Embedding Means and Why It Matters
When a PDF is created, it can either embed the font files used in the document or simply reference them by name. Embedded fonts travel with the PDF — the document contains everything needed to render the text correctly, regardless of what fonts are installed on the viewer's device. Referenced fonts rely on the viewer's device having the same font installed; if it doesn't, the viewer substitutes the closest available alternative.
Font substitution is the root cause of most font differences between an original document and its PDF. A document that used "Futura" with a specific weight and tracking gets opened on a device without Futura installed — the viewer substitutes a similar sans-serif font, but the substitution has different metrics, and suddenly line breaks change, text overflow occurs, and the layout shifts.
Why Fonts Sometimes Don't Get Embedded
Font embedding is usually on by default in modern export tools, but several things can prevent it. Some fonts have licensing restrictions that prohibit embedding — the font file includes a flag that tells PDF exporters not to embed it. When the exporter respects this restriction, the font is referenced by name but not included in the file.
Older versions of Word and some other applications have export settings that default to not embedding fonts, or have minimum embedding options that embed only some characters. Documents exported in compatibility mode or through print-to-PDF drivers sometimes fail to embed fonts that a direct export would have included.
Checking Whether Fonts Are Embedded
In Adobe Reader or Acrobat, go to File → Properties → Fonts tab. This shows every font used in the document and whether it's embedded. Fonts listed as "Embedded" or "Embedded Subset" are contained in the file. Fonts listed without that notation are referenced only — they'll substitute on devices that don't have them installed.
If you see a font without embedded status and you're experiencing rendering differences, that font is the likely culprit.
Fixing the Problem at the Source
The most reliable fix is to re-export the PDF with font embedding explicitly enabled. In Microsoft Word: File → Save As → PDF → Options → check "ISO 19005-1 compliant (PDF/A)" which forces full embedding, or look for an "Embed fonts in the file" checkbox. In Adobe InDesign or Illustrator, the export dialog has explicit font embedding options. In Google Docs, font embedding happens automatically on export.
If the font has licensing restrictions that prevent embedding, the options are: switch to a freely embeddable alternative font with similar metrics (Google Fonts offers many professional options that embed freely), purchase an embedding license for the font if your use case justifies it, or accept the substitution and choose a widely available font that renders consistently without embedding.
When You Receive a PDF With Wrong Fonts
If someone sends you a PDF that looks different on your device than intended, the sender's fonts weren't embedded. You can't fix this without the original source document — the font data simply isn't in the PDF file. Contact the sender and ask them to re-export with fonts embedded, or ask for a version using standard system fonts like Arial, Calibri, or Georgia that are available on virtually every device.
For your own PDFs going forward, using an PDF Editor that confirms font embedding status before finalizing the document eliminates this problem before it reaches whoever you're sending to.