Flattening is the answer to several unrelated complaints, and it is a one-way door. Keep the original.
What flattening actually merges
| Layer | Before | After |
|---|---|---|
| Form fields | Editable values | Printed text |
| Annotations | Deletable objects | Page content |
| Stamps | Draggable | Fixed |
| Signature images | Removable | Part of the page |
| Layers (OCGs) | Toggleable | One flat rendering |
| Transparency | Live blending | Pre-composited |
Note what is not on that list: the text of the page itself. Flattening does not rasterise a document — text stays text and stays selectable. That is the difference between flattening and rendering to images, which people conflate.
The problems it solves
- A completed form that must not be edited. Field values become printed text, so the answers are fixed.
- Annotations that do not print. Several readers omit them by default; flattened, they are page content and always print.
- A signature someone could drag off. After flattening it is part of the page.
- Inconsistent rendering. Readers implement annotations differently; flattened content looks the same everywhere.
- Transparency artifacts on print. Pre-compositing avoids the black-box rendering fault described in how to fix a broken PDF.
The common thread is finality. Flattening says the document is done, and everything on it is now part of it.
When not to
Three cases where flattening destroys something you needed.
- A document still in review. The next reviewer needs to reply to and resolve existing comments. Flattened, they are just marks on a page.
- A form you will reuse. Flattening a blank template destroys the fields permanently.
- Anything you might need to correct. Field values become uneditable text, so a typo means starting again.
And the ordering hazard: flattening after signing invalidates the signature, because it changes the file. Fill, flatten, then sign — never the reverse.
Flattening is not compression
These get confused constantly and the confusion is understandable, because flattening does usually make the file slightly smaller.
It removes interactive structures — the field dictionaries, the annotation objects, the layer definitions — and those have a size. But that is a side effect measured in a few percent, not the point.
If a 2 MB form becomes 1.9 MB after flattening, that is the expected result. If you need it meaningfully smaller, the size is in the images and the fix is compression — see why is my PDF so big. Occasionally flattening makes a file larger, when complex transparency has to be pre-composited into new image data.
Flattening versus rasterising
The strongest version of "make this uneditable" is not flattening at all.
Flattening merges the interactive layers and leaves the page as page content — text still text, still selectable, still searchable.
Rasterising renders every page to an image and rebuilds. Nothing is selectable, nothing is searchable, and nothing whatsoever can be edited.
Rasterising is the right tool when the requirement is that no text can be extracted — for genuine redaction, as in how to redact a PDF properly. It is the wrong tool for a finished form, where you want the values fixed but still searchable and accessible. Reaching for it by default throws away the text layer for nothing.
A working order
Most document workflows fit one sequence, and getting it right avoids redoing work.
- Assemble — merge the parts.
- Compress — one lossy pass over the whole thing.
- Fill — complete any form fields.
- Watermark — if it needs one.
- Flatten — fix everything in place.
- Sign — last, because everything before this changes the file.
- Encrypt — after signing, since an encrypted file cannot be processed further.
Keep the unflattened, unsigned version at step four. It is the last point at which the document is still fully editable, and it is the only copy you can correct without starting over.
Frequently asked questions
What does flattening a PDF do?
It merges the interactive layers — form fields, annotations, stamps, signature images, layers — into the page content. They stop being separate objects, so nobody can move or delete them, and readers that skip annotations when printing now print them.
Can flattening be undone?
No. Once merged into the page there is no annotation to restore. Always keep an unflattened copy before doing it — that copy is the only version you can still correct.
Does flattening make a PDF smaller?
Slightly, by removing the interactive structures — usually a few percent. It is a side effect rather than the purpose. If you need real size reduction, compress the images. Occasionally flattening makes a file larger, when complex transparency is pre-composited.
Does flattening turn my text into an image?
No, and this is the common misconception. Text stays text and stays selectable and searchable. Rendering to images does rasterise everything — that is a different operation with a different purpose.
Should I flatten before or after signing?
Before. Flattening changes the file, so doing it after signing invalidates the signature. Fill, flatten, then sign, then encrypt — everything that modifies the file has to happen before the signature.
When should I not flatten?
While a document is still in review, since the next reviewer needs to reply to and resolve comments. On a blank form template, since it destroys the fields. And on anything you might need to correct, since field values become uneditable text.