Why Acrobat Preflight Identifies OpenType Fonts as Type 1
Question details
The user needs to understand why Adobe Acrobat Preflight reports that an exported PDF contains Type 1 fonts, even though the original source document used OpenType fonts.

- Product
- Adobe Acrobat
- Device & OS
- not provided
- Scenario
- Analyzing an exported PDF/X file using Acrobat Preflight to verify font formats.
- Observed behavior
- Acrobat Preflight flags the embedded OpenType font (such as Frutiger) as a Type 1 font, raising concerns about Adobe's end of support for Type 1 fonts.
Ensure you have access to both the original source document and the exported PDF file to properly verify the font formats used before and after exporting.
Understand PDF Font Embedding and Conversion
Learn how the PDF export process converts OpenType fonts into Type 1 format for embedding, and why this triggers the Preflight warning.
Acrobat Preflight analyzes the actual font data embedded inside the exported PDF file, not the original font selected in your authoring software like InDesign. During the PDF/X export process, certain OpenType fonts (specifically those with PostScript outlines) are often converted or embedded in a way that the PDF specification and Preflight recognize as Type 1.
Because the PDF creation process modifies how the font is packaged, the warning generated by Preflight is technically accurate for the PDF file itself, even though your source document used an OpenType font. Furthermore, Acrobat Preflight cannot be used to reliably determine the original font format used in the source file prior to export.
Open your original document in the authoring program (e.g., InDesign) and navigate to 'Type' > 'Find/Replace Font' to confirm that the OpenType format is actively applied to your text.
When exporting your document to PDF, check the 'Advanced' tab in the export dialog to review how fonts are subsetted and embedded into the final file.
Open the exported PDF in Adobe Acrobat, go to 'Tools' > 'Print Production' > 'Preflight', and review the font warnings to ensure no unsupported missing fonts are flagged.

Manage and Edit PDFs Seamlessly with WPS Office
If you need a lightweight and reliable alternative to handle PDF documents without complex preflight errors, WPS Office provides a powerful built-in PDF editor. It easily opens, views, and edits PDFs while preserving embedded font formatting.
- 1. Open Your PDF in WPS Office: Launch WPS Office and click on 'Open' to load your exported PDF document into the application.
- 2. Access the PDF Editor: Navigate to the 'Edit' tab on the top ribbon to modify text, check layout, and verify how the embedded fonts are rendered.
- 3. Export and Save Safely: Use the built-in 'Save As' or 'Export to PDF' tools to save your document with proper standard font embedding for seamless sharing.

Frequently Asked Questions
Why do OpenType fonts become Type 1 fonts in a PDF?
During the PDF export process, authoring applications may convert OpenType fonts that have PostScript outlines (CFF) into a standard Type 1 format to properly embed them into the PDF structure. Acrobat Preflight simply reads this converted embedded format.
Will embedded Type 1 fonts in my PDFs stop working due to Adobe's policy changes?
No. Although Adobe has dropped support for authoring and creating new documents with Type 1 fonts, any Type 1 font already embedded inside an existing PDF file will continue to display, render, and print perfectly.
Can I use Acrobat Preflight to check the fonts in an InDesign file?
No, Acrobat Preflight can only analyze the resulting fonts that are embedded within the generated PDF file. To check the original fonts of an InDesign file, you must use the font management tools within InDesign itself.




