Flatten PDF — what "baking in" actually means and when to do it
Flattening a PDF is one of those operations that sounds technical but solves a very practical problem: stopping recipients from accidentally (or intentionally) editing your form values, annotations, or signatures. Done at the right time, it turns a working document into a final deliverable that behaves like a printed page. Done at the wrong time, it permanently destroys the editability you might still need. Here is what flattening does under the hood, when it is exactly the right move, and the three cases where doing it now is a mistake.
What gets baked in (and what doesn't)
When you flatten a PDF, the tool walks every page and converts live interactive elements into static page content. The PDF's AcroForm dictionary is processed: each form field's current value is rendered as text inside the page's content stream, then the field's interactive entry is removed. Annotations (highlights, sticky notes, text boxes, ink markup) are similarly merged into the page contents and their interactive references dropped. Visual signatures become embedded images at the position they were placed.
The output behaves like a printed page. Form fields are no longer fillable — they look exactly like they did when you flattened, and they cannot be re-edited. Highlight overlays are permanent. Comments either become visible text or are dropped. The PDF file itself is structurally simpler — fewer dictionaries, no interactive layer.
When flattening is the right move
Five canonical use cases:
- Final delivery of a filled form. You filled out a vendor onboarding form, a registration form, a contract. Flatten before sending so the recipient cannot modify your answers.
- Locking in markup from a review pass. You added comments, highlights, and tracked changes to a draft. Flatten when you want those comments to persist visually but be unchangeable.
- Printing a form that needs to be archived. Flattening makes the document behave like a printed page — useful for paper-trail compliance where the digital file should match what would appear on paper.
- Closing out a signed document. After everyone has signed a document with visual signatures, flatten to prevent further field changes. Pair with cryptographic signing if you need legal-grade non-repudiation.
- Preparing a PDF for systems that don't handle forms. Older archival systems sometimes choke on PDFs with AcroForm dictionaries. Flatten first to produce a structurally simpler file.
Three cases where flattening now is wrong
Flattening is permanent. Once a form field is baked into the page, there is no "unflatten" operation. Three situations where waiting is the right move:
- The form values are still in draft. If anyone — including you, on a different day — might still want to change the values, do not flatten yet. Keep the working AcroForm copy and only flatten the final-final version.
- You need cryptographic signatures to remain valid. Cryptographic signatures are bound to the exact byte layout of the file at signing time. Flattening rewrites the byte layout, which invalidates the signature chain. If you need a cryptographically-signed deliverable, sign AFTER flattening, not before.
- Form data extraction is still in the workflow. If a downstream system reads form-field values directly from the PDF (a common pattern in invoice processing, expense reports, and intake forms), keep the form fields live. Flattened PDFs require OCR + regex extraction, which is far more expensive than reading AcroForm dictionaries directly.
Cryptographic signatures and flattening — the precise rule
This trips up enough users that it deserves its own section. A PDF can carry two kinds of "signature":
- Visual signature (an image of a handwriting). A drawn or photographed signature placed on the page like any other image. Has no cryptographic verification. Survives flattening unchanged — it was already visual content; flattening just converts it from an annotation reference to part of the page contents.
- Cryptographic signature (a digital signature with a certificate). A signed hash of the file's bytes, anchored to a verifiable identity. Flattening rewrites the file bytes, so the hash no longer matches. The signature appears as a visual stamp in viewers, but the verification badge says "signature invalid — file modified."
What you keep, what you lose
After flattening, the file is smaller, simpler, and less interactive. Concretely:
- Kept: visual appearance. The PDF looks exactly the same as before flattening. Every form value, every annotation, every signature is visible at the same position with the same styling.
- Kept: searchability. Form values written as text are still selectable, searchable, and screen-reader-accessible after flattening.
- Lost: AcroForm dictionary. Cannot be re-edited via PDF readers.
- Lost: interactive annotations. Highlights, comments, sticky notes are no longer hover-able or removable.
- Lost: cryptographic signature validity (if any). Sign after flattening to preserve validity.
Limits and compatibility
On the free web tool, flatten handles PDFs up to 100 MB with no page-count cap. Processing runs in your browser via pdf-lib; nothing is uploaded. Output is byte-compatible with every PDF viewer since Acrobat 5.
Common pairings: Sign-then-flatten for documents that need both signature and lockdown. Page-numbers-then-flatten when you want the page numbers permanently rendered. Compress-after-flatten produces the smallest final-state file by combining structural simplification (flatten) with bitmap re-encoding (compress).