6 min read
How to embed fonts in PDF — so it looks the same everywhere
By ScoutMyTool Editorial Team · Last updated: 2026-05-20
I sent a 30-page report to a client years ago that looked beautiful in my office and ridiculous on theirs — fonts had substituted, line breaks had shifted, the entire layout drifted off where I had placed it. The cause was a missing font-embedding flag in the PDF export. The fix takes one checkbox at export time and produces files that render identically on every recipient machine. This article maps the embedding modes, the export settings across major authoring tools, and the verification step that confirms your PDFs travel correctly.
Font embedding modes
| Mode | What it does | Best for |
|---|---|---|
| Fully embed | Entire font file included; any glyph available | Documents that may be edited downstream |
| Subset embed | Only glyphs used in document are included | Default for most documents; smallest file size |
| Reference only | Font name referenced; not embedded | Universal fonts (Times, Helvetica); falls back to substitution otherwise |
| Outline (convert to vectors) | Text converted to vector shapes; no font needed | Logos and one-off display text; not for body text |
Step by step — embed fonts and verify
- Use only fonts available on your system in the source document. Missing fonts at design time cannot be embedded at export time.
- Export with embedding enabled. Word: "Best for printing" preset. InDesign: "Subset fonts when percent..." setting at 100%. Docs: tagged-PDF default behaviour embeds.
- Verify in Acrobat Reader. File → Properties → Fonts. Every font should show "Embedded" or "Embedded subset". None should show as plain font name without embedding status.
- Test on a clean machine without your design fonts installed. Open the PDF; visual appearance should match the source design. Differences indicate substitution; fix in the source document.
- Document the font stack per project. When you re-open the document in two years, you may not remember which fonts you used; a notes file in the project folder saves the future-debugging time.
Font licensing in PDFs
Font licensing varies widely. Open-licensed fonts (Google Fonts under OFL, Open Font Library) allow free embedding in any PDF. Adobe Fonts (formerly Typekit) allow embedding via Creative Cloud subscription; verify your subscription includes the specific font for embedding. Commercial foundry fonts (Monotype, Hoefler, House Industries) often require per-document or per-application licences for PDF embedding; consult the specific font licence. Bundled OS fonts (Helvetica on Mac, Calibri on Windows) generally allow embedding with their respective OS use cases; cross-OS distribution sometimes triggers licence questions — Calibri embedded by Windows Word and opened on a Mac, for example, shows as embedded but the source licence may not technically authorise redistribution.
For documents distributed broadly, default to Google Fonts (Source Sans, Source Serif, Inter, Noto family) — all OFL-licensed, all allow embedding, all have wide language coverage. The licensing-anxiety problem disappears, and the fonts are professional-quality. For brand-specific fonts, work with your foundry to confirm PDF-embedding rights at licence purchase.
One more consideration: variable fonts. Modern variable-font formats (single file containing weight, width, and italic axes) embed cleanly in PDF 2.0 but support is patchy in older readers and PDF authoring tools. For maximum compatibility, export to PDF 1.7 and let the export step bake variable-font instances into static font files during embedding. The output PDF embeds the specific weights and widths used; variable-font flexibility is collapsed but the result renders identically everywhere. For modern-only audiences where PDF 2.0 is acceptable, embed the variable font directly to preserve future-flexibility — though re-editing PDF text after-the-fact in different weights is rare in practice.
Related reading
- Make a PDF look professional: typography rules that depend on font embedding.
- PDF for graphic designers: print-grade font handling.
- Multi-language PDF: multi-script font embedding.
- PDF to PDF/A: archival format requires embedding.
- PDF compatibility: how embedding interacts with viewer compatibility.
FAQ
- What happens if I do not embed fonts in a PDF?
- The PDF stores font references by name. When the recipient opens the file, their viewer looks for the font in their system; if missing, it substitutes the closest available font. Substitution changes line breaks, kerning, and visual appearance — a document carefully designed in Calibri can render in Arial on a different system, breaking carefully-tuned typography. For most internal-distribution documents, substitution is acceptable. For client deliverables, print-bound files, and brand-sensitive documents, always embed. PDF/A and PDF/X archival standards require font embedding; if you target either, embedding is mandatory.
- How do I check if fonts are embedded in an existing PDF?
- Acrobat Reader / Pro: File → Properties → Fonts. Each font in the document is listed with its embedding status: "Embedded subset", "Embedded", or "(not embedded)". Apple Preview: Tools → Show Inspector → Fonts. Command line: `pdffonts file.pdf` (from poppler-utils) outputs a list with embedded status. ScoutMyTool PDF Metadata Editor surfaces font-embedding status in the file properties tab. Any of these tells you in under 10 seconds whether the PDF will render reliably on recipient machines.
- What is "font subsetting" and why does it matter?
- Subsetting embeds only the specific glyphs the document actually uses, rather than the entire font file. A document that uses 50 unique characters of a font with 5,000 glyphs embeds ~1% of the font size as a subset; saves substantial file size. Subset embedding is the default in modern PDF export tools and the right choice for most documents. The one downside: if the PDF is edited downstream (text added in Acrobat Pro), the new characters may not be in the subset and either get embedded separately or substituted. For documents intended for downstream editing, full embed is safer than subset.
- Can I embed any font, or are there licensing restrictions?
- Most fonts allow embedding; some commercial fonts have licensing restrictions that limit embedding modes. The font file itself carries embedding rights via the OS/2 table fsType flag — Editable, Preview & Print, Restricted License, or No Embedding. Modern PDF export tools honour these flags automatically; you do not usually need to check manually. If a font cannot be embedded, the export tool warns or refuses to embed; you would need to substitute a similar embeddable font in the source document. Google Fonts, Adobe Fonts (subject to subscription), and most major commercial foundries allow PDF embedding; check specific font licences if in doubt.
- How do I embed fonts when exporting from Word / Docs / InDesign?
- Word: File → Save As → PDF → Options → "ISO 19005-1 compliant (PDF/A)" forces embedding; otherwise "Best for printing" preset embeds by default. Google Docs: PDF export embeds by default. InDesign: File → Export → PDF → Advanced → set "Subset fonts when percent of characters used is less than" to 100% to force full embed, or leave at default 100% threshold for subsetting. LibreOffice: File → Export As → Export as PDF → check "Embed standard fonts". After export, verify with the methods in the prior FAQ — every font in your document should show as Embedded (or Embedded subset).
Citations
- ISO 32000-1:2008 — "Document management — Portable document format" — §9.6–9.7 (Fonts).
- ISO 19005 — PDF/A archival format requiring full font embedding.
- ISO 15930 — PDF/X print format requiring font embedding.
- SIL Open Font License — open-licensed font terms.
- Adobe Type — font licensing for Adobe Fonts.
Verify font embedding in your browser
ScoutMyTool PDF Metadata Editor surfaces font-embedding status alongside other metadata. Quick check before sending PDFs.
Open Metadata Editor →