Rename Form Fields - Free Online Browser Tool

Replace text inside form field names so templates and automation can address them.

Field names are the keys everything downstream keys off — mail merge, template engines, accessibility checkers and signature platforms all address fields by name. Exported forms routinely arrive with names like topofp1 that mean nothing to a human, and this renames them without touching the form itself.

This rename form fields utility runs completely inside your web browser. Your document is opened locally and processed on your own device using JavaScript and WebAssembly, so your file is never uploaded to any server. There is no signup, no watermark and no limit on how many documents you can handle.

  • 100% client-side - files never leave your device
  • Instant processing, no upload wait
  • Works on desktop, tablet and mobile
  • Free forever, no account required

Common next steps: Inspect & List Form Fields, Add TextField / Checkbox, Export Form Data (JSON), Inspect Form Field Properties.

How to Use the Rename Form Fields Tool

Four steps, and the whole thing runs locally on your own device.

  1. Load the form

    The document must have interactive fields; a flat scan has none to rename.

  2. Enter the text to find

    A fragment of the existing name, such as topofp or Text1.

  3. Enter the replacement

    Use a name that describes the field, since this is what a template will reference.

  4. Download

    You get the renamed PDF plus a list of every change that was made.

Frequently Asked Questions

Will renaming break the form?

No. Field names are labels, not behaviour. The field keeps its type, its position and its value — only the key used to address it changes.

What happens if two fields end up with the same name?

The rename is refused before anything is written, because duplicate names make a form ambiguous and some platforms silently pick the wrong field.

Can I rename only part of a name?

Yes. Replacing a fragment is the normal case — turning six fields called Text1 to Text6 into address1 to address6 is one operation, not six.

Does it rename in a specific order?

No, it replaces wherever it finds the fragment. Restrict it to the start or the end of a name when a short fragment would otherwise match too much.

Do I need to rename every field?

No. Only the ones a template or integration actually references; the rest can stay as the exporter named them.