By PDFKits Team — Published February 19, 2026
TL;DR. Flattening a PDF form converts interactive form fields, annotations, and digital signature appearances into static page content. After flattening, no one can change the field values, the form is no longer interactive, and the file is dramatically smaller. Flatten before sending a filled form to a counterparty who shouldn't edit it, before archiving a signed document, before printing for offline submission, or before publishing a "blank" form as a fillable PDF. Common pitfall: flattening destroys hidden form data — which is usually what you want, but be sure you have a copy of the data elsewhere if you'll need to query it later. PDFKits handles the flattening in your browser, so the filled form never goes to a third party.
A PDF form is two layers stacked: the static page content (background, labels, lines) and an interactive layer of form fields, annotations, and (optionally) signatures. The interactive layer carries the field values, the field types (text, checkbox, dropdown, signature), and any associated JavaScript or validation. Flattening collapses both layers into a single static layer: each field's current rendered appearance becomes a piece of the page content stream, the underlying field definition is removed, and the file becomes a non-interactive PDF.
The visible result usually looks identical — if a text field showed "Marcus Wilson," after flattening the page shows "Marcus Wilson" as static text. The functional differences are: no one can re-edit the values, the file size typically drops 10–40% because the AcroForm structure is gone, and a screen reader announces the content the same way it would a regular paragraph rather than navigating field-by-field. For document archive and signed-record use cases, this is exactly what you want.
A grant application requires filling a PDF form and attaching it as part of the submission. The granting body wants the values fixed, not editable — they should see exactly what the applicant submitted. Flattening before sending prevents accidental field changes, prevents reviewers from inadvertently overwriting answers, and signals that the document is final.
An e-signature workflow places a signature image and a date in the document. Without flattening, those are annotation objects — anyone with the file can drag them, replace them, or delete them. Flattening bakes the signature appearance into the page, removing the possibility of repositioning. For most signed-image workflows (ESIGN-compliant in the U.S., compatible with non-PKI signing), this is the right post-signing step.
An organization archives signed contracts, executed agreements, and finalized reports as PDFs. The archive format should be predictable: any PDF reader, any operating system, any era should be able to open the file consistently. Interactive forms can render inconsistently across readers — different fonts in fields, missing rendering of certain widget types — so flattening to static content guarantees consistency.
Some printers and print drivers render form fields inconsistently — text overflow, font substitution, or fields that print empty despite containing data. Flattening before printing produces a print-stable file. For high-volume printing (mailing 500 personalized letters), this prevents random one-off rendering bugs.
The form is still being filled in. The form needs to be reusable as a template. The downstream system extracts field data programmatically (the flattening destroys that capability). Track-changes review is in progress and comments need to remain interactive. Compliance requires preserving the interactive form structure (PDF/A-2u allows tagged forms; PDF/A-1 generally does not).
Sarah generates offer letters from a Word template with merge fields, exports each to PDF, and sends them to candidates. Without flattening, the candidate could open the PDF, edit the salary field, and reply with a modified version. Flattening before sending makes the offer text static and tamper-resistant. (Tamper-resistant, not tamper-proof — a determined editor can always rebuild the document, but they can't quietly change a number.)
Diego sends PDF invoices to clients. Some clients use accounting platforms that try to "open" PDFs for review and inadvertently introduce edit marks. Flattening the invoice before sending prevents the accounting tool from treating it as editable.
Aisha distributes annual benefits enrollment to 200 employees. The blank form is fillable; once an employee fills and returns it, Aisha flattens each returned form before filing it in the employee record. The flattened version is the official record; the original interactive form is archived separately for audit.
Carlos manages residential closings. The closing package includes 20+ signed documents — the deed, the title insurance binder, the disclosures. After all signatures are collected, each document is flattened so the e-signature appearances cannot be repositioned and the field values cannot be altered. The flattened binder goes to the buyer, the seller, and the title company.
A non-profit publishes a tax-exempt purchase order form. Before publishing the template, they flatten the example values (the demonstrating cells showing "ABC Charity" and a sample order number) into static content so users don't accidentally submit the example values. The user-facing version has fillable fields only where intended.
Priya is preparing a settlement agreement for court filing. The agreement was negotiated and signed via DocuSign; the resulting PDF has signature objects. Flattening before filing produces a clean, court-ready exhibit with the signatures baked in.
Drag the PDF into Flatten PDF (or use Edit PDF with the flatten option). Select what to flatten: form fields only, annotations only, or all interactive layers. For most cases, "all" is correct — flatten fields, annotations, and signature appearances together. Click Flatten. The browser processes the file: each form field's current rendered appearance becomes a piece of the page content stream, the underlying AcroForm structure is removed, and the file is rewritten. Download the result. Verify the file is non-interactive by opening it in a PDF reader — clicking on what was a form field should produce no editable cursor.
For partial flattening — flatten only certain fields while leaving others editable — use Acrobat Pro's field-level flatten function. PDFKits flattens at the document level only. For most workflows, document-level flattening is what's needed.
| Feature | PDFKits | Adobe Acrobat Pro | pdftk (CLI) | iLovePDF |
|---|---|---|---|---|
| Cost | Free | $29.99/month | Free (open source) | $48/year Premium |
| Files stay on your device | Yes | Yes (desktop) | Yes | No — cloud |
| Flatten entire document | Yes | Yes | Yes | Yes |
| Flatten specific fields only | No | Yes | Partial | No |
| Preserve signature appearance | Yes | Yes | Yes | Yes |
| Batch flatten (100+ files) | Manual | Action Wizard | Scriptable | Cloud queue |
| No login required | Yes | Adobe ID | — | Account-gated |
For one-off flattening (a signed contract, a completed form ready to send), PDFKits is the lowest-friction option. For batch flattening of hundreds of files, a pdftk one-liner in a shell script is faster. For granular per-field control, Acrobat Pro is the only practical option.
Will: lock form field values, freeze e-signature appearance positions, remove form-level JavaScript, drop hidden form data, reduce file size by removing AcroForm structure, prevent casual edits.
Won't: prevent a determined user from rebuilding the document or modifying it with Adobe Acrobat Pro, remove pre-existing content stream items, change the visible appearance of properly-rendered fields, validate that the field values are correct, add tamper detection (for tamper-evident output, combine with a content-stream hash or digital signature).
If you need cryptographic tamper-evidence — proof that the file hasn't been modified since signing — flattening is necessary but not sufficient. Pair flattening with a PKI-backed digital signature, which produces a tamper-evident signed PDF.
Flattening before you have a copy of the form data. If a downstream system needs to extract field values from the form, flatten a copy — keep the original interactive form for data extraction. The flattened version is the human-readable record; the original is the machine-readable record.
Flattening but expecting the file to remain accessible to screen readers as a form. Flattened forms read as paragraphs, not as labeled fields. If accessibility requires field-level navigation, do not flatten; instead, ensure the form fields have proper labels and tab order.
Flattening to "secure" a document. Flattening makes casual edits hard but doesn't prevent serious modification. For real document security, encrypt the file or use a digital signature with certificate-based verification.
Flattening a partially-completed form. Once flattened, the form is uneditable. If you're not done filling, save a working copy first, complete it, and flatten only the final version.
Flattening forms in regulatory submissions. Some regulators (FDA eCTD, SEC EDGAR for certain filings) require submitted PDFs to retain specific structure including interactive forms. Read the submission spec before flattening — a flattened submission may be rejected.
These three operations are often confused but solve different problems.
Flattening = lock the visible content. Field values are frozen as static text. Anyone can still copy text or modify with a determined effort.
Encryption = restrict who can open the file. A password is required to view content. Once opened, edits may or may not be restricted depending on permission settings.
Digital signatures = prove the file hasn't been modified since signing. A cryptographic hash binds the signer to the file state at signing time. Any later modification invalidates the signature.
For a signed final contract, the right combination is often all three: flatten to bake values, sign cryptographically to prove integrity, encrypt to restrict who can open if confidentiality matters.
Not really. Flattening converts field structure into page content; there's no reverse operation that recovers field types and validation. The closest is to manually rebuild a form on top of the flattened static content, which is significantly more work than starting from the original.
Image-based signatures (drawn or uploaded signature graphics) flatten cleanly — the signature appearance becomes static. Cryptographic signatures (certificate-based PKI signing) become invalid if you flatten after signing, because flattening alters the signed content. For PKI-signed documents, do not flatten after signing.
Usually yes, by 10–40%. Form structure, JavaScript, validation rules, and unused field definitions are removed. Documents with many fields see larger reductions than text-heavy documents.
PDFKits flattens the entire document. For per-field flattening, Adobe Acrobat Pro is the right tool — its field-level Lock function effectively flattens specific fields while leaving others editable.
Sometimes. If the corruption is in the AcroForm structure but the visible page content is intact, flattening can salvage the visible content. If the corruption is in the page content itself, flattening won't help — use Repair PDF first.
Less accessible than well-tagged interactive forms. Screen readers read flattened fields as paragraph text. For maximum accessibility with form interactivity, keep the form interactive and ensure proper labels; for read-only accessibility, flatten and verify the tag structure separately.
The visible signature image is flattened into the page; the cryptographic certificate object is removed during flattening. This invalidates the certificate-backed signature. For PKI-signed documents, the document should remain unflattened.
Only if you have the password to open it. The encryption is preserved across flattening — the flattened result will have the same password protection as the original. To remove the password, use Unlock PDF first.
Document-info fields (Author, Title, etc.) are preserved through flattening. The change is in the page content streams and the form structure, not the metadata. To strip metadata separately, run Clean Metadata after flattening.
For most documents, under five seconds even for 100-page forms. Flattening is a structural operation — no image processing, no OCR, no compression — so it's fast.
Edit PDF — Includes a flatten option among other edits. Sign PDF — Add an image signature, then flatten to lock it. Protect PDF — Encrypt the flattened result for restricted distribution. Fill PDF Forms — Fill out forms before flattening. Clean Metadata — Strip metadata before publishing flattened versions. Repair PDF — Recover corrupted forms before deciding whether to flatten.