By Jetformat
PDF form filling assigns values to interactive fields. Flattening turns field appearances into page content for a delivery copy. Fill and verify an editable version first; flattening does not replace the checks needed to establish that the answers are correct.
Discover the actual fields
jetformat pdf fields form.pdf > fields.json
The visible label beside a field may differ from its internal name. Use the returned names rather than deriving keys from a screenshot. The fill command expects a name/value array; edit the exported data locally and retain only the values you intend to submit.
If no interactive fields are found, the document may be a static page or a scan. A drawn rectangle is not automatically a fillable field. Do not promise that entering arbitrary JSON keys will make text appear there.
Fill a new copy and inspect it
jetformat pdf fill form.pdf --json fields.json -o filled.pdf
jetformat pdf fields filled.pdf
jetformat pdf render filled.pdf --pages 1 --width 1600 -o form-preview
Check field values and visible appearances. Long names can clip, and a correct stored value does not guarantee that the intended viewer will display it correctly. Review every filled page when the form spans multiple pages.
Flatten only the approved result
jetformat pdf flatten filled.pdf -o delivery.pdf
jetformat pdf fields delivery.pdf
Keep the blank form and the filled editable version. Flattening places field appearances into page content and removes the ordinary field-editing workflow. It is useful for a delivery copy but does not encrypt the document or remove private data.
See listing PDF fields, filling fields, and flattening forms. Use the PDF security guides for distinct tasks such as encryption or redaction.
Compare blank, filled, and flattened copies
| Copy | Purpose | Keep it when |
|---|---|---|
| Blank source | Reusable form and field inventory | Future records need the same form |
| Filled editable PDF | Review values and make corrections | The answers are not final |
| Flattened delivery PDF | Distribute the reviewed appearance | The ordinary field-editing workflow is no longer needed |
A PDF containing lines and labels may have no interactive fields. Inspect the field list before preparing values. If the expected field is missing, investigate the source instead of guessing a name from the page image.
Prepare the values and verify the delivery
- List the source fields and retain the exact internal names.
- Prepare the name/value array required by
pdf fill. - Fill a new file and inspect the stored values and visible appearances.
- Correct clipping, wrong values, or missing fields before flattening.
- Flatten a separate delivery copy, inspect it again, and retain the editable copy privately when needed.
For a form field actually named Customer, an illustrative value file is:
[{"name":"Customer","value":"Example customer"}]
That identifier is an example, not a universal PDF field name. Use your source’s inventory, and check non-text controls according to the values supported by the actual field.
Count the separate writes
For an illustrative 3-page form, filling uses 3 credits, flattening the 3-page result uses 3 credits, and rendering all 3 delivery pages adds 3 credits: 9 credits total. Field listing is free. If a correction requires another successful write, include that extra operation in your estimate.
Flattening does not encrypt the PDF, redact sensitive answers, or establish signature validity. Review those requirements independently. The PDF security comparison explains the different goals.