How to Create a Fillable PDF Form (2026)
Most PDFs you'll ever send someone are flat — they're meant to be read, not filled in. But the moment you ask a recipient to type their name, check a box, or pick an option, you've crossed into fillable-form territory, and a flat PDF suddenly becomes a bottleneck. They'll print it, hand-write answers, scan it, and email it back, or they'll give up and text you instead. This guide covers how to convert a flat PDF into a real fillable form with interactive fields, which field types to use, and how to make sure the form works everywhere your recipient might open it.
- Turn any flat PDF into a fillable form — for free, in your browser.
- What Makes a PDF Fillable.
- The Five Field Types You'll Actually Use.
- Covers designing a form people will actually complete.
- Covers flattening vs. leaving the form editable.
What Makes a PDF Fillable
A fillable PDF contains form fields — structured placeholders that software can recognize as interactive. Click one and you type into it. Tab between them and focus jumps predictably. Save the PDF and the values you entered are preserved as field data, separate from the underlying page. This is fundamentally different from typing on top of a flat PDF, where your text is just annotations layered over a picture of a form.
Two form formats exist in the PDF specification. AcroForm is the original, specified in ISO 32000-1, and is supported by essentially every PDF reader ever made — Adobe Acrobat, Preview on macOS, Foxit, browser PDF viewers, mobile apps, everything. XFA is a newer XML-based format that Adobe pushed in the mid-2000s but has since deprecated in PDF 2.0; it only works reliably in Adobe products and is effectively dead outside specialized enterprise workflows. For any form you're creating today, you want AcroForm.
Our PDF Form Builder produces AcroForm fields exclusively. That means the resulting PDF works in every mainstream reader with no special software required on your recipient's end. They don't need Acrobat. They don't need to install anything. They just open the PDF and fill it in.
The Five Field Types You'll Actually Use
Text fields are the workhorse — anywhere you need a name, address, date written out, or a paragraph of comments. Size them to match the visual line on your PDF so filled entries look native. For a single-line field, a height around 16–22 points works well; for multi-line (like a comments box), give it 50+ points of height and it will wrap text automatically when the user types.
-webkit-backdrop-filter alongside backdrop-filter for Safari support. Without the prefix, the effect is invisible to roughly 25% of mobile users.Checkboxes are for independent yes/no choices — 'I agree to terms,' 'I received a copy,' 'Please send updates.' Each checkbox stands alone: checking one has no effect on the others. Keep them small (roughly 14–18 points square) and position them tightly aligned with their labels.
Radio buttons are for mutually exclusive choices within a group — 'Male / Female / Non-binary,' 'Yes / No / Maybe,' 'Option A / B / C.' The grouping is what makes them radio buttons rather than checkboxes. When you place multiple radio buttons with the same field name, selecting one automatically deselects the others. Each individual radio has its own value (like 'Yes' or 'No') but they share the group name.
Dropdowns are for selecting one option from a long list where space is tight — state, country, department, product type. A dropdown with four options takes the same visual space as a single text field, where four radio buttons would take four times as much. The tradeoff is that users can't see all options at once until they click.
Signature fields, strictly speaking, are a separate PDF feature with cryptographic signing behavior, but in practice a plain text field labeled 'Signature' is what most fillable forms use. Our tool creates a signature field as a specially named text field that works in any reader. For forms requiring legally-binding digital signatures with audit trails, you'd use our PDF Signer tool separately after the form is filled.
Designing a Form People Will Actually Complete
Place fields right on top of the existing visual cues in your PDF — the lines, boxes, and underlines that were already meant to indicate where entries should go. If the form was designed with an empty line after 'Name:', drop your text field exactly on that line with the same width. Users will feel like the form was always fillable.
backdrop-filter inside a position: fixed element can cause severe scroll performance issues. Test thoroughly on real iOS devices.Size matters more than you'd think. A text field that's too small forces users to scroll horizontally inside the field to see what they've typed, which makes proofreading impossible. A field that's too tall looks broken. Match the visual expectation set by the original printed layout, and your form will feel polished rather than slapped together.
Name every field meaningfully. Field names appear in the tab order and in any automated form-processing downstream (if you or a recipient ever parses filled data). 'Text1,' 'Text2,' 'Text3' is what happens when you don't — don't let it happen. Use names like 'FullName,' 'StreetAddress,' 'PhoneNumber.' Future-you will thank present-you.
Consider the tab order. Most PDF readers tab through fields in the order they were created. If you build the form header-first then come back to add a missed field in the middle, that field will tab out of order. Our tool creates fields in click order, so work the page top-to-bottom, left-to-right as you place fields and the tab order will match reader expectations automatically.
Flattening vs. Leaving the Form Editable
Once someone has filled out your form, they — or whoever receives it next — has a choice: leave it editable so values can still be changed, or flatten it so the filled data is baked into the page as permanent content. Which you want depends on what the form is for.
Keep it editable when the form represents a draft or a working document. An application that needs review before submission, a contract template being populated by multiple parties, a spreadsheet-style form you'll reuse with different data. Flattening too early locks in mistakes.
Flatten when the form represents a finished record. A signed waiver, a filed return, a completed HR form. Unflattened filled forms are dangerously editable — anyone who receives the file can change the numbers, reverse answers, or alter a signature with two clicks in Acrobat. Flattening prevents this and produces a PDF that's functionally identical to a scan of a handwritten form.
Our PDF Flattener handles the second step after your form is filled. If your workflow needs both — fillable for the user, flattened for the archive — build once with the PDF Form Builder, have the user fill with the PDF Form Filler, then flatten the final copy.
How This Compares to Adobe Acrobat Pro
Adobe Acrobat Pro is the industry reference for PDF form creation. Its 'Prepare Form' feature auto-detects where fields should go on many standard forms, supports complex validation and calculations, and integrates with enterprise workflows like document routing and e-signature platforms. For teams processing thousands of forms with complex business logic, it's the obvious choice.
The barrier is pricing. Adobe Acrobat Pro runs about $239.88 per year for a single user. That's worth it if you're using the advanced features — calculations, conditional logic, JavaScript-driven field behavior, Adobe Sign integration. For the much more common use case of 'I have a flat PDF and I want users to be able to fill it out,' it's a lot of money for features you won't touch.
Our tool covers that common case for free, runs in your browser, and produces standard AcroForm PDFs that work identically in Acrobat Reader (also free), Preview, and every other mainstream PDF reader. If you ever outgrow it and need calculations or validation logic, you can always move up to Acrobat Pro — but you likely won't need to.
Other free tools exist but most come with caveats. PDFgear is genuinely free but requires a desktop download. LibreOffice Draw can create forms but the UX is clunky for quick edits. Browser-based alternatives typically either require signup (Jotform, Paperform, Formplus) or apply a watermark. Running the form builder entirely client-side in your browser is the cleanest tradeoff.
Common Problems and How to Fix Them
If fields don't appear in a recipient's reader, the most common cause is an outdated or unusual PDF viewer. Browser PDF viewers in older versions of Safari occasionally miss fields; the fix is for the recipient to open the file in Preview or Acrobat Reader instead. If you control both ends, test the form in Acrobat Reader (free) before sending to confirm it renders correctly.
If filled values disappear when the recipient saves the PDF, their reader isn't saving form data correctly. Some browser viewers display fields but don't persist values — the classic 'it worked until I emailed it' problem. Ask recipients to save-as from a real PDF reader rather than relying on a browser's built-in viewer.
If radio buttons don't deselect each other, the radio group names don't match. All radio buttons that should behave as a group need identical field names but distinct values. Our tool sets this up automatically when you place multiple radio buttons, but double-check in the Field panel — the name should be the same across all options in a group.
If text in fields appears tiny or cut off, the field is too small for the content. Click the field, adjust its height (for vertical cropping) or width (for horizontal cropping), and export again. There's no universal 'auto-size,' but a field sized to fit the longest expected answer will look right for all answers.