Why Some PDF Forms Won't Fill In (AcroForm vs XFA Explained)

You download a tax form, a permit application, or a healthcare intake sheet. You open it in Preview, a browser, or any sensible PDF viewer. The fields look like fields — they have borders, they have labels — but when you click in them, nothing happens. No cursor, no typing, nothing. The form is a PDF, it opens fine, and it refuses to be filled. You have not done anything wrong. The form was built on the wrong standard.

There are two competing fillable-form technologies inside the PDF ecosystem, and most users have no idea. They have nearly opposite compatibility characteristics, they are both called "PDF forms" in everyday conversation, and the fact that one of them is dying quietly while the other keeps working is responsible for an enormous amount of wasted user time. This post explains the split, how to tell which kind of form you have in front of you, and what to do when you get the wrong one.

The two form standards in one paragraph

The PDF format has supported fillable form fields since version 1.2 in 1996. That original, universally supported standard is called AcroForm. Around 2003, Adobe pushed a much fancier alternative called XFA — XML Forms Architecture — which treated the "form" as an XML document rendered inside a PDF wrapper. XFA supports dynamic layouts, JavaScript-driven logic, and complex data binding. AcroForm supports static fields with basic formatting. XFA requires Adobe's full desktop Reader; AcroForm works in every PDF viewer ever shipped. Most government forms produced between 2005 and 2017 were XFA; most forms produced since about 2020 are AcroForm again, because Adobe deprecated XFA in PDF 2.0.

If a form opens in Preview, Chrome, Firefox, or any mobile PDF viewer and the fields work, it is AcroForm. If the same form refuses to accept input and you see a warning bar at the top saying "Please wait..." or "This PDF form is not compatible with this viewer," it is XFA.

Why XFA is effectively dead

Adobe itself killed XFA. The PDF 2.0 specification (ISO 32000-2, 2020) formally deprecates XFA, and Adobe announced end-of-support with specific deadlines — XFA support was phased out of their web and mobile readers first, with full deprecation completed in recent major releases of Acrobat DC. Modern browsers that ship with built-in PDF viewers (Chrome, Edge, Firefox, Safari) never supported XFA in the first place. macOS Preview does not support XFA. No JavaScript-based open-source PDF library we are aware of — pdf.js, pdf-lib, PDFKit — parses XFA form fields well enough to render them as interactive inputs.

The practical result: a form authored in XFA around 2010 and uploaded to a government portal can still exist, still look authoritative, and still refuse to be filled by 90% of the software in use today. The original Reader installers that could handle it are harder to find every year. From the user's side it feels like the form is broken. It is not broken. It is built on an abandoned technology.

AcroForm, by contrast, keeps working. It is defined directly in the core PDF specification, every viewer supports it, and it is what any form you generate today should target.

How to tell which kind of form you have

Four diagnostic signals, cheapest first:

1. Opens-everywhere test. Open the file in three different viewers — say, Preview, Chrome, and any mobile PDF app. If the fields work in all three, it is AcroForm. If the fields work in none of them but there is a banner saying "Please open this in Adobe Reader," it is XFA.

2. The yellow banner. Open the file in Adobe Acrobat Reader DC. XFA forms frequently show a yellow banner at the top of the document window: "If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document." That banner is XFA's tombstone.

3. Command-line inspection. Run pdftotext yourfile.pdf - or pdfinfo yourfile.pdf. If the Form: line says AcroForm, great. If it says XFA or dynamic XFA, you have the dying standard.

4. File size check. XFA forms are often surprisingly large (500 KB to several MB) for what looks like a simple form, because they carry the full XML schema and rendering engine descriptors internally. A pure AcroForm tax-style document is rarely more than 200 KB.

Why modern tools cannot "convert" XFA to AcroForm

It is a common request. It is also, unfortunately, mostly a dead end. XFA forms can contain dynamic layout rules that reflow as users add rows, JavaScript that computes totals across fields, and data bindings to external XML schemas. None of that survives a direct translation to AcroForm, which is a flat, static field model. You can extract the current visible appearance of an XFA form — the fields in their default layout — and generate an AcroForm version with the same field names, but you lose everything dynamic. For a tax form that relies on dependent calculations, that is a real loss of functionality.

A few commercial tools (Acrobat Pro's own Prepare Form tool, some server-side libraries) will attempt this conversion. The output is often usable but rarely perfect. If the form is simple — name, address, signature, a couple of checkboxes — the conversion works fine. If the form has 40 calculated fields and three reflowing tables, you will spend more time fixing the conversion than filling the form manually.

Practical workarounds when you get an XFA form

In order of how painful they are:

1. Install the full Adobe Acrobat Reader DC and open it there. Current versions still support at least static XFA in most cases, though dynamic XFA has been progressively deprecated. This is the path of least resistance if you only need to fill the form once.

2. Use Adobe's fillable web service. Adobe offers an online form-fill tool at acrobat.adobe.com that handles XFA server-side. Upload the form, fill it in, download the result. Works but requires trusting a third party with the form data.

3. Print, fill by hand, scan. Unromantic but bulletproof. Useful for forms you need to submit once.

4. Print-to-PDF with fields filled. If you can fill the form in any XFA-capable viewer, then use "Print to PDF" as your final export. The output is a flat PDF — no live fields, but all the content is baked into the static page. This is our recommended path for forms you need to file electronically once the fields are filled.

5. Flatten the filled form. If you managed to fill an XFA form but the recipient wants a regular PDF without the dynamic machinery, use our Flatten PDF tool to collapse all form fields and annotations into their rendered appearance. The result is a static PDF that looks exactly like the filled form.

A related problem: forms that look fillable but will not save

Sometimes the form works in your viewer, you fill it in, you save, and the next person opens your file to find every field blank again. This is usually not a form problem — it is a browser-viewer limitation. The built-in PDF viewers in Chrome, Firefox, and Edge handle AcroForm display but do not always save filled data back into the file on download. The form was fillable on screen, but "Save" pulled the original empty PDF from cache instead of persisting your inputs.

Fixes:

• Open the PDF in a proper desktop viewer (Preview on macOS, Acrobat Reader on Windows), fill there, File → Save.
• Use our Edit PDF tool, which reads AcroForm fields, writes your input, and saves a properly modified PDF you can verify before sending.
• If the recipient explicitly needs a non-editable final, fill it, then flatten to bake the values in.

The "filled form does not save" problem is almost always the browser viewer, not the PDF. Switch tools.

Honest caveats

Our Edit PDF tool supports AcroForm fields — it reads the form-field objects defined in the PDF's core structure, lets you fill them, and saves them back into the file. It does not support XFA forms, because no practical browser-side library implements the XFA rendering engine. If you upload an XFA form to our tool, you will see the page content but not interactive fields, and we will tell you so explicitly. For XFA, one of the workarounds above is your best path.

The good news: the forms people are creating today are almost all AcroForm. XFA is a retirement-home standard. The workarounds above are for old government and enterprise forms that have not yet been re-authored, and that category is shrinking every year.

Fill or flatten a PDF form now

Edit PDF (AcroForm fields) — free | Flatten a filled form — free