If you’ve ever opened a PDF form in Chrome and seen “Please open this document in Acrobat”, you’ve met XFA. Here is why.
Two models, very different
AcroForms are fillable fields overlaid on a static page. They work in every viewer. Data lives in the PDF’s object tree and extracts easily to JSON or CSV.
XFA (XML Forms Architecture) is a form-definition language that generates pages on the fly. It was popular in government forms until Adobe deprecated it in Acrobat DC. XFA forms do not render in Chrome, Edge, Firefox, Safari or on mobile without Acrobat Reader.
How to tell what you have
Open the PDF in a text viewer. If you see <x:xfa> or <template> somewhere, it is XFA. AcroForms have /AcroForm entries in the catalog dictionary.
Why XFA keeps shipping
Despite deprecation, agencies continue to publish XFA forms because they offer runtime arithmetic and conditional sections. The real alternative is a web form — but XFA sits on top of print infrastructure dating back decades.
Converting XFA to AcroForms
Our Enterprise appliance includes an XFA-to-AcroForm transpiler. It flattens dynamic sections to the longest possible layout and preserves field names and types. Many government forms have been successfully migrated this way.
Data extraction
From AcroForms, you can read /V entries directly. From XFA, you must parse the embedded XML datasets. Both are easy once you know where to look; our API returns a normalised JSON regardless.
Signatures
Both form types support PAdES signatures, but XFA signatures tie to a specific rendering, which is why they often appear invalid in non-Acrobat viewers. If you require legal signatures, use AcroForms with a flattened PDF/A-3 wrapper.
Tags: #AcroForm #XFA #PDF forms #fillable PDF #form data extraction
Leave a Reply