Fillable PDF forms vs flat exports

A flat export has no fields left to click, and a fillable file is a poor final record because those fields can still change. Send the fillable PDF for collection. After it is filled and signed, flatten the copy you keep or distribute. Word's own PDF export may keep or drop fields depending on the export settings, so test every field. The browser Word to PDF tool extracts text and does not keep form fields. Merge PDF and Split PDF assemble the packet. They do not create the fields.

HR once emailed a benefits form as a "final PDF." The checkboxes did not click. The export from the design tool had burned the fields into static artwork. Enrollment week turned into print, scan, and fax.

On screen the two files can look the same until someone tries to type.

Fillable forms

Interactive PDFs (AcroForm, or the older XFA) can include:

• Text fields
• Checkboxes and radio buttons
• Dropdowns and date pickers
• Digital signature fields
• Calculated fields, with limited support

People fill them in Acrobat, in Preview (only partly), in a browser viewer (it varies), or in a phone app.

Use this when you are collecting data, running an internal form, or matching a government template that requires the fields.

Flat exports

Flattening merges the field values into the page content, or the export never had fields. You get:

• No clickable controls
• Print output that matches the screen
• Fewer reader quirks
• A file that is harder to change without a visible edit

Use this for a final contract, an invoice for the records, a published brochure, or an assignment that has to keep its layout.

Side by side

| Aspect | Fillable | Flat | | --- | --- | --- | | Recipient edits fields | Yes | No | | Print appearance | Empty fields can print oddly | What you see is what prints | | Archive or legal final | Risky unless you lock it | Preferred | | File size | Slightly larger | Often smaller | | Completing it on a phone | Variable | Not applicable; it is read-only | | Pulling the data back out | Possible with tools | OCR if the page was scanned |

Patterns that work

Collect, review, flatten

1. Send the fillable application.
2. The recipient completes it and sends it back.
3. HR reviews it while the fields are still live.
4. Flatten to a static PDF for the personnel file.
5. Optionally Merge PDF with supporting documents. See Merge PDF Without Losing Formatting.

Word, then PDF

Word's own export may keep or lose fields depending on the export settings. The browser Word to PDF tool does not keep fields. Test every field after conversion. Embedding fonts when exporting Word to PDF stops a layout shift that moves the boxes off the lines.

Forms that still have to be handwritten

Some agencies want a flat scan of handwriting. They will not take a digital fillable submission. Confirm that before you build the interactive version.

Security

Fillable fields can hide metadata. Flatten before an external archive. See PDF metadata: what it reveals.

For passwords, see PDF password protection explained.

For signed agreements, see Digital signatures in PDF.

Phones and screen readers

Phone PDF readers often struggle with tab order and small checkboxes. If most people will use a phone, a web form may fit better than a PDF. Test against mobile PDF editing limits.

Tags and field labels matter for screen readers. See PDF accessibility basics.

Mistakes

• Designing in Canva and expecting fields. That export is flat.
• Flattening before anyone has reviewed the answers. A typo then needs a new issue of the file.
• Mixing XFA and AcroForm. Enterprise readers handle that badly.
• Emailing a fillable file that contains JavaScript. Corporate readers block it.

When the file has to be flat

• A court filing that specifies a non-interactive PDF
• Print-shop prepress. See printable PDF margins
• A student submission. See submitting assignments as PDF
• A client proof. Watermark the flat export. See client proof PDF watermarks

Tools around the form

• Assemble the packet with Merge PDF
• Split returned sections with Split PDF
• Compress for email. See how to compress a PDF and email attachment PDF size limits

Government and healthcare forms

Medicare, tax, and court forms often publish an official fillable PDF with strict field names. Do not flatten it before the submission portal upload. A healthcare intake form may need to stay fillable for an EHR import. Confirm that the HL7 or FHIR integration expects AcroForm names that match the spec.

XFA

Older enterprise forms use XFA (XML Forms Architecture). Adobe Acrobat Reader supports it. Many browser viewers do not. If the form fails in Chrome, check for XFA and offer an Acrobat download or a web form.

Check before you send it

• [ ] Tab order follows the keyboard
• [ ] Required fields are enforced
• [ ] Calculated fields compute correctly
• [ ] The submit button does what you expect (email, save, or print)
• [ ] A phone reader your audience uses has been tested

Limits

AcroForm fields behave differently in mobile previewers and in browser PDF tabs. Once a form is filled and signed, flatten the copy you distribute so a viewer quirk cannot edit or hide a value.

Use fillable for collection and flat for the copy that has to stay put. Export on purpose, test one device your recipient actually has, and flatten before you archive. A benefits form that does not click is the wrong PDF type.