Fix Custom Font Substitution When Creating PDF from Word on Mac
Question details
Users experience custom font substitution when generating a PDF from a Word document on Mac.
- Product
- Adobe Acrobat Pro DC
- Device & OS
- macOS
- Scenario
- Converting a Microsoft Word document containing non-system custom fonts (e.g., Nobel) into a PDF file.
- Observed behavior
- The custom font is replaced with a generic font in the resulting PDF, even though the original font is locally installed on the Mac and available for editing within Acrobat.
Ensure that your custom fonts are fully installed and validated in the macOS Font Book, and check that they are properly applied to the text in your original Word document.
Use a Local Desktop Conversion Workflow
Bypass Adobe's cloud-based conversion service to ensure your locally installed macOS fonts are properly embedded in the PDF.
Adobe's cloud-based PDF creation service cannot access custom fonts installed only on your local Mac hard drive. If the font is not a standard system font or synced via Adobe Fonts, the cloud server will substitute it with a default alternative.
By switching to a local conversion method, you force the software to utilize your Mac's native font library, preserving your document's original appearance and embedded hyperlinks.
Launch Microsoft Word on your Mac and open the document that contains your custom fonts.
Navigate to 'File' in the top Apple menu bar and select 'Print', or press Command + P on your keyboard.
At the bottom of the print dialog window, click on the 'PDF' dropdown menu and select 'Save as PDF'. This utilizes the native macOS local PDF creator instead of Adobe's cloud.
Choose your desired save location, enter a file name, and click 'Save'. The PDF will be generated locally, correctly embedding all custom fonts.
Export Word to PDF without Font Substitution using WPS Office
WPS Office processes your document conversions locally on your Mac. This guarantees that any custom fonts installed on your machine are perfectly preserved and embedded into your exported PDF without relying on external cloud services.
- 1. Open Your Document in WPS Office: Launch WPS Office on your Mac and open the Word document containing your custom fonts.
- 2. Verify Font Appearance: Scroll through your document in the WPS Writer interface to ensure your custom fonts are loaded and displayed correctly.
- 3. Export Locally to PDF: Click on 'Menu' at the top left, select 'Export to PDF', configure your save settings, and click 'Export'. The file will be saved locally with all fonts embedded perfectly.
Frequently Asked Questions
Why does Adobe Acrobat substitute my fonts on Mac?
Acrobat often defaults to Adobe's Document Cloud for converting Office files to PDF. The cloud server does not have access to custom fonts installed locally on your Mac, forcing it to substitute them with standard available fonts.
How can I verify if a custom font is properly embedded in my PDF?
Open the generated PDF in Adobe Acrobat, navigate to File > Properties, and click on the Fonts tab. Here you will see a list of all fonts used in the document; look for the words 'Embedded' or 'Embedded Subset' next to your custom font's name.
Does changing the font file format fix the substitution issue?
Not usually. While standard TrueType (.ttf) and OpenType (.otf) formats are generally well-supported, the primary cause of substitution during cloud conversion is the server's inability to access your local machine's Font Book, regardless of the font's specific file format.
