Flatten a PDF Before You Send It

You filled in the form, saved it, and sent it. The reply comes back saying half the answers are blank, or that the figures have shifted out of their boxes, or that somebody in the approval chain typed over a date by accident. None of that is a mistake you made. It is what happens when a document still contains live form fields at the moment it changes hands.

Flattening is the usual fix, and it is a smaller operation than its reputation suggests. It takes the values your fields are showing right now, writes them into the page itself, and removes the fields. That is the whole of it. Knowing exactly what that does and does not buy you matters, because flattening gets confused with two things it is not.

A fillable PDF has two layers that a reader never sees as separate. The page is one of them: text, rules, whatever was printed. The fields are the other, a set of interactive widgets positioned on top, each holding a value and a description of how that value should be drawn. When you type into a form you are not changing the page. You are changing a value held by a widget that sits over it.

That separation is useful while you work and awkward once you are finished. The widget only describes how to draw its value, so a viewer without the right font substitutes one, and an answer that sat neatly inside its box on your screen can arrive somewhere else. Some receiving systems read only the page and ignore field values entirely, which is how a completed form arrives looking blank. And anyone who opens the file can click into a field and retype it, deliberately or by leaning on a key.

Flatten PDF reads the document, asks it for its form, and bakes each field's current appearance into the page content. Afterwards the values are ordinary page material: they are in the file, they print, they sit exactly where they did, and no viewer has to decide how to draw them. The fields themselves are gone, so there is nothing left to click into.

• You are sending a completed form. The answers are the point of the document, and they should arrive as the document rather than as editable suggestions.
• The receiving system reads only the page. Some portals and some printers ignore field values. Flattening puts the answers where those systems are already looking.
• The file will pass through several hands. A reviewer who can retype a figure eventually will, and afterwards nobody can tell which copy was the original.
• Appearance has to survive an unfamiliar viewer. A baked value cannot be redrawn in the wrong font, because there is nothing left to redraw.

If there is any chance an answer still has to change, do not flatten the only copy you have. The output has no fields, so the values are no longer editable as values, and getting them back means covering them over or rebuilding the form from scratch. The tool leaves your original file untouched, and the habit that makes this safe is to keep the filled but unflattened version and treat the flattened one as the copy you send.

The same applies to a document still going round for input. A form being passed between two people who each add answers should stay a form until the last of them is done. Flatten at the end of that process, not in the middle of it.

It is not protection. No password is involved, nothing is encrypted, and a flattened PDF opens for anyone it reaches. If the document should be readable only by its recipient, that is Protect PDF and a password, and it is a separate step. There is a related trap worth knowing: if the file you flatten was password protected, the copy that comes out is not. The report says so plainly, and the fix is to protect the flattened copy again before it goes anywhere.

It is also not redaction. Flattening bakes what the fields are showing and has no opinion about what lies beneath them. A white box drawn over a paragraph still has that paragraph under it after flattening, and so does a black one. If content genuinely has to be gone, read how to redact sensitive information first, because covering and removing are different operations with very different outcomes.

1. 1

   Fill and sign first

   Every value has to be showing what you want before you flatten, because afterwards you cannot change it. Check the pages themselves, not only the fields you remember filling in.

2. 2

   Flatten next

   Bake the values, download the new copy, and confirm the field count in the export report matches the number of answers you expected to be baked.

3. 3

   Protect last

   If the document needs a password, apply it to the flattened copy. Doing it the other way round means the flattening step hands you an unprotected file.

• Comments, links and other annotations. Form fields and general annotations are different structures inside a PDF. This tool flattens the fields, and it does not claim to bake every other kind of annotation.
• Forms built only on XFA. A document of that kind may expose no ordinary form fields at all, in which case there is nothing here for the tool to find.
• A document with no fields. You get a structurally rewritten copy with no visual change, and a warning telling you no fields were present. That is an answer rather than a failure.

Open the download. Not the version still sitting in the editor, the file that was actually produced. Look at it in a second viewer if you have one, because the entire reason to flatten is that other people's viewers do not behave like yours. Confirm the values are where they should be, confirm the count, and keep the editable version somewhere you will find it again.