Skip to main content
Forme supports native AcroForm components for creating interactive fillable PDF forms. Form fields work in every major PDF viewer without JavaScript or external form handling. Users fill in fields directly in their PDF viewer, and you can flatten forms at render time to lock in values as static content.

TextField

A single-line or multiline text input field.

Props

Example


Checkbox

A checkbox with checked or unchecked state.

Props

Example


A select dropdown with predefined options.

Props

Example


RadioButton

A radio button. Group multiple radio buttons by giving them the same name. Only one in the group can be selected at a time.

Props

Example

All three radio buttons share name="paymentMethod", so selecting one deselects the others.

Full Example: Contact Form


Form Flattening

Flattening converts interactive form fields into static PDF content. The visual appearance is preserved, but users can no longer edit the fields. This is useful when you pre-fill a form with data and want to send a finalized, non-editable PDF.

At render time

Pass flattenForms: true to the render options:

Via the hosted API

Pass flattenForms=true as a query parameter on any render endpoint:
See the Hosted API reference for details.

Edge cases

  • Flattening a form that has no fields produces an unchanged PDF.
  • Fields with no value flatten to empty space (the field widget is removed).
  • Read-only fields and editable fields are both flattened. The readOnly prop has no effect on the flattened output.

Known Limitations

  • Helvetica only for form field text. PDF form fields use the built-in Helvetica font regardless of the document’s font settings. This means form field text is limited to Latin characters. Document text outside of form fields uses your custom fonts as expected.
  • Field name collisions. If two fields share the same name (and are not radio buttons in the same group), they will be linked — editing one updates the other. Use unique names for independent fields.
  • macOS Preview quirks. macOS Preview renders basic text fields and checkboxes correctly, but dropdowns and radio buttons may not behave as expected. Use Chrome’s built-in PDF viewer or Adobe Acrobat for full form interactivity.

Viewer Compatibility

For the most reliable cross-platform experience, recommend Chrome or Adobe Acrobat to your users. If you need guaranteed rendering on all viewers, flatten the form before sending.