PDF Missing Embedded Fonts: Why Text Looks Wrong and How to Fix It
You create a beautifully formatted PDF using custom fonts, share it with a colleague, and they tell you the document looks completely different — the fonts have changed to something generic, some text appears as boxes or question marks, and the carefully crafted layout has fallen apart. Or you open the PDF yourself on a different computer and see the same problem. This is a font embedding issue. When a PDF doesn't embed the fonts it uses, the viewer has to find matching fonts on the computer where the PDF is being viewed. If those fonts aren't installed on that computer, the viewer substitutes the closest available font — which is almost always wrong, causing text to look different and layouts to break. Font embedding is how PDFs are supposed to work: the font data is stored inside the PDF file itself, guaranteeing that the document looks the same everywhere, on any computer, forever. But font embedding can fail to happen, get stripped during processing, or be deliberately omitted to reduce file size. Understanding when and why fonts get missing from PDFs lets you prevent the problem and fix it when it occurs.
How Font Embedding Works in PDFs
A PDF file can reference fonts in three ways: embedded (font data is stored in the PDF), subset-embedded (only the characters actually used in the document are stored), and referenced-only (the PDF names the font but doesn't include the data, relying on the viewer to find it). Full font embedding stores the complete font including all characters. This ensures every possible character renders correctly but increases file size. A complete Unicode font can contain 65,000+ characters and add megabytes to the PDF. Subset embedding is the best practice for most documents. Only the specific characters used in the document are embedded. A document using only English text might embed just 95 characters from a font that contains thousands. The file size increase is minimal, and the document looks correct everywhere. Referenced-only fonts (sometimes called 'non-embedded' or 'font not embedded') are a problem. The PDF names the font (like 'Helvetica Neue') but doesn't include the font data. If the viewer has that font installed, it looks correct. If not, the viewer substitutes a similar font — often incorrectly, causing spacing, weight, and rendering differences. Standard fonts (Type 1 fonts like Helvetica, Times New Roman, Courier, Symbol, and Zapf Dingbats) are specified in the PDF standard and are available in all PDF viewers without needing to be embedded. All other fonts — including most modern OpenType and TrueType fonts — should always be embedded.
- 1Open the PDF in Adobe Acrobat and go to File > Properties > Fonts tab
- 2Check the 'Embedded' column for each font listed — it should say 'Embedded Subset' or 'Embedded'
- 3Any font showing no embedding status is a potential display problem on computers that don't have that font
- 4Note which fonts are not embedded — you'll need to either embed them or replace them
- 5Standard fonts like Helvetica, Times New Roman, and Courier are safe without embedding
Why Fonts Get Stripped or Lost
Even if your PDF was created with properly embedded fonts, several operations can strip or damage the embedded font data. Aggressive compression is a common culprit. Some PDF compression tools remove embedded fonts as a size-reduction strategy, replacing them with referenced fonts or substitutions. This dramatically reduces file size but breaks font rendering on systems without those fonts installed. Format conversion is another frequent cause. Converting a PDF to another format and back (PDF to Word and back, PDF to HTML and back) almost always loses font information. The intermediate format may not support the same fonts, and the re-export to PDF references fonts rather than embedding them. Document assembly operations that don't handle fonts correctly can also cause issues. When merging PDFs from different sources, some merge tools don't consolidate the font tables correctly, causing fonts from one document to override or interfere with fonts from another. Older PDF creation software sometimes created PDFs with referenced-only fonts because embedding was optional and increased file size. Documents created in the 1990s and early 2000s frequently have this problem. PDF printing (using 'Print to PDF' from an application) typically does embed fonts correctly since it rasterizes the output. However, some virtual PDF printers configured with minimal settings may not embed fonts to save processing time.
- 1Identify whether fonts were embedded in the original PDF before any processing
- 2If fonts disappeared after compression, the compression tool stripped them — use a different tool
- 3If fonts disappeared after a format conversion cycle, re-export from the original source file
- 4For old PDFs with referenced fonts, the source application may no longer exist — see the flatten workaround
- 5For merged PDFs with font issues, check each source file separately to identify which had the problem
Fixing Missing Font Issues
The best fix for missing font embedding depends on whether you have access to the original source file or only the PDF. If you have the source file (Word, InDesign, PowerPoint, or any application): re-export the PDF with font embedding enabled. In most professional applications, font embedding is enabled by default. In Word, go to File > Save As > More Options and check 'Embed fonts in the file' or use the PDF export option which embeds fonts automatically. In Adobe InDesign or Illustrator, all fonts are embedded by default unless explicitly excluded. If you only have the PDF and cannot go back to the source, the cleanest workaround is to flatten the document to images. Use LazyPDF's PDF to JPG tool to convert each page to an image — this renders all text using the currently available fonts (or the embedded ones if they still exist) and captures the visual appearance as pixels. Then use Image to PDF to reassemble into a PDF. The resulting PDF will look visually identical to the original (assuming fonts were available when you did the conversion), but the 'text' is now part of the page images rather than separate text objects. The downside is that the text is no longer searchable or selectable — so if you need text functionality, apply OCR afterward using LazyPDF's OCR tool. For documents where you need both correct appearance and searchable text: flatten to images, then apply OCR. The OCR creates a new, properly encoded text layer based on what it reads from the images, which will use standard fonts that work everywhere.
- 1If source file available: re-export PDF from the original application with font embedding enabled
- 2If only PDF available: use LazyPDF PDF to JPG to render all pages as images
- 3Use Image to PDF to reassemble pages into a new PDF with visual content intact
- 4Apply OCR using LazyPDF OCR to add a searchable text layer to the image-based PDF
- 5Verify the final PDF displays correctly by opening on a different device or in a different viewer
Preventing Font Embedding Issues in Future PDFs
The most reliable way to prevent font problems is to verify font embedding before sharing any PDF created with custom fonts. In Adobe Acrobat (Reader or Pro), go to File > Properties and click the Fonts tab. Review every font in the list. Any font without 'Embedded' or 'Embedded Subset' in the description is potentially problematic. If you see unembedded custom fonts, go back to the source application and re-export with embedding enabled. For documents intended for wide distribution, use standard system fonts (Arial, Times New Roman, Georgia, Verdana) instead of custom fonts when possible. Standard fonts are available on virtually all computers and PDF viewers without embedding. The design flexibility is reduced, but compatibility is guaranteed. For documents where custom fonts are essential (brand documents, marketing materials, publications), use PDF/A format for archival documents — PDF/A requires all fonts to be embedded and verified, ensuring long-term accessibility. Export as PDF/A from Adobe Acrobat or InDesign for documents that must render correctly decades from now. When sending PDFs with custom fonts to print shops, email them the PDF font list from Acrobat's properties and confirm the shop's system has the same fonts. Professional print shops typically request PDF/X or PDF/A versions precisely to avoid font compatibility issues in their production workflow.
Frequently Asked Questions
Why does my PDF look right on my computer but wrong on my colleague's?
Your computer has the custom fonts installed (probably from the same design software that created the document), so your viewer uses the installed fonts even though they are not embedded. Your colleague's computer does not have those fonts, so their viewer substitutes the closest available font, which renders differently. The fix is to re-export the PDF from the source application with font embedding enabled so the font data travels with the file.
Some text in my PDF shows as boxes or question marks — what does that mean?
Boxes or question marks where text should be usually means the PDF references a font that is not installed on the viewing system AND the viewer cannot find a suitable substitute. This is common with specialty fonts (symbol sets, icon fonts, dingbats, non-Latin scripts) where there is no obvious fallback. The fix is the same: embed the font in the PDF by re-exporting from the source with embedding enabled, or flatten to images which renders the boxes or marks as visible symbols rather than font references.
Does font embedding significantly increase PDF file size?
Subset embedding (which most modern PDF creation tools use automatically) adds only the characters actually used in the document, which is typically 5–30KB per font for Latin text. For a document using three custom fonts, this adds roughly 30–90KB to the file size — imperceptible relative to the total file size of most documents. Full font embedding (all characters) can add much more, but subset embedding is sufficient for sharing PDFs and is what tools like Word and InDesign use by default.
Can I embed fonts in a PDF without the original source file?
Directly embedding fonts into an existing PDF requires the font files to be installed on your computer and requires tools like Adobe Acrobat Pro (Preflight > Fix > Embed All Fonts). Without Acrobat Pro, the practical workaround for a PDF-only workflow is the flatten-to-images method: convert to images (which captures the current font rendering) and reassemble as a PDF. This preserves visual appearance without requiring access to the font files.