How to Export Word to PDF While Preserving Links and Fonts
Question details
The user needs to convert a Word document to a PDF file without losing clickable hyperlinks or experiencing custom font substitutions.

- Product
- Microsoft Word
- Device & OS
- macOS, Windows
- Scenario
- Exporting a formatted Word document to PDF for electronic distribution and sharing.
- Observed behavior
- Exported PDF files lose functional hyperlinks, or custom fonts are replaced by system defaults, altering the document's original appearance, particularly on a Mac.
Before exporting, verify that all URLs in your Word document are formatted as active, clickable hyperlinks (usually blue and underlined) and that your custom fonts are fully installed on your operating system.
Use Word for the Web to Export the Document
Uploading your document to Word for the Web utilizes cloud rendering, which better preserves both hyperlinks and embedded fonts during the PDF conversion.
Local versions of Word, especially older Mac editions, sometimes struggle with complex font embedding during PDF exports. Processing the file via Word's web platform ensures you are using the most updated conversion engine.
In your desktop version of Word, navigate to 'File' > 'Options' > 'Save' and check the box for 'Embed fonts in the file'. Save the document.
Open your web browser, sign in to your Microsoft account, and upload the saved Word document to OneDrive.
Click on the uploaded document in OneDrive to open it inside the Word for the Web editor.
Click 'File' in the top ribbon, select 'Export', and choose 'Download as PDF'. The resulting PDF should contain intact fonts and functional links.

Use Alternative PDF Creators on Mac
If Microsoft Word's native macOS export fails, using third-party PDF generators like Adobe Acrobat or Apple Pages can accurately process the original formatting.
Export Word to PDF with Intact Links Using WPS Office
Avoid font substitution and broken hyperlinks effortlessly by using WPS Office. Its powerful, built-in PDF converter natively handles complex formatting, ensuring your documents look exactly the same across all devices.
- 1. Open Document in WPS Writer: Launch WPS Office and open your .docx or .doc file in the WPS Writer application.
- 2. Access the Export Tool: Click on 'Menu' in the top-left corner, go to 'Export to PDF', or click the dedicated 'Export to PDF' icon on the top toolbar.
- 3. Configure PDF Settings: In the dialog box that appears, select your desired export path. Ensure that 'Common PDF' is selected to maintain standard hyperlink compatibility.
- 4. Generate the PDF: Click the 'Export to PDF' button. Your document will quickly convert, preserving all custom fonts and active links seamlessly.

Frequently Asked Questions
Why do my hyperlinks disappear when I 'Print to PDF' on a Mac?
The macOS 'Print to PDF' feature is primarily designed to create a visual representation of a document for physical printing. Because of this, it automatically flattens the file and strips away interactive elements like functional hyperlinks. Always use 'Save As' or 'Export' to retain links.
How do I embed custom fonts in Word for Mac?
To embed fonts in recent versions of Word for Mac, go to 'Word' > 'Preferences' > 'Save'. Under 'Font Embedding', check the box for 'Embed fonts in the file'. Note that some protected or cloud-only fonts cannot be embedded due to licensing restrictions.
Does exporting to PDF in WPS Office require a premium subscription?
No, standard Word to PDF conversion in WPS Office is completely free and maintains basic formatting, text, and hyperlinks. A WPS Pro subscription is only required for advanced PDF editing features, like modifying PDF text or converting PDFs back to Word.
Why does my converted PDF use Arial or Calibri instead of my downloaded font?
This happens when the original font is not properly embedded in the document, or the font's license restricts embedding. The PDF reader falls back to a standard system font like Arial or Calibri to display the text. Ensuring font embedding is turned on before saving the source document usually fixes this.




