Other PDF Issues

Finding PDFMaker Button IDs in Microsoft Word for Automation

Huda QurayshiHuda Qurayshi Nov 3, 2026 868 views

Question details

The developer is trying to find the specific control IDs for buttons on the Acrobat PDFMaker tab in Microsoft Word, such as the Convert to PDF button, for automation purposes.

How to Find PDFMaker Button IDs in Microsoft Word
Product
Microsoft Word
Device & OS
not provided
Scenario
Automating PDF creation or interacting programmatically with the PDFMaker add-in via custom code or macros in Microsoft Word.
Observed behavior
Developers are looking for undocumented control IDs because Adobe does not publicly expose the Ribbon button IDs for the PDFMaker add-in, preventing direct UI automation.
Before you start

Make sure you have access to the official Adobe Acrobat SDK documentation, as direct UI ribbon automation using undocumented IDs is not supported by Adobe.

Solution 1Recommended

Use the Adobe Acrobat SDK Instead of Direct Control IDs

Adobe does not provide or support undocumented PDFMaker control IDs for automation. Developers must use the official Acrobat SDK to programmatically interface with Acrobat features.

Adobe intentionally does not provide support or documentation for programmers attempting to automate the PDFMaker add-in using control IDs. Attempting to bypass this limitation by using undocumented Microsoft Word ribbon IDs can lead to unstable code that may break unexpectedly during future Office or Adobe updates.

To ensure long-term stability and receive official support, developers should transition to using the Adobe Acrobat SDK. The SDK serves as the definitive reference for all supported programming interfaces, including Interapplication Communication (IAC), allowing you to automate PDF creation without relying on UI buttons.

1
Access the official Adobe Acrobat SDK

Navigate to the Adobe Developer Console or the official Adobe Acrobat SDK documentation portal online to download the latest reference materials.

2
Review the Interapplication Communication (IAC) reference

Look for the IAC API reference within the SDK, which provides the officially supported objects and methods to automate PDF operations from external applications like Microsoft Word.

3
Implement supported API methods

Rewrite your automation scripts or VBA macros using the exposed COM objects provided by the SDK, directly invoking PDF creation methods rather than attempting to trigger the 'Convert to PDF' UI button.

Use the Adobe Acrobat SDK Instead of Direct Control IDs
Avoid Unsupported Automation: Relying on UI automation tools to click ribbon buttons or searching for hidden control IDs is strongly discouraged, as any minor patch to PDFMaker will likely break your workflow.
Free Microsoft Office alternative

A Seamless Alternative for Word and PDF Workflows

If you are building workflows that require robust word processing and built-in PDF conversion without relying on complex, unsupported third-party add-ins, consider switching to WPS Office. It handles documents seamlessly and has native PDF creation tools built right in.

Built-in Export to PDF feature without requiring third-party add-ins like PDFMaker.Highly compatible with Microsoft Word (.docx) formats.Free, lightweight, and easy to deploy for everyday document management.Familiar user interface ensuring zero learning curve for Office users.
microsoft office alternative - wps office

Frequently Asked Questions

Why can't I automate the 'Convert to PDF' button in Word?

Adobe does not expose the control IDs for the Acrobat PDFMaker ribbon buttons to the public. Automating UI elements directly is unsupported by Adobe; developers are advised to use the Acrobat SDK's programmatic interfaces instead.

Where can I find the Adobe Acrobat SDK?

You can download the Adobe Acrobat SDK and access its comprehensive APIs and documentation from the official Adobe Developer website. It contains essential reference guides for Interapplication Communication (IAC) and plugins.

Will my existing PDFMaker macros break after a software update?

If your macros rely on undocumented control IDs, send-keys workarounds, or unsupported UI automation methods, they are highly prone to breaking during Microsoft Office or Adobe Acrobat updates. Using the official SDK guarantees better stability.