How to Create a Fillable PDF (and When to Have It Built for You)

A fillable PDF is an ordinary PDF with form fields on top: places where a person can type, tick, choose from a list or sign, using nothing more than the PDF viewer they already have. Done well, it replaces printing, handwriting and re-typing with a document that people complete in minutes and that your team can read back as data.

This guide covers how to build one yourself, the choices that decide whether it works on your customers' devices, the mistakes we see most often, and the point at which having it built for you is cheaper than doing it twice.

Start with the document, not the software

Before opening any tool, print the current form (or open it on screen) and go through it with a pen. Mark every place a person has to write something, every yes/no choice, every 'pick one of these', every date and every signature. That list is the specification. Most bad fillable PDFs come from skipping this step and adding fields wherever there happens to be a line.

For each item, decide who fills it in (the customer, your team, or both), whether it is required, and where the answer ends up afterwards: a spreadsheet, a CRM, an email, a filing cabinet. If the answers need to go somewhere, the fields need consistent names, which matters later.

Choose the right field for each answer

Text fields are for free answers: names, addresses, notes. Set a font size and, for multi-line answers, allow the field to scroll or grow. Checkboxes are for independent yes/no items: 'send me updates', 'I have read the terms'. Radio buttons are for one choice from a small set that should all be visible: payment method, size, membership type. Dropdowns are for one choice from a longer list where space is tight: country, department, product code.

Date fields should be real date fields with a format, not text fields labelled 'date', so the answer is consistent. Signature fields let the person sign in Acrobat, Preview or a mobile viewer. Calculated fields (line totals, grand totals) are useful on order forms and quotes but are the first thing to break in lightweight viewers, so keep them simple.

The tools that can build one

Adobe Acrobat Pro is the reference tool: it recognises fields automatically from an existing PDF, lets you set every property, and its output works everywhere. LibreOffice Draw and Writer can add form controls and export to PDF for free, with less polish. Microsoft Word can produce a PDF with fields if you build the form with content controls, though the result is less reliable across viewers. Online editors vary widely; check that the exported fields are real PDF form fields rather than flattened images.

Whatever you use, the test is the same: open the finished file in Acrobat Reader, in a browser (Chrome and Edge render PDF forms themselves), in macOS Preview if your customers use Macs, and on a phone. Fields that work in one and not another are the most common complaint we hear.

Make it usable, not just fillable

Set the tab order so pressing Tab moves through the form in reading order. Mark required fields visibly and consider making them required in the field properties. Give every field a clear label next to it, not only a placeholder inside it, because placeholders disappear when typing starts. Use enough space: a 10-point field for a full address guarantees an unreadable answer.

Keep the branding light and consistent: logo, one accent colour, one typeface. Lock the parts of the document that should not change (terms, prices on a quote template) so the person completing it cannot accidentally edit them. Finally, save a master copy you never send out, and duplicate it for each use.

Mistakes that make fillable PDFs fail

Flattened exports: some tools 'print' the form to PDF and the fields become pictures. Nothing can be typed. Fields with duplicate names: two fields called 'Name' will mirror each other's contents. Fonts that are not embedded: the form looks different on the recipient's machine. Calculations that reference fields by the wrong name and silently return zero. Signature fields placed on a page with security settings that block signing.

The other class of failure is process, not technical: sending a fillable PDF but asking people to print and post it anyway, or collecting hundreds of completed forms and re-typing them because nobody planned how to read the data back out.

When to have it built for you

Building one form once is a reasonable afternoon's work. It stops being reasonable when the form has several pages and dozens of fields, when it needs calculations or signatures that must work on every device, when it is a template your business will reuse for years, or when the answers need to flow into a system rather than an inbox.

That last case is where a document becomes a workflow. A form with named fields can be read automatically and its answers routed into a spreadsheet or CRM, and a contract or quote can be generated pre-filled from your data. TaimurTools builds fillable PDFs and, where it makes sense, the automation around them, as one project with a fixed quote.