Skip to main content

Work with native PDF forms (AcroForm)

Use this page when your source PDF already contains supported native form fields and you want Bulk Fill to write into those fields directly. This native path applies to supported non-XFA AcroForm PDFs only.

What Counts As A Supported Native PDF Form​

Bulk Fill's native form workflow is scoped to existing native AcroForm fields that are already present in the source PDF. It does not create new native fields or edit the form structure itself.

In the current product, supported native field types are:

  • text fields
  • checkboxes
  • single-select dropdowns
  • radio groups

XFA PDFs are outside this native workflow. If the PDF is XFA, use overlays instead.

Why Native Form Fill Matters​

When a PDF already contains supported native fields, native form fill is often the cleaner and more professional path for structured business documents.

That is especially true for workflows such as:

  • HR and onboarding forms
  • internal operations paperwork
  • customer intake documents
  • registration forms
  • order or service forms

Instead of placing every changing value as an overlay, you can use the form layer the PDF already provides.

How CSV Mapping Works For Native Fields​

In the web app:

  1. Upload the source PDF and CSV.
  2. Open the Form tab.
  3. Add the native row type you need:
    • Add Form Field
    • Add Checkbox
    • Add Dropdown
    • Add Radio
  4. Choose the native PDF field for that row.
  5. Choose the CSV column that should drive it.
  6. Preview representative rows before exporting.

Native mappings keep their own row identities in the Form tab:

  • text rows use FF
  • checkbox rows use FC
  • dropdown rows use FD
  • radio rows use FR

Bulk Fill also shows native guide boxes on the PDF canvas so you can confirm which native field you are working with.

Field Types In The Current Native Workflow​

Text Fields​

Use native text fields when the PDF already has a real text input in the right place. This is often the most natural way to fill names, IDs, dates, or short structured values.

Checkboxes​

Use native checkboxes when the source PDF already defines the check state as a native form field.

Use native dropdowns when the PDF already includes a supported single-select choice list. Bulk Fill follows the current dropdown matching contract described in CSV Mapping Guide.

Radio Groups​

Use native radio groups when the source PDF already includes a supported native radio choice. Bulk Fill follows the current radio matching contract described in CSV Mapping Guide.

What To Validate In Preview​

When you preview native form output, check all of these:

  • text appears in the intended native field
  • checkboxes reflect the expected checked or unchecked state
  • dropdowns resolve to the intended visible option
  • radio groups resolve to the intended option token
  • warning messages are reviewed before you trust the batch

Preview a few representative rows, not just one safe example. That matters most for choice fields, blank values, and unusual rows.

For a deeper checklist, read Preview, Validation, and Export.

When Flattening Matters​

On supported non-XFA PDFs, Flatten form fields turns editable form fields into static content in the export.

Use flattening when you want a final non-editable output. Leave it unchecked when you intentionally want the exported form fields to remain editable.

If the PDF is XFA, native form fill is unavailable and Flatten form fields does not apply to that native workflow.

When Overlays Are Still Better​

Overlays remain the right choice when:

  • the PDF does not already contain the native fields you need
  • you need to place content anywhere visually on the page
  • you need overlay QR codes or barcodes
  • the document is XFA
  • the native field type is outside the supported scope

You can also combine methods. A common pattern is to use native fields for the main form data and overlays for extra codes, labels, or fixed content.

Native form fill is especially useful when the PDF already comes from another system with a real form layer, such as:

  • onboarding packets with existing checkboxes and dropdowns
  • internal approval forms with defined answer choices
  • customer intake forms with structured selections
  • registration forms with repeated field layouts
  • service or order documents that already include fillable fields

Next Steps​