When to use this
Someone designed a beautiful form in Word or InDesign, exported it as a flat PDF, and now expects people to fill it in digitally. Without fillable fields, recipients are stuck printing it out, writing by hand, and scanning it back. This tool bridges that gap — you overlay interactive fields on top of the static PDF so anyone can type directly into it.
Common scenarios: employee onboarding packets that HR designed but forgot to make interactive, client intake forms for law firms or clinics, internal checklists that need sign-off fields, and event registration forms that get emailed as attachments. If the PDF already exists and you just need to make it fillable, this is faster than rebuilding it in Adobe Acrobat.
It is also useful for adding a signature field to a contract or agreement that was originally created without one. Drop a signature box at the bottom of the last page and you have a signable document in seconds.
Good to know
AcroForm is the standard that actually works. PDF has two competing form technologies: AcroForm (the original, supported everywhere) and XFA (Adobe's XML-based format, poorly supported outside Acrobat). This tool uses AcroForm, which means your fillable PDF works in Adobe Acrobat, Preview on Mac, Chrome and Firefox's built-in PDF viewers, and most mobile PDF apps. XFA forms routinely break outside Adobe — AcroForm does not.
Four field types cover most use cases. Text fields handle names, addresses, and free-form input. Checkboxes work for yes/no questions, agreement acknowledgments, and multi-select lists. Date fields provide structured date entry. Signature fields designate where a signer should place their mark. These four cover the vast majority of form workflows without overcomplicating things.
Field naming matters more than you think. If you plan to extract form data programmatically later (via PDF libraries or form processing services), give each field a clear, unique name like "applicant_name" or "agree_terms" rather than "Field1." It saves significant headaches downstream.
The underlying PDF is untouched. Form fields are layered on top of the existing page content. The original text, images, and formatting remain exactly as they were. If a recipient opens the PDF in a viewer that does not support forms, they still see the full original document — the fields just will not be interactive.
Filled-in data can be saved by the recipient. When someone fills out your form and saves the PDF, their responses are stored in the file. They can reopen it later and their answers are still there. This is standard AcroForm behavior — no special "save permissions" are required.
Quick Reference
| Field type | Best for | Compatibility |
|---|
| Text field | Names, addresses, free-form answers | All PDF readers |
| Checkbox | Yes/no, agreements, multi-select | All PDF readers |
| Date field | Dates of birth, deadlines, event dates | Most PDF readers |
| Signature field | Contract sign-off, approval workflows | Acrobat, Preview, most mobile apps |