Fix Missing Fonts When Creating PDFs Through Adobe Cloud
Question details
The user needs to fix an issue where custom fonts are substituted during cloud-based PDF conversion in Word for Mac.
- Product
- Adobe Acrobat Cloud / Microsoft Word
- Device & OS
- Mac
- Scenario
- Converting a Word document containing custom fonts to a PDF file using the Adobe Create PDF cloud service.
- Observed behavior
- Custom fonts (such as Panton) are replaced by default fonts (like Courier) in the output PDF generated by Adobe Cloud, whereas local PDF exports preserve the fonts correctly.
Verify that all custom fonts used in your document are fully installed on your Mac system and that you have embedded them in the source file before attempting any PDF conversion.
Use Word's Built-in Local PDF Export
Bypass the Adobe cloud service entirely by utilizing Microsoft Word's native local export feature to guarantee exact font preservation.
The font substitution issue is a known limitation of the Adobe Create PDF cloud service when triggered from Word for Mac. The cloud service cannot access the local font library on your Mac, replacing unavailable custom fonts with standard ones like Courier. Using a local conversion method avoids this limitation.
Open your document in Word for Mac, go to the top menu bar, click on 'File', and select 'Save As'.
In the 'File Format' dropdown menu, choose 'PDF'.
Select the option 'Best for electronic distribution and accessibility' (uses Microsoft online service) or 'Best for printing' (uses macOS local engine) depending on your needs. For strict local font embedding, 'Best for printing' is highly reliable.
Click 'Export' to save the PDF to your local drive. Check the resulting file to confirm the custom fonts are preserved.
Use Adobe Acrobat Desktop Application
Use the full locally-installed desktop version of Adobe Acrobat instead of the cloud-based add-in to process the file using local system fonts.
Preserve Custom Fonts When Converting to PDF with WPS Office
Avoid cloud conversion limitations and font substitution entirely. WPS Office natively supports high-fidelity, local Word to PDF conversion directly on your desktop, ensuring custom fonts are perfectly embedded and preserved without requiring third-party add-ins.
- 1. Open your document: Launch WPS Writer and open the Word document containing your custom fonts.
- 2. Access the Export to PDF tool: Click on 'Menu' in the top left corner, then select 'Export to PDF'.
- 3. Configure output settings: In the export dialog, choose your desired save path and confirm the document quality settings.
- 4. Export locally: Click 'Export to PDF'. The software uses its local engine to generate the file, keeping all custom fonts intact.
Frequently Asked Questions
Why does Adobe Cloud replace my custom fonts with Courier?
This happens due to a known limitation in the Adobe Create PDF cloud service for Mac. The cloud server performing the conversion does not have access to the local font files installed on your Mac, so it substitutes missing fonts with a default standard like Courier.
Will embedding the fonts in Word for Mac fix the Adobe Cloud issue?
Unfortunately, no. Even if you embed the fonts in the source Word document, the Adobe Create PDF cloud service on Mac often ignores or strips them during upload and processing. Using a local conversion method is the recommended solution.
How can I report this conversion bug to Adobe?
You can report the issue through Adobe's official feedback channels. Visit the Adobe Acrobat UserVoice forum and search for 'Create PDF through the Adobe Create PDF cloud service from Word for Mac does not maintain fonts' to add your vote and comments.
