Imagine sending a poetry booklet to a printer. Every page looks right in your design app. You open the PDF on the same computer and the title still has the narrow lettering you chose. Then the proof arrives: an accented name looks different, and the page number no longer sits comfortably beside the footer. The change may have nothing to do with the paper. The first question is whether the exported file carried the font it needed.
The distinction matters because a designer usually reviews two different objects in quick succession: the working document and the exported PDF. The first can depend on resources installed on the designer’s computer. The second has to work in the printer’s process. A useful handover check looks at the final file itself, including what it contains and what the printer sees when processing it.
Read the font list in the exported file
Font embedding puts font data inside the PDF so that it can travel with the document. Adobe’s November 2025 guidance on embedding and substitution explains the distinction between including a font and substituting another when the original is unavailable. If a font is missing from the file, a local preview may still look fine when the system can access that font. A clean preview on the machine that exported the file is therefore a weak test of portability.
Open the exact PDF you will deliver and view its font information. In Acrobat, Adobe shows how to find the list under Document Properties → Fonts. Check the expected family and faces, such as the italic used in quotations and the bold used in chapter headings. The list can also expose a font you never meant to use. A stray face might come from an imported graphic or a character that was assigned a different font during layout. Treat that as a clue and trace it back to the page before changing any settings.
An embedded subset can be exactly what you need
A subset carries the characters used in the exported document. For a booklet whose text is final, that can be enough: if the page contains an accented letter and the correct glyph is in the subset, the printer does not need all the unused characters in that face. Adobe’s September 2025 overview of PDF conversion settings describes subsetting as a way to reduce file size. Seeing “Embedded Subset” is therefore different from seeing a face without an embedding indication.
A last-minute correction changes the situation. Suppose a contributor spots a missing accent on their surname. The cleanest route is to correct it in the source, export again and inspect the actual page in the replacement PDF. The old subset tells you what travelled with the old file. It cannot tell you which glyphs the new file will contain, or whether the accent came from the intended face. Reopen the new file even if the edit took only a few seconds.
There can also be a reason why a font cannot be embedded as you expected. The OpenType specification’s OS/2 table defines flags for embedding permissions, including an option that disallows subsetting. If an export reports a restriction, check the font provider’s terms and the printer’s requirements. Another export preset cannot give you permission the font provider has withheld. If you replace the face with one suitable for the job, check the line breaks, page breaks and spacing again before sending.
Proof the pages where a font change would matter
A font list can tell you what the PDF carries. A visual check tells you whether it carries what you meant to use. Pick a handful of high-risk details: a proper name with accents, a price using a currency symbol, a light italic at small size or a caption imported from a separate illustration. Compare those details in the source and exported file. If your printer offers a proof, check them there too. A physical proof can answer a different question again: whether the chosen type remains readable at size on the intended stock. That is where a soft proof of the paper and print conditions can help you decide what needs a closer look.
- Inspect the deliverable. Check the font list and the pages in the exact PDF that will go to the printer.
- Follow up on unexpected entries. Trace a missing or unfamiliar face before approving the file. Check the printer’s export requirements if you are unsure how it should be supplied.
- Repeat after changes. Open the new PDF after a correction and check that the proof being approved is for that version.
Ask the printer before treating outlined text as a default fix. As Adobe’s June 2026 guidance on making outlines explains, an outline preserves the letter shape as artwork rather than keeping it as ordinary text; that may suit a particular graphic, but an accessible digital edition has different needs. Keep the editable source and decide separately what each delivery format requires. The best question at handover is a specific one: can the recipient reproduce the type in this version, and have we both checked the pages where a small change would cause trouble?
If you commission the design, ask for a short handover note alongside the PDF. It can identify the final file, flag any deliberate exceptions and name the pages that were checked after the last export. That gives you something useful to compare with the printer’s proof, without requiring you to install the designer’s typefaces or open their working document.
Sources
- Adobe: Font embedding and substitution in PDFs (5 November 2025).
- Adobe: PDF conversion settings and checking fonts in Acrobat (23 September 2025).
- Microsoft: OpenType 1.9.1 OS/2 table specification.