Choose the completed form
Open an unlocked PDF and review its detected field count and field types. A scan with printed blank boxes has no interactive fields to flatten.
A filled form may display differently across PDF readers when field appearances are incomplete. Flattening updates supported field appearances and draws them into the pages. It deliberately removes their interactive field behavior. This is different from removing comments, rasterizing every page or securing a document against all future editing.
Open an unlocked PDF and review its detected field count and field types. A scan with printed blank boxes has no interactive fields to flatten.
Inspect the original form in a reader and save any intended values. Keep an interactive original if you need to edit or reuse it later.
Confirm that you want fixed field appearances. The workflow updates appearances, removes XFA data when present and flattens supported AcroForm fields.
Download and check the output in the reader used by your recipient. Verify text, checkboxes and chosen options, especially unusual fonts or language characters.
Accepts one non-empty PDF up to 150 MiB without an explicit page-count cap. At least one interactive AcroForm field must be detected.
Flattening is intentionally irreversible in the saved copy as an interactive-form operation. It does not flatten every annotation or rasterize whole pages. XFA-only forms may have no usable AcroForm fields; appearance generation can fail on unsupported text.
Create a fixed-value reading copy after reviewing the answers.
Regenerate supported appearances before flattening, then verify the saved result in another reader.
Retain both the interactive working form and a separate flattened record.
Field inspection and flattening happen in the browser. Document bytes and filled values are not uploaded for processing. Website resources can still load from the network.
Select a question to view the answer.
They are page content in the saved copy. Keep the interactive original for field editing.
The workflow targets form fields, not all annotations.
No. Use password protection separately when appropriate.
A scan has no interactive field objects unless another workflow added them.
Open another Fylvexa tool that works well with this task.