Making a fillable PDF form
Most forms in circulation are dead PDFs: a document designed to be printed, filled in with a pen and scanned back. Adding real fields turns the same file into something that can be completed on a laptop or a phone, and it takes minutes rather than a redesign.
The field types and what each is for
Six types cover nearly every form. **Text** for a single line — a name, a reference, a short answer. **Multiline** for anything that runs over, such as a description or an address; sizing it honestly is a kindness, since a field one line high tells people you did not expect them to write anything. **Date** for dates, which stops the argument about which number is the month. **Checkbox** for yes or no and for consent lines. **Dropdown** for a closed list, which is how you avoid transcribing forty spellings of the same option. **Signature** for the place a signature goes. Choose by what the answer is, not by what fits the layout.
Placing fields on an existing document
Draw each field over the space the printed form left for it, rather than next to it. Match the box to the line or the ruled area so the filled form still looks like the form. Keep the fields in a sensible tab order — down a column, then across — because a form that jumps around when you press tab is a form people fill in wrongly. And leave the printed labels alone: the label on the page is what tells the reader what the field is for, and duplicating it inside the field just clutters the page.
What happens to the values
A filled field stores its value as data in the file, separate from the page content. That is what makes the form fillable, and it has a consequence worth knowing: a field can display as blank while still holding what was typed. If you are handling a form that was filled in and needs to be shared with the answers removed, do not clear the display — remove the values, or produce a redacted output and verify it, exactly as you would for any other hidden data. The article on hidden data in PDFs covers the rest of the places this bites.
Before you send the form out
Fill it in yourself, on a phone as well as a laptop. It is the fastest way to find the field that is too small, the tab order that jumps, the checkbox that is easy to miss and the dropdown whose options do not cover the common case. Then check that it opens correctly in a plain viewer as well as your own — form support varies, and a form that only works in one program is a form half your recipients will print and fill in with a pen anyway.
Frequently asked questions
Can I add fields to a PDF I did not create?
Yes. Fields are placed over the existing page; the underlying document is not modified.
Which field types are available?
Text, multiline, date, checkbox, dropdown and signature.
Will the form work in any PDF reader?
Standard fields work in mainstream viewers, but support varies, particularly on mobile and in browser previews. Test the finished form in more than one.
Can people fill it in on a phone?
Generally yes, in a proper PDF app. Browser previews are the weakest link, which is another reason to test.
Do the filled-in answers stay in the file?
Yes, as field data. A field can look blank and still hold a value, which matters if the completed form is shared onward.
Can I add a signature field without an e-signature service?
You can add a place for a signature. Whether a drawn signature is legally sufficient for your purpose is a separate question and depends on your jurisdiction.
Remove the text, then prove it is gone. Redact takes the words out of the page rather than covering them, then reopens the file it just made and searches it twice — by text extraction and by raw stream scan — before letting you download. The file never leaves your browser.
Redact a PDF in the browser