← All posts

Remove the form fields but keep what was typed in

You have filled in a PDF form. The answers are all correct, and now it has to go out as a finished document: a signed-off application, a completed return, something a colleague should be able to read but not re-type. What you want is the boxes gone and the answers still there.

So you searched for how to remove the form fields, ran the first tool that came up, and got back a blank form. Every answer went with the fields it was typed into.

That is not a bug, and no setting on that tool would have saved you. The answers were never on the page in the first place.

Why deleting the fields deletes the answers

A PDF page is a content stream: a list of drawing instructions for text, lines and images. A form field is not in that list. It lives in a separate structure called the AcroForm, held at the document level, and each field is a small dictionary with a name, a type, and a value — the thing you typed. Attached to it is a widget, a rectangle on a particular page, with an appearance stream that says how the value should be drawn inside it.

When you open the file, your reader draws the page, then draws each widget's appearance on top. It looks like one sheet of paper. It is two layers, and only the bottom one is the page.

That gives you two very different operations:

Flattening is the one you want. It is called flattening because it presses the two layers into one.

Which one you want, decided in one question

Should the finished file show the answers?

If yes, flatten. The answers become ordinary page content: readable, printable, selectable, and no longer editable by anyone, including you.

If no — you are clearing a completed form to reuse it as a blank template — then deleting the fields is correct, and Remove annotations from PDF is the tool. Choose form fields and it takes the controls and their values together, leaving the printed form itself exactly as it was.

Flattening it

Open Flatten PDF, upload the form and leave Flatten form fields ticked: that is the operation. The full run-through — what to do about review comments, what the notes on the result are telling you, and how to test the download like a sceptic — is set out in locking a filled-in form so the answers cannot be changed.

One thing has to happen before any of it, though, and it is the reason most people end up here twice.

When the file will not flatten

If the download is blank, or your reader still offers to fill something in, the cause is almost always one of three things.

The answers were never saved. The case above, and by a distance the commonest.

Dynamic XFA forms. The kind Adobe LiveCycle produced keep their layout as XML that the reader builds at opening time, so their fields are not part of any page and there is nothing to press down. Our tool tells you so rather than handing back a file that looks wrong. Open it in Adobe Reader and print it to PDF; that gives you a flat document you can work with.

The boxes were never fields. Some "forms" are a scan or a drawing with rectangles on it, and whatever you typed went into a sticky note or nowhere at all. Our PDF inspector lists what a file really contains, in the browser and without uploading it, so you can settle that in a few seconds.

There is a fourth, rarer case: a few forms carry no drawable appearance and leave the rendering entirely to the reader. We regenerate the appearances before flattening, which handles almost all of them, and the notes say when a value could not be redrawn.

What you cannot get back

Flattening cannot be undone. Not by us, not by anything. The fields no longer exist and the answers are drawing instructions in the middle of a page, so there is nothing left for a tool to read back out as a value. The only route back is the copy you kept, which is why keeping it is a step and not a footnote.

That is also the answer to the typo you find afterwards. You are editing page content now, in the PDF editor or not at all, and retyping an answer there rarely comes out matching the rest of the form. Correct the original instead, and flatten it a second time.

What flattening is not

It is not security. It removes the mechanism that let somebody re-type a field, and that is all it claims: the result is not encrypted, and page content can still be painted over by anyone determined enough. If the file also needs a password, or has to stay verifiably unaltered, Password protect PDF and a digital signature do those two jobs, in an order that matters — what each one actually buys you. If the document already has a password, you will have to take it off before you can re-protect it, which is its own short job.

Doing it without a browser

If you flatten forms often, or you cannot upload the file at all, this is a one-liner locally:

Before you send it

Flattening freezes the answers. It does not clean up everything else that travels with a working document. The review comments, if you did not flatten them, are still live objects somebody can open — strip them once the record is set. The author name and the software that made it are still sitting in the metadata, under whatever the person who first opened the template was called.

The flattened file is what you send. The original is the only thing that can ever produce a corrected one.