Others

How to Create a Top-Level Menu with an Acrobat API File

Huda QurayshiHuda Qurayshi Nov 3, 2026 869 views

Question details

The developer needs to create a custom top-level menu using an API file in Acrobat.

How to Create a Top-Level Menu with an Acrobat API File
Product
Adobe Acrobat API
Device & OS
not provided
Scenario
Developing an Acrobat plug-in to introduce custom functionality and a top-level menu interface.
Observed behavior
The custom menu requires correct compilation, valid extension identifiers, and specific directory placement to successfully appear in the Acrobat or Reader interface.
Before you start

Ensure you have the Acrobat SDK installed and your development environment configured for the target Acrobat version and architecture.

Solution 1Recommended

Verify Plug-in Compilation and Installation

Compile the code correctly and ensure the plug-in is installed in the proper Acrobat directory to load the menu.

Acrobat relies on compiled plug-ins to generate custom menus via the API. The process requires a valid extension identifier and specific function calls like AVAppGetMenubar and AVMenuNew.

1
Compile the plug-in

Compile your Acrobat plug-in code in your IDE, ensuring that the extension identifier is valid and matches Acrobat API requirements.

2
Install in the correct directory

Navigate to the installation directory of your Adobe Acrobat or Adobe Reader, locate the 'plug_ins' folder, and place your compiled plug-in file inside.

3
Check API return values

In your code, verify the return values from the AVAppGetMenubar and AVMenuNew API calls to confirm that the menu object is successfully created.

4
Test architecture compatibility

Restart Acrobat and test the newly added top-level menu, ensuring you are testing on the supported Acrobat version and architecture.

Verify Plug-in Compilation and Installation
Development Best Practice: Release objects only when appropriate in your code to prevent memory leaks, and post implementation follow-ups under the original development question to maintain full context.
Free Microsoft Office alternative

Experience Seamless Document and PDF Management with WPS Office

While custom API plug-in development is strictly for Acrobat environments, everyday users and professionals can view, edit, and convert PDFs effortlessly using WPS Office. It provides a comprehensive, lightweight suite for all your document needs without complex configurations.

Fully compatible with Microsoft Office formats (Word, Excel, PowerPoint) and standard PDFs.Free, lightweight, and easy-to-use alternative to heavy PDF editors.Familiar user-friendly interface requiring no specialized development.Seamless migration for all your daily document workflows.
microsoft office alternative - wps office

Frequently Asked Questions

Why is my custom top-level menu not appearing in Acrobat?

This typically happens if the plug-in is not installed in the correct Acrobat 'plug_ins' directory, or if the AVAppGetMenubar or AVMenuNew API functions return null values due to an invalid extension identifier.

Where should I place my compiled Acrobat plug-in?

The compiled plug-in file must be placed directly into the designated 'plug_ins' folder within your Adobe Acrobat or Adobe Reader installation directory.

Does WPS Office support Acrobat API files?

No, WPS Office utilizes its own independent PDF engine and does not support or load third-party Adobe Acrobat API plug-in files.