A filled-in PDF form is not what it appears to be. The values you typed are not part of the page — they live in interactive form fields sitting on top of it, and anyone who opens the file can clear them, type over them, or export them. The same is true of comments, stamps and highlights.
Flattening turns that interactive layer into ordinary page content. The value of a field becomes drawn text; a stamp becomes part of the page. Nothing can be typed over, cleared, or dragged away afterwards.
When you need it
Sending a completed form to someone who must not alter it. Archiving a signed document so it reads the same in ten years regardless of which reader opens it. Submitting a form to a system that ignores form fields and would receive a blank page. And solving the surprisingly common problem of a form that displays correctly in one reader and blank in another, because form field rendering is inconsistent across viewers in a way page content never is.
That last one is worth dwelling on: a form that looks perfect in Acrobat and empty in a browser preview is not broken. It is a form, and the browser is not drawing the fields. Flattening removes the ambiguity entirely.
What it does not do
Flattening is about permanence, not secrecy. The text is still text on the page: it can be selected, copied, and read by any tool that reads PDFs. Nothing is hidden and nothing is encrypted.
This distinction causes real harm when it is misunderstood. Flattening a document with a value that should not be visible does not remove that value — it fixes it in place. If content needs to be genuinely gone rather than locked, that is redaction, which destroys the underlying content rather than making it uneditable.
Nor is flattening a signature. It prevents casual alteration; it does not prove who signed or detect later tampering. That is what a cryptographic signature is for.
The annotations that cannot be flattened
An annotation usually carries a stored appearance — a small piece of drawing instructions saved by the reader that marked the document up, describing exactly how it looks. Flattening means taking that appearance and drawing it into the page, which reproduces it faithfully.
Some annotations have no stored appearance, leaving the rendering entirely to whichever reader opens the file. Those cannot be baked in faithfully: synthesising an appearance means guessing what the original reader drew, and guessing wrong silently alters the document.
Filum leaves those in the file, still editable, and shows the count on screen rather than pretending the job was complete. Links are also kept deliberately — a link has no visible body of its own, so flattening one would only break the link.
And when there is nothing to flatten, the tool says so and produces no file. A document that looks processed but is not is worse than a clear refusal, because you would send it on believing it was locked. All of this runs in your browser: the forms people flatten are the filled-in ones, carrying names, dates, account numbers and signatures.