-
Notifications
You must be signed in to change notification settings - Fork 120
Bug Report: Hyperlinks on objects are lost when exporting to PDF via getFileAsync on Mac #6567
Description
Provide required information needed to triage your issue
Your Environment
- Platform [PC desktop, Mac, iOS, Office on the web]: Mac
- Host [Excel, Word, PowerPoint, etc.]: PowerPoint
- Office version number: 16.106.3 (26030211)
- Operating System: MACOS
Expected behavior
When calling the Office.js API Office.context.document.getFileAsync with Office.FileType.Pdf, the resulting PDF file should preserve hyperlinks that have been applied to objects (shapes, images, etc.), similar to how it functions in PowerPoint for Windows.
Current behavior
On PowerPoint for Mac, when a PDF is generated using getFileAsync, any hyperlinks attached directly to objects (not text) are missing in the final PDF output. The objects appear correctly, but they are not clickable. This issue does not occur on Windows, where object hyperlinks are preserved in the exported PDF.
Steps to reproduce
Open PowerPoint on Mac and create a new presentation.
- Insert a shape (e.g., a rectangle) or an image.
- Right-click the object and add a hyperlink (e.g., https://www.microsoft.com).
- Use an Office Add-in to call Office.context.document.getFileAsync(Office.FileType.Pdf, ...) to retrieve the PDF version of the document.
- Save and open the generated PDF.
- Observe that the hyperlink on the object is not functional.
Link to live example(s)
- link-test.pptx
- windows-exported.pdf - Correct behavior
- mac-exported.pdf - Buggy behavior
Provide additional details
- This issue specifically affects hyperlinks attached to the container/object itself, whereas hyperlinks attached to text within a text box seem to work correctly.
- The issue has been consistently observed since early 2026.
- There is a clear platform disparity between Windows and Mac regarding this API's PDF export result.
Context
This issue prevents us from providing a consistent user experience across platforms. Our Add-in relies on getFileAsync to generate interactive PDF reports for users, but Mac users are currently receiving "broken" PDFs where the interactive elements (links on shapes/icons) do not work.
Useful logs
- Console errors
- Screenshots
- Test file (if only happens on a particular file)