Fonts in PDFs for business mail: embedding, subsets and missing characters
A document looks right on its author’s computer, but different letters or blank characters appear after handover for printing. Start with the final PDF, not the source file.
An incorrect character in a name or a substituted typeface can hold up an otherwise ready mailing batch. A preview on a computer with the original font installed is not sufficient evidence that another environment will reproduce the document correctly.
This guide addresses fonts and characters in PDFs handed over for printing. It does not replace checks of content, recipient data or the full print-run specification. It focuses on one practical handover between the document author and the team managing production.
1. Distinguish font embedding from a font name
Embedding includes font data inside the PDF. Adobe distinguishes between the complete font and a subset containing characters used in the file. Either can be valid. Seeing a typeface name in a list does not establish that the necessary font data is included.
If a font is neither embedded nor available in the recipient’s environment, substitution may occur. Do not equate that with identical character shapes. Record three distinct findings in the working check: embedded, embedded subset, or embedding not confirmed.
2. Inspect the file after the last export and merge
In Adobe Acrobat, open the final document’s properties and its Fonts tab. Review every entry, including different styles of the same typeface. Do not stop at the first name. Keep the finding with the identifier of the PDF inspected.
If an attachment is then added, a page changed or files merged again, check the new output. An earlier assessment does not automatically cover a later export. An empty font list may also mean that text is stored as images or outlines; it does not prove correct characters or readability.
3. Do not reject a valid font subset
A subset is not inherently a damaged file. For a completed, self-contained PDF, the key question is whether the characters actually used in that document render correctly. Do not demand a complete font solely because the report identifies a subset.
For personalised mail, inspect the file after recipient data has been inserted, not the empty letter template. New names, place names or currency symbols may require characters absent from the template. After data changes, regenerate the PDF and repeat the check instead of assuming the earlier result still suffices.
4. Combine technical findings with a character test
Prepare a non-production test set covering the languages and symbols in use, for example Łódź, ñ, ü, ß, €, and the pairs 0/O and 1/l. Inspect the corresponding positions in the final PDF and an agreed print sample. A sample does not guarantee an entire run, but can expose a specific class of errors.
Adobe Acrobat Pro provides Preflight inspection, and a resource inventory can help examine embedded glyphs, or character shapes. Distinguish missing embedding, a missing character and incorrect content. A successful technical report does not verify the spelling of a name or the intended recipient.
5. Fix the cause rather than just the warning
Begin with analysis without automatic correction. If a font is missing, return to the source application and export settings. Embedding also depends on permissions in the font; selecting a checkbox does not override a restriction. Do not send font files to a contractor without checking their permitted use.
Work on a copy and agree changes with the document owner. Do not convert all text to outlines or images as a default cure: this affects later text handling and does not correct wrong content. After an approved fix, recheck the PDF and the sample where the change requires one.
6. Hand over an unambiguous inspection result
A useful issue report identifies the file version, page, font, incorrect character and expected result. Agree who fixes the source, repeats the export and approves the output. Send production the exact file inspected, not a similarly named document from an earlier email.
BackOffice Outsourcing offers document printing and enveloping. When outsourcing business mail, agree the input format, issue-reporting route and sample-approval rules beforehand. Describe your file workflow to the team to define an appropriate scope. Colour is addressed separately in the guide to logo colour in printing.
Sources and scope
- Adobe: Embedding fonts in PDFs overview
- Adobe: PDF creation settings - fonts
- Adobe: Analyzing documents with the Preflight tool
- Adobe: Preflight reports
Adobe documentation checked on 18 October 2026. Product features are not a claim that BackOffice Outsourcing uses that software. The test set, responsibilities and handover procedure are editorial proposals to agree for each job.
FAQ
Does every PDF contain embedded fonts?
No. The PDF extension does not confirm font embedding. Check the final document, not merely the template settings.
Is an embedded subset an error?
Not by itself. Check the characters used in the completed PDF. Repeat the inspection after data changes or file merging.
Does a successful Preflight replace content approval?
No. Results depend on the inspection profile, and technical validity does not verify names, addresses or meaning.
Must text always be converted to outlines?
No. Do not use this as the default fix. Agree the cause, correction method and later document-use requirements with its author.
