PDF forms

Complete the details. Make it official.

Fill existing text, checkbox, radio and dropdown fields. Or place a new text field or checkbox on the preview.

How to use PDF forms

1. Open your document from your device.
2. Adjust the settings and preview the result.
3. Read text results on screen or download your file. Your original remains untouched.

Local by design

Your documents are processed on your device. No account, payment or document upload is required.

Enable JavaScript to use the document workspace.

Fill supported fields and review their saved appearance

PDF forms helps you complete existing text, checkbox, radio and dropdown fields, or place supported new text fields and checkboxes. It is useful for forms that contain actual interactive controls. A printed blank line or a scanned square is not automatically an interactive field, and this tool does not infer a complete form from every visual template.

Start by checking the issuer’s instructions. Some recipients require an editable form, while others want a static completed copy. An automated portal may expect specific field names or values. Decide which representation is required before adding new controls or flattening an existing form.

Complete the intended controls

1. Open the PDF and inspect the detected fields.
2. Fill text and choose checkbox, radio or dropdown values as appropriate.
3. If adding a supported field, place it carefully on the preview and give it a useful name.
4. Create and download the completed form.
5. Reopen it and inspect every required answer in the saved file.

Field names can differ from visible labels, and several visible widgets can belong to one logical field. Test whether changing an answer repeats it elsewhere. That may be intentional in the source design, but it should not surprise you in the final submission. For a form you create, use clear names and avoid accidental duplicate identities.

Values and appearances both matter

A PDF field can store a value separately from its visible appearance. Different readers can expose problems when those representations do not agree. Check the result after the field loses focus and after the file is reopened, not only while you are typing. A stored value is not enough if the recipient sees a blank box.

Long answers can be clipped or reduced to an unreadable size. Follow the form’s instructions for continuation pages rather than forcing an entire paragraph into a tiny field. Review accented characters, symbols and non-Latin names carefully. If a character does not display correctly, resolve that before sending the form.

Checkboxes and radio groups have different meanings. A radio group normally represents one choice, while independent checkboxes can allow several. Confirm that the selected states match the question’s instructions. A visible mark drawn over a square may not provide the stored value an automated workflow expects.

Decide whether to flatten afterwards

Flattening turns supported field appearances into static page content and removes their interactive behaviour. It can be useful for a final reading copy but inappropriate when the recipient needs to import or edit the fields. Verify the completed form first, then flatten a separate copy only when that is the intended delivery.

Keep a blank template, an editable completed version and a flattened delivery copy distinct where your workflow needs them. Reusing an old completed form can accidentally carry forward personal data or choices. Start from the correct source and review every answer rather than assuming only one date has changed.

Apply a required certificate signature only after finalising the form and following the recipient’s process. Later filling or flattening can change the signed document. Read form filling and flattening and the signing checklist for the complete review. The final test is whether the saved file displays the intended answers and behaves as the recipient requires.

Frequently asked questions

Why are no fields detected on my form?

It may be a scan, a non-interactive template or an unsupported form type. Visual blank lines are not necessarily fields.

Can I add a new field?

The tool supports placing new text fields and checkboxes. Review their names, position and behaviour after export.

Why does one answer appear in two places?

The source may use several widgets for one logical field. Check whether that repeated value is intentional.

Should I flatten before sending?

Only if the recipient wants a static copy. Keep interactive fields when the receiving workflow requires them.

What is the most important output check?

Reopen the downloaded form and verify all required values, selected options, character rendering and clipping.