Why is my PDF form no longer fillable?
Almost always the file was flattened: every form field was converted into ordinary page artwork, so the boxes are still visible and no longer hold anything. Something in the chain did it — a print-to-PDF step, a merge, a signature, or a viewer that rewrote the file when it saved. The fields are not hidden or switched off. They are gone, and the way back is to place fresh ones.
What flattening actually does
A fillable PDF carries two separate things. There is the artwork — the lines, labels and boxes drawn on the page — and there is the AcroForm, a set of named data containers, each with a type, a page number and a rectangle of coordinates. Typing into the form writes a value into a container. The container is what makes the file fillable.
Flattening merges the second thing into the first. The current value of each field is painted onto the page as static text, and the container is deleted. Visually almost nothing changes, which is exactly why it is so confusing: the form looks identical, the boxes are still ruled, and clicking one does nothing at all.
The important consequence is that this is one-way. There is no hidden layer to restore and no setting to reverse. Once the containers are gone the file is artwork, in the same category as a form somebody designed in Word and exported.
What flattens a form
Print to PDF, or Save as PDF from a print dialogue. This is the most common cause by a distance. Printing re-renders the page from scratch and writes out what the printer would have put on paper. Printers do not have form fields, so none survive. People do this without noticing, usually while trying to save a copy.
Merging or combining files. Stitching several PDFs together makes some tools flatten everything first, because merging two documents that both contain a field called full_name raises a question the tool would rather not answer. Others preserve fields and quietly rename the duplicates, which causes a different and subtler mess.
A certifying signature. Signing a document can lock it against further change by design — that is the point of certifying it. Fields may survive here and simply refuse input, which is a different problem with the same symptom.
A viewer that re-saved it. Preview on macOS has a long history of mangling AcroForms when it writes a file back out. Various browser viewers and mobile apps do the same. The trigger is often innocuous: someone opened the form, added an annotation or rotated a page, and hit save.
How to tell which one you have
The symptoms overlap enough that guessing wastes time, and the three cases need different responses. Upload the file to the free fillable PDF checker — it reports whether the file still has real fields and how many, whether the page is flat with none at all, or whether there is no readable text either, which means somebody scanned a printout.
By hand, two tests get you most of the way. Press Tab: in a file with live fields the cursor jumps between them, and in a flattened file nothing moves. Then try to select the text of an answer that was already filled in. If it highlights as ordinary page text, that value has been painted on and the field behind it is gone.
If the fields are still reported as present and still will not take input, you are looking at a lock rather than a flattening, and the fix is different — try a different reader first, because a surprising share of these turn out to be the reader rather than the file.
Getting a working form back
If you still have the version that had live fields, use it, and treat the flattened copy as the accident it was. Check any shared drive or mail thread for the file as it was before the step that broke it.
If you do not, the flattened page is your starting point and fields have to go back on top of it. That means marking a rectangle wherever an answer belongs and choosing what kind of answer it takes, one at a time. Knowing the page is flat does not place anything for you. A one-page form is a few minutes of work, and the original artwork is untouched — you are restoring the containers, not redrawing the document.
Stopping it happening again
The underlying problem is that a fillable PDF is a fragile thing to put in circulation. It has to survive every reader, every save and every well-meaning person who merges it into a pack, and any one of them can quietly turn it back into a picture. You will not hear about it when it happens, because the person who received it will assume they are doing something wrong.
Keep the version with live fields as a master you never save over, and send copies. Better, stop distributing the file at all: if people complete the form through a link in a browser, there is no fillable PDF in circulation for anyone to flatten, and the completed document comes back to you as a finished PDF each time. The HR and hiring templates are the same forms set up that way — applications, new-starter details and handbook acknowledgments that go out as a link rather than an attachment.