PDF Form Fields Won't Fill? Flat Forms, Permissions, and Preview Bugs

You downloaded the form, opened it, clicked the first box — and nothing happened. Or worse: you typed, it looked filled, and after save-and-reopen everything's blank again. Form failures are almost never "the PDF is cursed." They're one of three mechanical issues.

Cause 1: It's not a form — it's a picture of a form

Scanned forms, print-to-PDF exports, and Word forms saved without field objects produce flat PDFs: rectangles drawn on the page, no AcroForm fields underneath. Clicks land on artwork.

Test: click inside a box — no caret, no highlight, Tab doesn't jump. Hover: sometimes the entire row lights up as one blob (it's an image, not a field).

Fix paths:

• Get the true fillable original from the issuer (best);
• Use an editor's "add text field / annotate" mode to type on top (works, but values are annotations, not field data — see flatten realities);
• Print a paper copy if the form demands field-level integrity you can't fake.

Cause 2: Permissions say no

A PDF can open fine while form filling is disabled by permission flags — the owner/permission layer, not encryption of content (password types). Compliant readers gray out fill; some don't even gray, they just ignore keystrokes.

Test: Document Properties → Security. If "Changing the Document" / filling is restricted, that's your answer.

If it's your file: re-protect with filling allowed (protect guide — fill permission is an advisory flag for compliant readers). If it isn't your file: ask the sender for an unlocked/fillable copy. "Unlocking" someone else's restricted form without authorization is bypassing their controls — out of scope, ethically and often contractually.

Cause 3: Your viewer is the problem

Field support varies:

• Browser built-ins — fine for basic AcroForms, weaker on legacy XFA;
• macOS Preview — known to demand owner passwords on permission-locked forms when you only meant to fill;
• Old desktop readers — stale field engines miss newer appearance streams.

Test: open the same file in a second app. If app B accepts input, the PDF was never broken — switch apps or update. Only when every viewer fails should you suspect field corruption; then get a fresh copy (integrity checks).

Save-then-blank: the other classic

You filled fields, saved, reopened — empty. Usual causes: you closed without saving (apps lie about autosave state), you filled in a view-only annotation layer that wasn't persisted, or you reopened the original instead of the saved output. Habit: save to a new filename, close fully, reopen that file, spot-check three fields before you leave the desk.

Flatten when the form is done

Filled and final? Flatten converts fields to static page content — values print exactly, nobody can silently re-edit answers, and viewers without field support still show what was entered. Flatten after filling and before signatures you care about (or per your signature workflow — sign-last still rules: signature validity). Then the pre-send checklist catches the rest.