How to flatten a signed contract pdf for long-term archiving
- Step 1Download the fully signed contract — Get the executed PDF from your e-signature platform (DocuSign, Adobe Sign, etc.) with all signatures applied.
- Step 2Verify the digital signature FIRST — Run the Signature Verifier to confirm the signature is intact and covers the document, and save the report. Flattening will invalidate the cryptographic signature, so capture the proof of validity now.
- Step 3Keep the original signed file — Archive the untouched, cryptographically signed PDF alongside the flat copy. The flat copy is the readable render; the original is the legal evidence.
- Step 4Drop the signed contract onto the flatten tool — Open the PDF Flatten tool and drop the file. Flattening starts automatically — there are no options to set.
- Step 5Let it flatten the form layer — The tool draws each field and signature appearance onto the page and removes the interactive widgets.
- Step 6Convert to PDF/A for the archive — For ISO 19005 archival compliance, run the flattened output through the PDF/A converter. Download and store both the flat/PDFA render and the original signed file.
Signed-PDF flattening: what to do in what order
The safe sequence for archiving a digitally signed contract. Flatten is NOT the first step.
| Step | Tool | Why |
|---|---|---|
| 1. Verify | Signature Verifier | Confirm intact + coverage and save the report while the signature is still valid |
| 2. Preserve | (file system) | Keep the original signed PDF as the legal evidence; never flatten the only copy |
| 3. Flatten | PDF Flatten | Produce a static, universally readable render of the executed contract |
| 4. Archive | PDF/A converter | Lock the render to ISO 19005 for long-term preservation |
Signature types and flatten behaviour
Flatten treats a drawn image very differently from a cryptographic signature.
| Signature type | After flattening | Validity impact |
|---|---|---|
| Image / drawn appearance | Baked into the page as a picture | Visual only — nothing to invalidate |
| Cryptographic digital signature | Appearance baked; signature object disturbed | Cryptographic validity is broken — verify and record first |
| Empty signature field (unsigned) | Removed (blank space) | No signature was present to lose |
Cookbook
Archival workflows for executed contracts, in the correct order.
Verify, then flatten an executed DocuSign contract
The signature is genuine and you want a clean archival render. Verify and save proof first, then flatten the leftover form layer.
1) Signature Verifier → intact: true, coversWholeDoc: true (save the JSON report — this is your validity proof) 2) PDF Flatten → contract.flatten.pdf (static render) 3) Keep BOTH the original signed PDF and the flat copy
Flattening breaks the cryptographic signature
This is the key warning. After flattening, a verifier will no longer report the signature as cryptographically valid, because the file changed. That is why you verify and preserve the original first.
Original signed.pdf → Verifier: intact: true
flatten →
signed.flatten.pdf → Verifier: signature no longer valid
(file bytes changed after signing)Empty signature shells removed
A platform left unsigned signature-field shells in the document. Flatten removes them, so a future viewer does not show stray empty boxes.
Before: 2 signed + 1 leftover empty signature widget After: signatures baked; empty widget gone Clean archival render, no orphan boxes.
Flatten then PDF/A for the records system
Your DMS requires ISO 19005 archive files. Flatten produces the static render, the PDF/A converter makes it archive-grade.
contract.pdf → PDF Flatten → contract.flatten.pdf → PDF/A → contract.flatten.pdfa.pdf (archival) Store alongside the original cryptographically signed PDF.
Old viewer showed empty boxes; flatten fixes the render
A ten-year-old viewer rendered the interactive widgets as blank rectangles. Flattening converts those appearances to page content that any viewer draws.
Legacy viewer on original: empty boxes where fields were Legacy viewer on flat copy: values drawn correctly (Flatten removes the dependency on widget rendering.)
Edge cases and what actually happens
Flattening invalidates the cryptographic digital signature
invalidates signatureA digital signature covers a specific byte range of the file. Flattening rewrites the file, so the signature no longer verifies — a verifier will report it as broken or absent. This is unavoidable. Verify the signature with the Signature Verifier and save the report BEFORE flattening, and keep the original signed file as the legal evidence.
Never flatten your only copy of a signed contract
By designBecause flattening is irreversible and breaks the signature, the flat copy is a render, not the evidence. Always retain the untouched signed PDF. Archive both: the original for legal validity, the flat (and optionally PDF/A) copy for guaranteed readability.
Is a flattened contract legally binding?
out of scopeFlattening preserves the visible signature but removes the cryptographic proof. Whether the flattened render alone is enforceable depends on your jurisdiction and the signing method — which is exactly why you keep the original signed file. Consult your legal advisor; this tool makes no legal determination.
Signed PDF is also encrypted
decrypts on saveThe tool loads encrypted PDFs by ignoring encryption and writes the output unencrypted. Combined with the signature being broken, the flat copy is purely a readable render. Keep the protected, signed original; re-apply protection to the render with Password Protect if your archive requires it.
Signature appearance uses a non-WinAnsi font
may fail silentlyIf a signature or field appearance needs regenerating and contains non-WinAnsi characters, pdf-lib's default Helvetica can throw; the tool catches it and re-saves, possibly leaving that widget un-flattened. Check the rendered output. For signatures rendered as images (the common case), this does not apply.
Multiple signatures from different signers
SupportedFlatten bakes every signature appearance onto the page regardless of how many signers there were. Each visual signature is preserved; all cryptographic signatures are equally invalidated. Verify all of them first with the Signature Verifier, which reports each signature independently.
Contract over 2 MB or 50 pages on Free
blocked on freeLong contracts with embedded exhibits can exceed the free 2 MB / 50-page cap and get blocked with an upgrade prompt. Pro extends to 50 MB / 500 pages, and Pro+Media to 500 MB / 2,000 pages for large agreement packages.
Document metadata persists after flattening
PreservedFlatten does not touch the PDF's metadata — author, creation date, and the e-signature platform's producer string remain. For a sanitised archival copy, run the Metadata Scrubber after flattening (on the render, never the signed original).
Frequently asked questions
Will the digital signature still be valid after flattening?
No. A cryptographic digital signature covers a specific byte range, and flattening rewrites the file, so the signature no longer verifies. This is why the workflow is: verify with the Signature Verifier and save the report first, keep the original signed file as the legal evidence, and treat the flattened copy as a readable archival render only.
Then why flatten a signed contract at all?
For long-term readability. E-signature platforms leave interactive widgets in the file that some viewers render as empty boxes, and the interactive layer can depend on specific software. Flattening produces a static page that any viewer — now or in ten years — draws identically. You keep the cryptographically signed original for validity and use the flat copy for reliable display and archiving.
Should I verify the signature before flattening?
Always. Once flattened, the cryptographic signature is broken and you cannot re-verify it on that file. Run the Signature Verifier on the original, confirm it is intact and covers the whole document, and save the JSON report as your proof of validity. Only then flatten.
Is the flattened contract legally binding?
Flattening preserves the visible signature but removes the cryptographic proof, so the flat copy alone may not carry the same legal weight as the signed original. That depends entirely on your jurisdiction and signing method. Keep the original signed file for legal purposes and consult your legal advisor — this tool makes no legal determination.
Should I convert to PDF/A after flattening?
For archival purposes, yes. Running the flattened output through the PDF/A converter produces an ISO 19005-compliant file designed for long-term preservation. The sequence is verify → preserve original → flatten → PDF/A, storing both the archival render and the signed original.
Will hand-drawn or image signatures survive flattening?
Yes. A signature that is an image or a drawn appearance is baked onto the page as a picture — there is no cryptographic object to invalidate, so it simply becomes fixed page content and renders everywhere. The validity concern applies only to real cryptographic digital signatures.
Is the contract uploaded anywhere?
No. Flattening runs in your browser via pdf-lib; the executed contract never leaves your device. Only an anonymous usage counter is recorded when signed in, with no file content. That keeps confidential agreements local throughout the process.
Are there any options to configure?
No. Flatten is a zero-option tool — drop the file and it flattens the entire form layer automatically. There is nothing to set, so the only decision you make is the order of operations (verify and preserve before flattening), which this guide covers.
What if the signed PDF is also password-protected?
The tool can open an encrypted PDF by ignoring the password, but it writes the output unencrypted. So the flat copy is decrypted and its signature is broken — purely a render. Keep the protected signed original; if your archive requires encryption on the render, re-apply it with the Password Protect tool.
Can it handle a contract signed by several parties?
Yes. Flatten bakes every signature appearance onto the page no matter how many signers there are. Verify each signature first — the Signature Verifier reports each one independently — then flatten to produce the combined static render. All cryptographic signatures are invalidated equally, so the verification step matters for each.
Does flattening remove the e-signature platform's metadata?
No. Flatten leaves document metadata in place, including the producer string your platform stamped in. To sanitise the archival render, run the Metadata Scrubber afterward — but only on the flattened render, never on the original signed file you are keeping as evidence.
How large a contract can I flatten for free?
Up to 2 MB and 50 pages on the free tier. Long agreements with exhibits can exceed that and need Pro (50 MB / 500 pages) or Pro+Media (500 MB / 2,000 pages). The tool flattens one PDF per run on every tier.
Privacy first
All PDF processing runs locally in your browser using PDF-lib and pdf.js. No file is ever uploaded — only metadata counters are saved for signed-in dashboard stats.