You fill in a PDF form, it looks fine, you send it, and the other person says it’s blank. Or you open it yourself the next day and half the answers have gone. Usually your answers are still in the file. The file just keeps them in a way that some apps don’t show.
The quick fix: flatten the form and send that copy. Flatten PDF does it in your browser without uploading the file. The answers become ordinary page content, so there is nothing left for another app to get wrong. Keep your original, because a flattened copy can’t be edited again.
Why it happens
A form field holds an answer twice: the answer itself, and a small drawing of how it looks in the box. Most apps simply show the drawing. So when a program saves the answer but not a matching drawing, what you see depends on which app opens the file. That is why it can look perfect for you and empty for someone else.
What we saw when we tested it
On 3 November 2026 we saved the same form, with one answer typed in, four different ways. We opened each copy in Chrome 156 and Edge 156 on Windows 11. We also drew each page as a flat image with pdf.js, the PDF engine used in Firefox, to see what an app shows if it only draws the page and doesn’t handle the form.
| How the form was saved | Chrome 156 | Edge 156 | pdf.js, page drawn flat |
|---|---|---|---|
| Answer plus a matching drawing (the normal way) | Correct | Correct | Shown |
| Answer only, with a note asking apps to draw it | Correct | Correct | Shown |
| Answer only, no note | Correct | Correct | Blank |
| New answer, but the drawing still shows the old one | Old answer | Old answer | Drew the old drawing |
| Any of the four, flattened with our tool | Correct | Correct | Shown, as page text |
Two things stand out. Chrome and Edge rescue a missing drawing, so opening a “blank” file in a browser is a fast way to find out whether the answers are really there. And the fourth row is worse than a blank: the person reading it sees a wrong answer and has no reason to doubt it.
How to check whether your answers are still there
- Save the attachment first rather than reading it in an email preview or a phone’s quick view.
- Open it in Chrome or Edge by dragging the file into a browser window. If the answers appear, they are in the file, and the problem is the app that showed it blank.
- Still empty? Then the answers probably never got saved. Some apps let you type into a form and then save an empty copy. You’ll need to fill it in again, using something that confirms the save. Fill PDF Form reopens the saved file and reads each answer back to you.
How to fix it before you send it
- Open Flatten PDF and drop in the filled form.
- Read the result. It tells you how many fields had an answer with no drawing, and how many showed different text from the stored answer. In both cases it draws the stored answer, so check those boxes.
- Download the copy ending in
-flattened.pdfand open it once to look it over. - Send that copy, and keep the original in case something needs changing.
In the same test, all four flattened copies showed the new answer in both browsers and in pdf.js. The real USCIS Form I-130 came through too: its 450 fields were flattened, and all 12 pages looked exactly the same as before, pixel for pixel, when drawn with pdf.js. That was the blank form, with no answers typed in.
When not to flatten
- Someone else still has to fill in part of it. Flattening removes every field, so send the normal copy and ask them to open it in Chrome, Edge or Adobe Acrobat Reader.
- The office reads the form automatically. Some systems pull answers out of the fields, and a flattened form has none. If the instructions say to keep the form fillable, keep it fillable.
- It already has a digital signature. Flattening changes the file, so the signature stops verifying. Flatten first, then sign.
If the form shows “Please wait…” instead
That is a different problem: an Adobe XFA form that browsers can’t draw, and flattening can’t read it either. See why you can’t type in some PDF forms for what to do.
What we tested, and what we didn’t
Windows 11, Chrome 156 and Edge 156 built-in viewers, and pdf.js 6.3, on 3 November 2026. The four forms are our own test files, made from one fillable form so that we knew exactly what each contained. We don’t know which real apps save which way, so we can’t tell you that a particular app caused your problem. Plenty of people report it, though, as in this thread on Adobe’s forum. We didn’t test Adobe Acrobat Reader, Mac Preview, phones, email previews or real printers. A flattened copy should behave the same in those, because its answers are ordinary page content, but we haven’t checked.