Fonts are not embedded in my PDF

A PDF is supposed to be self-contained. When a font is embedded, the glyph outlines travel inside the file and the text renders identically everywhere. When it is not, the opening application substitutes whatever it considers closest.

The failure is quiet, which is what makes it costly. The document still opens. The text is still there. But the metrics differ, so line breaks move, a heading that fitted on one line wraps onto two, and a carefully set price list stops aligning. Nobody notices until it has printed.

Why fonts fail to embed

• Licensing. Some fonts carry embedding restrictions in their metadata, and a compliant exporter will honour them and leave the font out.
• The wrong export preset. Screen or web presets routinely omit embedding to save file size. Print presets such as PDF/X include it.
• Missing at export time. If the font was not properly installed, the application may have already substituted before the PDF was written.
• System fonts. Some are assumed to exist everywhere and are excluded. That assumption breaks the moment your file meets a different machine.

The reliable fix

Export to a PDF/X standard. Embedding is part of the specification rather than an option, so the export fails loudly instead of producing a file that is quietly wrong.

If a font genuinely cannot be embedded for licensing reasons, convert the text to outlines. The text stops being editable and searchable, so it is a last resort rather than a habit, but it guarantees the shapes are correct.

What Filecheck does

Missing fonts are detected at upload and, where the licence allows, embedded automatically so the file becomes self-contained before it reaches production. Where it cannot be resolved automatically, the upload is flagged while the customer is still there to act on it, rather than becoming your problem an hour before the run.