How to Create a Fillable PDF Form

Use AcroForm fields when recipients should fill in the PDF itself. Use the interactive stamp builder in 1.5.1 for a reusable review mark whose values are entered when it is placed. The saved stamp is an annotation appearance; it does not add fillable AcroForm fields or execute imported stamp JavaScript.

Build an interactive review stamp

PolyPDF can add AcroForm fields to an ordinary PDF or edit supported fields in an existing AcroForm. Authoring is locked when a document is encrypted, permission-restricted, or digitally signed. XFA forms follow separate rules below.

Before placing fields, list what the form collects, which values are required, the tab order, and the viewers recipients use. Keep visible labels in the page artwork; a field is not a substitute for instructions, units, or legal wording.

Work on a copy. Adding or editing fields changes the PDF structure, and it is intentionally blocked on signed documents because rewriting that structure can invalidate the signed revision.

Existing signature and push-button fields can be preserved, but the current builder does not author them. Use the separate digital-signature workflow when cryptographic verification is required.

1. Open the PDF and show the Forms panel from the sidebar or Window > Panels > Forms.
2. Drag a field type from the palette onto the page. You can also select a type and click the page, or choose Add Field for numeric placement.
3. Enter a unique field name. PolyPDF rejects blank names, duplicates, certain bracket characters, and periods because PDF reserves a period for parent-child field-name hierarchy.
4. Add a visible tooltip that identifies the field to someone navigating without relying only on page position.
5. For radio, combo, and list fields, enter one option per line. Radio groups require at least two options.
6. Set the relevant behavior flags, such as Required or Read Only, and add a default value only when the form's business rule calls for one.
7. Set the page and tab order. Arrange the field on the page by dragging its move grip, resize it with the handles, or nudge it with the arrow keys.
8. Repeat with a consistent naming scheme, then save a working copy before the fill test.

Use names that describe data, such as bill_to_company, rather than positions such as top_left_1. Stable names help downstream mappings survive layout changes.

Encrypted or permission-restricted PDFs keep form authoring locked. Digitally signed PDFs also keep authoring locked to protect the signed revision. Obtain an authorized, unsigned source or revise the upstream form rather than trying to defeat those controls.

An unsigned, unrestricted AcroForm can still have Read Only fields. PolyPDF can offer a session override, and Make Permanently Fillable can clear that flag in a new revision. It is unavailable for signed or secured documents and does not unlock every form technology.

• Preserve the original before clearing read-only flags.
• Confirm that you are authorized to alter the form, not merely able to open it.
• Use Undo or Revert to Saved if the result is not the intended form state.
• Apply digital signatures after form design and approved filling are complete, not before authoring changes.

PolyPDF authors AcroForms, not XFA templates. A dynamic XFA form asks a compatible XFA viewer to generate its fields at runtime; PolyPDF preserves that data but cannot fill or author those generated fields as ordinary PDF controls. Some government and enterprise forms are built this way, so check the source form before you plan a conversion around it.

Some static or hybrid XFA PDFs also contain usable AcroForm fields. Those can be filled, but PolyPDF warns about the XFA layer. Saving may remove the stale XFA layer so other viewers show the entered values. Test a copy in the recipient viewer.

If the form must remain an XFA document for an agency workflow, use the workflow and viewer that agency specifies. An AcroForm copy that looks correct will not always be accepted by that submission system.

1. Save a new PDF and reopen it rather than relying only on the unsaved editor view.
2. Tab from the first field to the last. Confirm order, focus visibility, tooltips, and keyboard operation.
3. Enter short, long, blank, and non-ASCII sample values where relevant. Check clipping, scrolling, and multiline behavior.
4. Exercise every checkbox, radio group, combo box, and list box. Confirm defaults, required states, and option labels.
5. Reset representative fields and verify that their default values return as intended.
6. Open the saved copy in at least one other PDF viewer your recipients use, then print or export a test copy if that is part of the workflow.
7. Keep the clean template separate from completed forms and from any later digitally signed record.

PolyPDF preserves JavaScript actions it encounters and evaluates a restricted safe subset used by supported form calculations. It is not a full Acrobat JavaScript runtime. Explicitly test calculations, validation, submission actions, and any enterprise dependency in the viewer your recipients are required to use.