Flatten Forms

Turns a filled PDF into a fixed copy of itself: the values are locked into the page, and there are no form fields left to edit or clear.

Overview

A filled PDF form is not as finished as it looks. The values live in form fields, which means they are still editable — by the recipient, by a reviewer who clicks in the wrong place, and by whatever PDF app the file passes through on its way to its destination. Some submission systems will not take a PDF with live fields at all.

Flattening ends that. Each page of the filled form is replaced by a fixed rendering of that page, values included: the typed text, the checkmarks and the selections are all still there to look at, in the same places, and there is nothing left to click into.

The trade-off is real and worth knowing before you rely on it. What comes back is a rendering of the document rather than the document: nothing in it can be selected, searched or copied, and its pages no longer carry the dimensions they started with. That makes flattening the right last step for a file that is leaving, and the wrong one for anything a later step still has to read.

What It Does

When This Runs

Nothing decides this on your behalf. Flattening is a download-time choice: a filled form is downloaded as a non-editable copy because someone asked for one, and without that request the file downloads with its fields intact. It is not a step the agent selects, and it is not applied automatically on the way out.

Two cases where you should not ask for it:

• The recipient still has to fill something in. A form going out for a counterparty to complete, or a draft going back for corrections, needs its fields live.
• A later step still has to read the values. Anything that reads values back out of the form structure — Extract Form Fields, for instance — has to run before the flatten, because the flat copy has no fields left to read.

Inputs and Outputs

Takes: a single filled PDF. A file that is not a PDF is rejected.

Returns: a PDF with the same number of pages in the same orientation, the field values fixed into each page, and no interactive form fields.

Example

An estimator finishes a bid cover sheet in the browser: bidder name, solicitation number, a checked certification box, a unit-price table. The agency wants a PDF nobody can alter after it is submitted.

They download it as a non-editable copy. What comes back has the same pages in the same order and every value sitting exactly where it was typed — but no fields at all. The certification box is a printed checkmark now rather than a control, and none of the text can be selected or searched.

An hour later the estimator spots a wrong unit price. The still-fillable version is untouched, so the fix happens there and a fresh non-editable copy comes out of the same download.

Limits

• The flat copy is a rendering, not the original. Nothing in it can be selected, searched or copied — not the field values, and not the text that was already printed on the form. Its page dimensions are larger than the original's, so it no longer reports the paper size it started with. If the recipient requires a text-searchable PDF, or a specific paper size, this is not the format they want.
• Output size is unrelated to input size. Every page is re-rendered, so a small text-only form can come back substantially larger. Flattening is not a way to reduce file size.
• Flattening is one-way in the output. The flattened file cannot be converted back into a fillable form with its original fields. Corrections are made on the retained editable version and re-flattened, not edited into the flat file.
• Flat is not secure. Flattening prevents field editing, not determined tampering — page content can still be altered in a full PDF editor. Controlling who can open, print or copy a file is a separate problem, and flattening does not address it.
• It is not a digital signature. A flattened document proves nothing about who filled it or when. An image of a signature on the page is visual, not cryptographic.
• An unfilled field leaves behind whatever the form draws. Flattening fixes whatever the form currently contains, and each field is rendered the way the form defines it. A field with a border or a background colour leaves a visible empty box, so the omission shows; a field with neither leaves nothing at all, and the gap is invisible in the finished document.
• Password-protected files fail. A PDF that cannot be opened without its password is not flattened. The request fails rather than returning the file unchanged.
• Downstream field reading stops working. Any step that needs to read values back out of the form structure has to run before the flatten, not after.

FAQ