Develop a Third-Party Plug-In for Adobe Acrobat
Question details
The user wants to develop a third-party application that runs inside Acrobat or Adobe Acrobat Reader, authenticates users, and performs custom tasks.

- Product
- Adobe Acrobat and Adobe Acrobat Reader
- Device & OS
- not provided
- Scenario
- A developer wants to extend an Adobe PDF application with functionality similar to a Microsoft Word add-in.
- Observed behavior
- The goal is an in-application plug-in that can authenticate users and perform custom tasks.
Identify the target Acrobat or Reader version and operating system, then review the Acrobat SDK requirements for that environment. Reader plug-ins have additional restrictions, so check Adobe's current Reader-enablement requirements before planning deployment.
Build an Acrobat plug-in with the Acrobat SDK
Use Adobe's SDK documentation and sample plug-ins as the starting point for a native Acrobat extension.
Acrobat plug-ins are generally written in C++. Depending on the tasks you implement, you may also need knowledge of PDF structure and the ISO 32000 PDF specification.
An Acrobat plug-in does not automatically work in Adobe Acrobat Reader. Review Adobe's Reader-enablement and licensing requirements for your intended use.
Open the Acrobat SDK Plug-In Guide at https://opensource.adobe.com/dc-acrobat-sdk-docs/acrobatsdk/pdfs/acrobatsdk_pluginguide.pdf and review the plug-in architecture and development requirements.
Obtain the Acrobat SDK from Adobe's developer resources, then follow its setup instructions for your target operating system and Acrobat version.
Open a relevant SDK sample in the supported C++ development environment and follow the SDK's build and installation instructions to test it in Acrobat.
Extend the sample using the SDK APIs to add your user interface, authentication workflow, and PDF-related tasks. Consult the API documentation for each operation.
Load and test the plug-in in the intended Acrobat environment. If you also need Reader support, check Adobe's current enablement requirements before testing or distributing it for Reader.

Work with PDFs and Office files in WPS Office
For everyday document work alongside your development project, WPS Office is a free, lightweight alternative with a familiar interface and support for common Office formats, making it easy to move existing files. It does not build or run Adobe Acrobat plug-ins.

Frequently Asked Questions
What language are Acrobat plug-ins written in?
Acrobat plug-ins are generally written in C++. Start with the Acrobat SDK Plug-In Guide and its sample projects to learn the required interfaces.
Will an Acrobat plug-in also work in Adobe Acrobat Reader?
Not automatically. Reader plug-ins are subject to additional enablement and licensing requirements. Check Adobe's current developer documentation before planning Reader support.
Do I need to understand the PDF specification?
It depends on the plug-in's tasks. Work involving PDF structure may require knowledge of the ISO 32000 PDF specification as well as the Acrobat SDK APIs.
Where can I find examples of Acrobat plug-ins?
Look in the Acrobat SDK sample projects and consult the Plug-In Guide for build, installation, and API guidance. A sample may provide a starting point even if it does not perform your exact task.




