Optimize Filled PDF Forms for Universal Compatibility

Share this page

Turn Completed Forms into Stable PDF Records

Interactive PDF forms are useful while information is being collected, but their behavior can become a problem after submission. Field values may still be editable, and some viewers or downstream systems do not reproduce every form technology consistently. Dynamic XFA is especially dependent on Adobe-compatible rendering because its layout can change in response to data.

The pdfRest Flatten Forms API Tool converts filled form fields into fixed page content. It preserves the visual appearance of the completed values while removing the interactive fields, producing a standard, non-editable PDF that is easier to view, print, distribute, and process across varied systems. pdfRest supports Acroforms, Static XFA, and Dynamic XFA through Adobe PDF technology.

For example, an insurance platform may receive completed claim forms from several agencies. Some arrive as Acroforms and others use legacy XFA templates. Once the claim is accepted, the platform can flatten each document into a stable record that displays the submitted values without requiring the recipient's viewer to support the original form system.

Use Flattening at the Finalization Point

Flattening is most valuable when a form has reached a state that should no longer be edited. Common examples include signed applications, approved claims, completed onboarding forms, regulatory submissions, and records entering an archive. The flattened PDF retains the visible content while removing the controls used to enter or change it.

This simplifies downstream workflows. A document viewer can present ordinary page content, a print service can process the result without interpreting form widgets, and a records system can store the finalized representation. The output also receives a pdfRest resource ID that can continue to PDF/A conversion, encryption, redaction, merging, or another required operation without an intermediate download.

An application can connect flattening to a business event such as approval, signature completion, or case closure. That makes form finalization a repeatable system rule rather than a manual “print to PDF” step and gives every source form the same controlled destination.

Keep Forms Interactive When the Workflow Requires It

Not every XFA form is ready to become a fixed record. When users still need to enter or revise values, the XFA to Acroforms API Tool provides a different modernization path. It converts Static or Dynamic XFA into the more broadly supported Acroforms format while retaining interactive form functionality.

The workflow decision is straightforward: use XFA to Acroforms when the document must remain fillable, and use Flatten Forms when the completed values should become fixed page content. Because both tools handle Static and Dynamic XFA with Adobe technology, applications can support legacy form collections without building a separate conversion system for each template type.

Flatten a Completed Form with One Request

The cURL example below sends a filled PDF to /flattened-forms-pdf and assigns a name to the finalized output.

Flatten a Completed PDF Form Code Example | Load this into API Lab↗

# By default, this request uses the US-based API service.
API_URL="https://api.pdfrest.com"

# For the EU-based service, use:
# API_URL="https://eu-api.pdfrest.com"

curl -X POST "$API_URL/flattened-forms-pdf" \
  -H "Accept: application/json" \
  -H "Content-Type: multipart/form-data" \
  -H "Api-Key: xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" \
  -F "file=@/path/to/completed_form.pdf" \
  -F "output=finalized_form"

The same endpoint accepts a resource ID instead of another file upload, making it easy to flatten a form produced or modified by an earlier pdfRest step. This chainable approach supports a complete forms lifecycle—from interactive collection through final delivery and retention—inside one API toolkit.

Use API Lab to run the flattening request. The Flatten Forms and XFA to Acroforms API references provide current endpoint fields for the fixed-record and interactive-form paths.

Flatten Forms