Do fonts need to be embedded for print?
Short answer
For print exchange, fonts should be embedded (or converted to outlines) so every machine that opens the PDF sees the same type. An unembedded font can be substituted, reflow the layout, or stop the RIP. Checking embedding before production is cheaper than reprinting.
What embedding actually does
Embedding stores the font data inside the PDF. The receiving RIP does not need the font installed locally. Subsetting keeps file size down by including only the glyphs used. Without either, the viewer or RIP may pick a substitute font with different metrics.
Font Helvetica Embedded no Risk substitute · layout shift · job reject
Embed vs outline
Embedding keeps text selectable and editable downstream. Outlining converts type to paths — safer for some cutters and when the foundry licence forbids embedding, but you lose live text. The right choice is a workflow decision, not a universal rule.
How to check before you send
Run a preflight that lists fonts that are not embedded. A free font check reports the names so your message to the designer is specific: which font, not “fix the fonts.” Then re-export with embed enabled, or outline if that is your shop standard.
- Ask for PDF export with fonts embedded / subset
- Or convert type to outlines if your workflow requires it
- Re-check the replacement file before production
How Prepta handles it
The free public check reports fonts that are not embedded and notes live text for review. Full Prepta applies your profile’s font policy — report, outline, or escalate — without silently substituting type.