Most often it is the browser viewer. Values live in the viewer rather than in the file, and the download button hands you the original.
The fix that always works is flattening: the values become ordinary page content, so they display everywhere and cannot be lost.
This is a genuinely maddening failure because nothing warns you. The form accepts your typing, the save appears to succeed, and the loss only surfaces when someone opens the file and finds it blank.
The browser viewer
By far the most common cause, and the one that catches people who did everything reasonably.
Opening a PDF link in a browser tab loads it into the browser's own viewer. You type into the fields and the values are held by the viewer in memory. Clicking download then does what it says: it downloads the file from its source, which is the empty original. Your answers were never part of it.
Legacy reader rights
For many years, free Adobe Reader could display and fill a form but not save the completed values unless the document had been specially enabled with a feature called Reader Extensions, applied by the form's author.
Forms produced under that assumption are still in circulation, often from organisations whose form templates have not been revisited in a decade. Modern readers generally allow saving regardless, but a document carrying those older flags can still behave unexpectedly depending on what opens it.
- Filled in a browser tabViewer held the values
- Message about saving a copyLegacy usage rights
- Please wait placeholder pageXFA form
- Saves in one reader, not anotherReader support differs
- Values show for you, not themRecipient's reader
XFA forms
If the document shows a message asking you to open it in Adobe Reader, the real form is an XML payload rather than PDF content. Other tools can render only the placeholder page, and anything typed into an approximation of the form has nowhere to be stored.
Adobe Reader handles these properly. Otherwise, asking the issuer for an ordinary PDF form is often successful, since most organisations have moved away from XFA.
When they save but the recipient cannot see them
A different and quite common variant. The values saved correctly and the recipient opens the file to find it blank.
Field values are stored separately from the page content, and displaying them requires the reader to render the form layer. A reader with limited form support, or a viewer showing only the page content, displays the empty form underneath. Your values are in the file and their software is not drawing them.
Flattening
Flattening draws the current field values onto the page as ordinary content and removes the fields. The document looks identical and stops being a form.
Reliable everywhere
- Values are page content, visible in any reader
- Nothing can be edited or cleared by accident
- No dependency on form support
- Prints exactly as it displays
- Safe to send to anyone
Still a live form
- Values depend on the reader drawing the form layer
- Recipients can change the answers
- A stray click can clear a field
- Some viewers show the blank form underneath
- Right only while you may still need to edit
Print to PDF as a fallback
If no flattening option is available, printing the filled form to PDF achieves the same thing. The virtual printer receives the page as rendered, including the field values, and writes them as ordinary content.
It is cruder than a proper flatten and it works reliably. The one thing to check is that the print preview actually shows your values, since a reader that was not drawing them on screen will not print them either.
Fill and build PDF forms
Complete a form or make one fillable, in your browser. Nothing is uploaded.
Common questions
Getting the values to persist.
01Why do my form answers disappear when I reopen the file?
Most often because you filled the form in a browser tab. The values were held by the browser's viewer, and the download button fetched the original empty file. Download the PDF first, then fill it in a proper reader and save.
02What does flattening do?
It draws the current field values onto the page as ordinary content and removes the form fields. The document looks the same, the values become permanent, and no reader can fail to display them.
03The recipient says the form is blank, but it looks filled to me. Why?
Field values are stored separately from page content, and displaying them requires the reader to draw the form layer. Their software is showing the empty page underneath. Flattening before sending prevents this entirely.
04What is the message about saving a copy?
A legacy behaviour where free readers could fill a form but not save the values unless the author had specially enabled the document. Modern readers mostly allow saving, but older forms carrying those flags can still behave oddly.
05Can I unflatten a form?
No. Flattening converts values into page content and discards the fields, which cannot be reconstructed. Keep the blank original so you can fill it again if an answer needs changing.
06Is printing to PDF a reasonable substitute for flattening?
Yes, when no flatten option is available. The virtual printer receives the page as rendered, values included, and writes them as ordinary content. Check the print preview shows your answers before relying on it.