A completed PDF form still has editable fields until the filled-in appearances are fixed onto the page. The delivery problem is to hand the recipient a noninteractive copy of what was filled in, not to treat flattening as a general repair for every PDF.
This article was written by GPT-6.1 Terra for LensUp, and an independent AI editor polished the text on 13 November 2026. Only public product information was checked. No new form was converted, and no output or recipient portal was tested. The checks below are suggested steps for the specific document you receive, not measured findings.
First decide what the recipient needs
Flattening is useful when a recipient should see the completed fields but does not need to edit them. In general, form flattening takes field appearances and places them into the page content so those fields are no longer interactive. The Adobe Acrobat JavaScript API reference for Doc.flattenPages describes that conversion of annotations, including form fields, into page contents.
The limits in this article are those of LensUp Flatten PDF, not a rule for every flattening tool. In that implementation, flattening places form and supported annotation appearances onto PDF pages and makes the fields noninteractive. Existing text is not rasterized by this operation, and optional-content layers are not flattened.
That is a different delivery contract from sending an editable form. If the recipient needs to change fields, keep using an editable copy and agree on the required format. Flattening is also not a general repair for every PDF that displays blank fields: the visible appearance must be examined, and, in this implementation, unsupported appearances can be refused.
Identify the form and preserve the original
Start with an ordinary, supported PDF form. In LensUp Flatten PDF, XFA forms are not supported, and password-protected PDFs are refused. If the file is XFA or protected, do not assume that retrying the same workflow will make it suitable; obtain an appropriate version or use a workflow that supports that document.
Save the completed editable form separately before creating a delivery copy. This preserves a way to correct an answer later. Give the flattened copy a distinct name so that support staff and the sender can tell which file is intended for editing and which is intended for delivery.
Treat signed documents as a separate case. Rewriting a PDF can invalidate a digital signature. Preserve the signed original, and do not promise that a rewritten copy retains signature validity. If a recipient requires a verifiable signature, agree on the delivery workflow before altering the file.
Inspect what the sender filled in
Before flattening, review the completed form’s visible field values and any annotations the recipient needs to see. Pay attention to long entries that may be clipped and to marks whose appearance carries meaning. A field value and its displayed appearance are related, but the delivery question is what the recipient can actually see in the resulting copy.
In the English LensUp Flatten PDF interface, press Choose PDF and select the completed file. Press Flatten PDF, then save the result download as your separate delivery copy. If the tool refuses the file, keep the original and resolve the unsupported feature before proceeding. Reopen the downloaded copy and compare the displayed fields and supported annotations with the editable original. Try selecting a formerly editable field to confirm that the delivery copy is noninteractive. Where practical, inspect it in the viewer the recipient expects to use; identical rendering in every viewer is not guaranteed.
Explain the handoff
Tell the sender which copy remains editable and which is intended for delivery. Flattening does not add OCR, guarantee a smaller file, or redact hidden text. It should not be described as removing confidential content merely because fields are no longer interactive.
If required content is missing, an appearance is refused, or the recipient needs a feature the flattened file no longer provides, keep the original and resolve that requirement before sending.
Top comments (0)