Usually the file was flattened: something turned every form field into ordinary page artwork, so the boxes still show but nothing can go in them. Printing to PDF is the most common culprit. Less often, nothing happened to the file at all. It's an Adobe-only XFA form and you've opened it in a different app this time. Either way you can check in a minute and get a working form back.
A fillable PDF is two things stacked. Underneath is the page: labels, lines, boxes. On top is a layer of fields, each one a named box with a type and a position. When you type, your answer goes into a field.
Flattening paints whatever is in each field onto the page and then deletes the field.
On screen almost nothing changes, which is why it's so confusing. Clicking a box is where you find out.
There's no undo. The fields aren't hidden somewhere in the file waiting to be switched back on, and no setting brings them back. Once they're gone the file is in the same category as a form someone laid out in Word and exported.
Chrome or Edge "Save as PDF". This is the big one. Someone opens the form in their browser, wants a copy, presses Ctrl+P (Cmd+P on a Mac) and picks Save as PDF as the destination. Printing redraws the page as a printer would see it, and printers don't have fields.
Every browser Save as PDF file in the real forms we test against was flat. "Microsoft Print to PDF" on Windows and the PDF button in the macOS print dialog work the same way, for the same reason.
Spot it in ten seconds. Open the file in Adobe Acrobat Reader and go to File, then Properties. If the "PDF Producer" line says Skia/PDF, the file came out of Chrome or Edge's print dialog. That's your culprit.
A flatten option somewhere. Plenty of tools flatten on purpose and say so in small print. Canva's download has a "Flatten PDF" tick box under PDF Print. Many online PDF editors and compressors flatten as a side effect, and some merge tools flatten pages before combining them so that two fields both called "Name" can't clash.
A viewer that saved over it. macOS Preview fills simple forms, but its handling of form fields when it saves a file back out is unreliable, particularly after pages have been rotated, added or removed. Some phone apps behave similarly. The trigger is usually innocent: someone opened the form, rotated a page, and pressed Save.
A signature. Certifying or signing a document can lock it on purpose. The fields survive and refuse input, which looks the same from the outside and needs a different fix.
"It worked yesterday" sometimes means it worked in a different app yesterday.
Some forms, mostly government, tax and immigration paperwork, are built in an older Adobe format called XFA. They fill in perfectly in Adobe Acrobat Reader. Open the same file in Chrome, Edge, macOS Preview or a phone app and you get this instead of the form:
Waiting longer won't help. The browser can't display this kind of form at all.
So yesterday you opened it from your desktop in Adobe Reader, and today you tapped it in an email on your phone. Same file, different app.
Save it to a computer and open it in Adobe Acrobat Reader (free). One warning: don't press Save as PDF on that "Please wait..." page to "get a copy that works". You'll get a nicely saved PDF of the waiting message.
The free fillable PDF checker reports whether the file still has real fields and how many, whether the page is flat, or whether there's no readable text at all (someone printed it and scanned it back in, which also happens).
Or match what you see:
What you see
What probably happened
Boxes visible, clicking does nothing, Tab goes nowhere
Flattened
Old answers highlight like ordinary page text when you drag over them
Flattened, with the answers painted in
A single page saying "Please wait..."
XFA form opened outside Adobe's apps
Fields highlight but won't take typing
Locked by a signature or password
Works for you, not for the person you sent it to
Their app, not the file
For the last two, try Adobe Acrobat Reader before anything else.
One thing flattening never causes is a form that types fine on screen and then prints empty. Flattening makes answers permanent, so if the text survives right up until you print it, nothing was flattened. Why a PDF form prints blank covers the three faults that do cause that.
Look for the original. Check the email thread it arrived in, the shared drive, or the website you downloaded it from. A copy from before the Save as PDF step still has its fields. Use that and treat the flattened one as an accident.
If there's no original, put fields back on the flattened page. It's a good case for automatic detection, because flattening leaves the ruled boxes and underscored blanks exactly where they were, and those are what detection looks for.
Check for old answers first. If the flattened copy has someone's answers painted into it, new fields can't remove them. You'll need a blank copy for that.
Detected fields on a flat form. The Phone line was missed here, so that's one box you'd draw yourself.
You check the suggestions, rename any label that came out wrong, and draw what was missed. The page artwork isn't touched. A one-page form takes a few minutes. How to make a PDF fillable without Acrobat goes through it step by step.
A fillable PDF is a fragile thing to send round. It has to survive every app, every save, and every helpful person who tidies it into a pack, and any one of them can quietly turn it back into a picture. You won't hear about it. The person who received it assumes they're doing something wrong.
Keep the copy with working fields as a master that you never open in a viewer and save over. Send copies.
Better still, stop sending the file. If people fill the form in their browser from a link, there's no fillable PDF in circulation to flatten, and each response comes back as the original PDF with the answers drawn onto the page. The HR and hiring templates are set up this way: job applications, new-starter details and handbook sign-offs that go out as a link rather than an attachment.
Common questions
Why did my PDF form stop being fillable?
Almost always because the file was flattened. Flattening turns each form field into ordinary page artwork, so the boxes stay visible but nothing can go in them. Printing to PDF, a flatten option in an export or editing tool, and some viewers that re-save the file all do it.
Does "Save as PDF" in Chrome remove form fields?
Yes. Choosing Save as PDF in the Chrome or Edge print dialog redraws the page the way a printer would see it, and printers have no fields. Any answers typed in are kept as page text, and every empty box becomes a drawing.
Can I undo flattening and get the fields back?
No. The fields are not hidden somewhere in the file waiting to be switched back on. Either go back to a copy from before it was flattened, or put fresh fields on the flattened page.
It worked yesterday and today it only says "Please wait...". What happened?
Probably nothing happened to the file. It is an XFA form, which only Adobe's apps can display, and you have opened it in a different app this time, such as a browser or a phone. Open it in Adobe Acrobat Reader on a computer.
My form still shows fields but they are locked. Is that the same problem?
No. Locked fields are still fields, and something is refusing input, usually a signature or a permissions password. Flattened fields are gone. The fillable PDF checker tells the two apart.
How do I stop it happening to the next version?
Keep the copy with working fields as a master you never save over, and send copies. Or stop sending the fillable file at all and share a link to an online form, which nobody can flatten.