Always embed your CJK fonts fully. Never rely on the F1 fallback. For designers: If your PDF uses F1 Family, re-embed the original fonts before commercial printing. For archivists: The F1 Family is a warning sign. Your metadata is already degrading. Key Takeaways (FAQ Style) Q: Is CID Font F1 Family a virus? A: No. It is a standard font subsystem component in Adobe software and Ghostscript.
A user receives a PDF that looks perfect on screen (rendered by the F1 family) but when they copy text to Notepad, they get: cid font f1 family
/CIDFont/F1Family /NotoSansCJK-Regular ; /CIDFont/F1Family /SourceHanSans-Regular ; Then run: Always embed your CJK fonts fully
Introduction: The Ghost in the PDF Pipeline In the world of digital typography and document engineering, few acronyms cause as much confusion—or as many technical support tickets—as the term "CID Font F1 Family." For archivists: The F1 Family is a warning sign
When a PDF cannot locate the original embedded font (perhaps a corporate-specific Japanese font like "Ryumin-Light"), it substitutes the . The "F1 Family" is the operating system's default CID fallback—often mapped to Source Han Sans , Noto Sans CJK , or MS Gothic . Part 3: Where Does the F1 Family Come From? You will typically encounter this font family in three specific scenarios: Scenario A: PDF/A Archiving When a legacy document is converted to PDF/A (an ISO-standard archival format), fonts must be embedded. If the original CJK font does not allow embedding (due to licensing), the converter replaces it with a built-in F1 synthetic CID font family. Scenario B: Ghostscript and PostScript Rendering Open-source renderers like Ghostscript use CIDFont F1 Family as a default placeholder. When Ghostscript processes a PostScript file with a missing CJK font definition, it falls back to a built-in CID-keyed font. Inspecting the gs command line with -dFONTMAP often reveals:
A: Use Acrobat Pro > Preflight > Embed all fonts or use command line tools like cpdf -replace-font to substitute a real OpenType font. Last updated: October 2023. Specifications based on Adobe Technical Note #5014 and ISO 32000-2:2020.