Build a PDF Document Capture Application with the Acrobat SDK
Question details
Create a Windows application that scans multiple pages into sequentially named PDFs and supports page management, viewing, and printing.

- Product
- Adobe Acrobat SDK and Acrobat Pro
- Device & OS
- Windows
- Scenario
- A .NET development team wants to integrate a TWAIN scanner with Acrobat PDF workflows.
- Observed behavior
- The intended application should acquire scanned pages, create named PDF files, manage their pages, and let users view and print them.
Confirm the installed Acrobat version and review its SDK documentation for the supported Windows integration models. Install the scanner's TWAIN driver and verify that the device can scan from a TWAIN-compatible application.
Combine the Acrobat SDK with a TWAIN scanning library
Use a separate scanner interface for image acquisition and Acrobat integration for supported PDF operations.
The Acrobat SDK provides documentation and samples for Acrobat automation and plug-in development. Check the documentation for the intended Acrobat version before choosing an integration model.
Scanner acquisition may require a separate TWAIN library or the scanner manufacturer's SDK; do not assume Acrobat exposes a universal scanning API for the workflow.
Open the Acrobat SDK documentation and samples, then review the Windows interapplication communication and plug-in documentation for the Acrobat version you plan to deploy.
In the .NET project, integrate a TWAIN-compatible library or the scanner manufacturer's SDK. Provide an action to select the scanner and acquire multiple pages.
Use a supported Acrobat conversion workflow or a separate PDF library to turn the acquired pages into PDF files. Add a naming routine that assigns sequential filenames and checks for existing files before saving.
Use the Acrobat SDK documentation to identify supported operations for inserting, deleting, rotating, and rearranging pages in the chosen integration model. Connect those operations to controls in the application.
Use the SDK's documented Acrobat viewing and printing interfaces where supported. Test the application's view and print actions with multipage PDFs on the target Windows and Acrobat versions.

Use WPS Office for everyday PDF and document work
WPS Office is a free, lightweight alternative for working with PDFs and Office documents through a familiar interface. Its format compatibility helps teams move existing files into WPS, although it does not replace the Acrobat SDK or a TWAIN library for building the capture application.

Frequently Asked Questions
Can the Acrobat SDK acquire pages from any TWAIN scanner?
Do not assume it provides a universal scanning API. Check the SDK documentation for your Acrobat version and use a TWAIN library or the scanner manufacturer's SDK if separate acquisition is needed.
How can the application name PDFs sequentially?
Add a naming routine in the .NET application that increments a number for each new PDF. Check the destination folder for existing filenames before saving to avoid overwriting files.
Where can I find examples of Acrobat automation?
Review the Acrobat SDK documentation and samples for Windows interapplication communication. The Acrobat SDK forum is another place to ask about a specific integration workflow.
Can WPS Office replace the Acrobat SDK in this project?
WPS Office can open and print PDFs for everyday use, but it does not replace the Acrobat SDK or a TWAIN scanning library for building this capture application.




