You filled in a form, signed it, sent it back — and the recipient says the fields are blank, or your signature is missing, or the boxes are still editable. Flattening is the fix, and the reason it works explains a lot about how PDFs are put together.
Two layers, not one
A PDF you have filled in or annotated is really two things stacked together.
The page content is the fixed layer: the printed text, lines, boxes, and images that came with the document. It is the same for everyone.
The interactive layer sits on top: form field values, signature annotations, highlights, comments, stamps, and sticky notes. These are separate objects with their own coordinates, referencing the page rather than being part of it.
That separation is useful while you work — fields stay editable, annotations can be moved or deleted. It becomes a liability once you send the document, because every viewer decides for itself how to render that layer, and they do not all decide the same way.
Flattening merges the interactive layer into the page content. Afterwards there is one layer. What you see is what the file contains, and every viewer renders it identically because there is nothing left to interpret.
Why unflattened documents cause trouble
Fields appear empty to the recipient. Some readers, portals, and preview panes render the page and ignore field values. Your carefully completed form arrives blank. This is the single most common reason people discover flattening exists.
Annotations render inconsistently. A highlight or stamp that looks right in your editor may sit in the wrong place, appear in the wrong colour, or not appear at all elsewhere.
Values are still editable. Anyone receiving the file can change what you entered — including after you signed it. For a signed agreement that is a meaningful problem.
Printing behaves unpredictably. Some print pipelines drop annotations, so a document prints without the signature it displays on screen.
Upload portals reject or mangle it. Government and institutional systems frequently expect flat files, and their validators are not forgiving.
When to flatten
- Before returning a completed form, so the recipient sees the values you entered.
- Before sending anything signed, so the signature cannot be lifted or altered.
- Before printing, if the document contains annotations that matter.
- Before uploading to a portal, essentially always.
- Before archiving, so the record is fixed rather than a template someone can re-fill.
When not to flatten
- On a form you are distributing for others to fill in. Flattening destroys the fields, turning your fillable form into a picture of one. This is a genuinely annoying mistake to make on a template you spent an afternoon building.
- When collaborative review is still running. Flattened comments cannot be replied to or resolved.
- On a document carrying a certificate-based digital signature. Flattening alters the file and invalidates the signature.
- When accessibility matters and your method rasterises. Some flattening approaches destroy the tag structure that screen readers depend on. See PDF accessibility guide.
How to do it
Export from an editor. When you export a completed document from Docento.app, your text, stamps, and signatures are drawn directly into the page content rather than attached as annotations — so the exported file is already flat. Nothing extra to do. See how to fill out a PDF form.
Print to PDF. The universal method: open the file, press Ctrl+P (Cmd+P), choose "Save as PDF" or "Microsoft Print to PDF", and save. Works everywhere with no software. The cost is real, though — it discards bookmarks, internal links, hyperlinks, and accessibility tags, and can increase file size. Fine for a signed form, poor for a structured report.
macOS Preview. File → Export as PDF flattens annotations in most cases, with better fidelity than printing.
Acrobat Pro. Offers proper control: "Flatten Fields and Comments" under Print Production, or a Preflight profile. This is the only route that reliably flattens while preserving links and tags.
Command line. qpdf --flatten-annotations=all in.pdf out.pdf merges annotations while keeping the document structure intact — much better than print-to-PDF for anything where structure matters. Ghostscript can also do it, at the cost of re-encoding.
Check it worked
Open the exported file and try to click into a form field or select an annotation. If nothing responds, it is flat. Also confirm your entries are actually visible — a flatten that dropped the values rather than baking them in is a specific and unpleasant failure, and the reason to check in a different application than the one that produced the file.
Keep the original
Flattening is irreversible. There is no unflatten, and no tool that recovers the fields. Save the interactive version before you flatten anything you may need to amend, resend, or reuse as a template. The habit worth building is to export the flat copy under a new name — application-signed-flat.pdf — rather than overwriting what you started with.
