Fill a PDF Form

How it works

Interactive PDF forms store a form dictionary and a collection of fields. On opening, the server reports each field's name and type. Text fields become text inputs, checkboxes become boolean controls, and dropdown fields expose their own option list. The tool does not infer a label from the page drawing; it uses the field name supplied by the document, which is why well-authored forms are easier to complete.

When you save, the source is loaded again and each entered value is applied to the matching field by name. A new PDF is then serialized in memory. Reopening the source for saving avoids mutating the document object used to inspect the form and keeps the original file available for comparison. Flattening asks the PDF form layer to turn the values into fixed appearances after they have been set.

Form limits that matter

PDF forms are not all built alike. A field can have a visual widget but rely on JavaScript calculations, a remote submit action, an XFA form model, or a signature provider. This local utility intentionally covers common AcroForm controls and leaves advanced behavior alone. A completed-looking file is not proof that calculated totals, validation rules, or submission buttons still behave as they did in the author's software.

Review the downloaded document in the reader that will receive it. Check long names, multiline fields, checkbox state, dropdown text, page appearance, and any required fields the PDF itself does not mark clearly. Keep a copy of the source and do not treat flattening as an integrity signature.

Field names are the author's, not the form's

The inputs are labeled with the names stored inside the document, which is why a well-built form is pleasant here and a badly-built one is a puzzle.

A careful author names fields for what they hold: applicant_surname, date_of_birth, agree_terms. A form assembled in a hurry — or converted from a scan by a tool that detected boxes automatically — gets Text1, Text2, Check Box 7, in an order that follows how the boxes were created rather than how the page reads.

There is no way to recover the visible label from the field name, because the label is drawn on the page as ordinary content with no link to the widget that sits near it. The tool could guess by looking for the nearest text, and deliberately does not: a guess that is right most of the time is worse than no label, because it teaches you to trust it right up until it puts your surname in the wrong box.

The reliable method with an opaque form is to open the original alongside, fill one distinctive value at a time — a recognizable string, not a real answer — save, and see where it lands. Two or three passes usually map the whole document, and you only need to do it once per form.

Flattening is a one-way door

Flattening converts each field's value into ordinary page content and removes the interactive layer. It is the right choice more often than not, and it cannot be undone.

Do it when the form is finished and going to someone who should not change it, or when you need it to look identical everywhere. Unflattened forms render through each viewer's own form layer, and appearance genuinely varies — a browser's built-in viewer, a phone mail client and desktop Acrobat can differ in font, size and alignment, and some mobile viewers do not render field values at all, so a recipient sees a blank form and tells you it did not arrive.

Do not do it while anything is still in progress, and do not do it if the recipient needs to complete the remaining fields — flattening removes their boxes as surely as yours. Never do it to a form whose totals are computed by embedded JavaScript without checking the numbers first: the calculations run when a value changes, and if they have not run, flattening freezes whatever was displayed, which may be zero.

Always keep the unflattened version. The flattened file is a new document, not an updated one, and there is no path back to editable fields from it.