Flatten PDF

Flattening a PDF is the process of converting interactive elements into static page content. In technical terms, it takes the appearance streams of form fields and annotations — the rendering instructions that define how each widget looks on screen — and bakes them directly into the page's content stream. The result is visually identical to the original but no longer contains any interactive objects that a PDF viewer could edit or modify.

A PDF form field (defined by the /AcroForm dictionary in the document catalog) consists of two linked components: a field dictionary that stores the field's value, type, and validation rules, and a widget annotation that controls how the field renders on a specific page. When pdf-lib's form.flatten() method executes, it reads each widget's appearance stream — which is a self-contained set of PDF drawing operators defining the field's visual state — and writes those operators into the page's main content stream. It then removes the widget annotation and its associated field dictionary, effectively transforming an editable control into a permanent graphic.

The distinction between "Flatten Forms" and "Flatten All" matters for document workflows. Flatten Forms targets only /Widget annotations linked to AcroForm fields — text inputs, checkboxes, radio buttons, dropdowns, and signature fields. Other annotation types like /Link (hyperlinks), /Highlight (text highlights), /Text (sticky notes), and /Stamp (stamps) remain intact. Flatten All goes further: after flattening forms, it iterates through every page's /Annots array and deletes all remaining annotation objects, producing a completely clean document with no interactive layers whatsoever.

Flattening differs fundamentally from rasterization (converting to images). A flattened PDF retains all its vector text, embedded fonts, and searchable content — only the interactive form layer is removed. Rasterization, by contrast, converts everything to pixels, destroying text selectability and dramatically increasing file size. This distinction is critical for archival workflows where documents must remain searchable and text-extractable while being locked against editing.

Digital signatures in PDF documents are cryptographic objects stored as /Sig-type form fields. They contain a hash of the document's byte range at the time of signing. Any modification to the document — including flattening, which alters content streams and annotation arrays — changes the byte sequence and invalidates the hash. This is why the tool warns when signatures are detected: the flattened output will be structurally different from the signed original, and signature validation will fail. For signed documents, best practice is to keep the original signed version alongside the flattened copy.

Flattening PDF forms and annotations serves several important purposes across legal, administrative, and archival workflows:

• Prevent unauthorized editing — Flattened form fields cannot be modified. This is essential when distributing completed contracts, applications, or compliance forms where the recorded values must remain fixed. Unlike PDF passwords (which can be removed by third-party tools), flattening permanently embeds values into the page content — there is no "unflatten" operation.
• Archival and records management — Regulatory frameworks like PDF/A (ISO 19005) for long-term archival recommend or require that interactive elements be flattened before storage. Flattened documents are self-contained: they do not depend on external font servers, JavaScript execution, or form calculation scripts to render correctly decades later.
• Print consistency — Interactive form fields sometimes render inconsistently across different PDF viewers and printers. A checkbox that appears checked in Adobe Acrobat may display differently in Preview, Chrome, or a commercial print RIP. Flattening eliminates these rendering variations by converting every field to standard PDF drawing operators that all renderers handle identically.
• File size reduction — Form fields carry overhead: field dictionaries, appearance streams for multiple states (normal, focused, read-only), JavaScript actions, calculation order arrays, and the AcroForm dictionary itself. Flattening strips this metadata. Documents with hundreds of form fields — such as multi-page government forms or insurance applications — can see measurable size reductions after flattening.
• Clean document distribution — Before sharing a PDF externally, flattening removes interactive clutter: empty form fields that display as bordered rectangles, comment threads visible to recipients, and highlight marks from internal review. The result is a professional, polished document suitable for clients, regulators, or publication.
• Cross-platform compatibility — Some lightweight PDF viewers on mobile devices or embedded systems do not fully support AcroForm fields. Flattened documents display correctly everywhere because they use only basic PDF content stream operators — no form rendering engine required.

Processing PDFs locally in your browser is particularly important for flattening workflows. The documents most commonly needing flattening — completed tax forms, signed contracts, medical intake paperwork, HR onboarding documents — contain sensitive personal information. This tool guarantees that your document data stays on your device throughout the entire process, with no network requests, no server-side storage, and no third-party access to your content.