How to Create Fillable PDF Forms: 3 Methods

A fillable PDF contains interactive form fields that a recipient can select, type into, save, or print. The most suitable method depends on your starting file and the behavior you need:

• Adobe Acrobat: best for creating fields in a blank PDF or adding fields to an existing PDF.
• Microsoft Word desktop: best when the document itself is your form source and you need text controls, checkboxes, dates, or dropdowns.
• LibreOffice Writer: a free route that exports supported form controls as PDF fields.

After export, open the PDF in the viewer your recipients will use and test every field. Visible lines or blank spaces do not prove that a PDF is interactive.

1. Create a fillable PDF in Adobe Acrobat

Acrobat has a dedicated Prepare a form workflow. It can start with a blank page or detect fields in an existing PDF or source document. See Adobe’s official PDF forms documentation for current labels and interface details.

From a blank page

1. Open Acrobat and choose Prepare a form.
2. Choose Start from blank page.
3. Add the fields your recipient needs: text fields, checkboxes, radio buttons, dropdowns, list boxes, signatures, or other available components.
4. Set each field’s name, required status, appearance, and behavior in its properties.
5. Choose Preview and complete the form as a recipient would.
6. Save the PDF and reopen the saved copy to confirm that values persist.

Convert an existing document

1. Open Prepare a form.
2. Select an existing PDF or another supported source document.
3. Let Acrobat detect likely fields, then inspect every detected field.
4. Add, delete, resize, rename, or reposition fields where detection is incomplete.
5. Preview, save, close, and reopen the final PDF.

Field design checklist

• Give every field a unique, meaningful name.
• Mark only genuinely required fields as required.
• Use radio buttons when exactly one option is allowed; use checkboxes when multiple options are allowed.
• Use dropdowns for a short, fixed list and list boxes when several visible choices are useful.
• Set a sensible font size and enable multiline text where long answers are expected.
• Use tooltips or accessible labels so users know what to enter.
• Check tab order so keyboard users move through fields logically.

2. Build the form in Microsoft Word desktop

Microsoft’s instructions explain that Word can create a form users complete, save, or print. The workflow uses the desktop application’s Developer tab; Microsoft says form creation is not available in Word for the web. See Microsoft Support’s form guidance.

Enable Developer tools

1. Open Word desktop.
2. Open Word Options and customize the ribbon.
3. Enable the Developer tab.
4. Start from a blank document or a form template.

Add controls

1. Place the cursor where a response belongs.
2. From Developer > Controls, insert a plain-text or rich-text control.
3. Add checkbox controls for independent yes/no choices.
4. Add a date picker for dates.
5. Add a dropdown or combo box, then define its choices in the control’s properties.
6. Use design mode and properties to set prompts, defaults, and editing behavior.
7. Protect the document if recipients should edit fields but not the surrounding layout.
8. Turn off design mode and complete the form yourself.

Word-to-PDF limitation

Word content controls make a Word form. Simply exporting that document does not guarantee that the controls become interactive PDF fields. If the deliverable must be a fillable PDF, use a PDF form workflow after export, such as opening the PDF in Acrobat and checking or adding fields with Prepare a form. Test the resulting PDF in the target viewer.

3. Create a PDF form with LibreOffice Writer

LibreOffice Writer includes a Form Controls toolbar and can export supported controls as PDF fields. The LibreOffice Writer Guide, Chapter 18 documents the workflow and its limits.

Build and export the form

1. Open Writer and create the document layout.
2. Enable View > Toolbars > Form Controls.
3. Insert controls such as text fields, checkboxes, radio buttons, list boxes, or combo boxes.
4. Open each control’s properties to set its name, label, default value, and choices.
5. Use form design mode while arranging controls, then disable it to try the form.
6. Choose File > Export As > Export as PDF.
7. In the PDF options, ensure Create PDF Form is checked.
8. Export, close, and reopen the PDF in the viewer your recipients will use.

LibreOffice constraints

Not every Writer control maps to a PDF field. The guide also documents that data binding, macros, and scripts are not preserved in PDF 2.0, and validation or formatting may be limited. Treat the exported PDF as a separate deliverable and verify the behavior you require.

How to choose among the three methods

Question	Acrobat	Word desktop	LibreOffice Writer
What is your starting point?	Blank PDF or existing PDF/document	Editable Word document	Writer document and form controls
Where are fields designed?	Directly in the PDF	In the Word document	In Writer before export
Best fit	Interactive PDF field work	Document-first forms	Free desktop workflow
Key caution	Review detected fields and tab order	Word controls may not become PDF fields automatically	Some controls and advanced behavior do not survive export

Testing checklist before distribution

1. Open the saved PDF in the viewer your recipients will use.
2. Navigate with the keyboard and confirm the tab order.
3. Enter short, long, accented, and multiline values.
4. Try every checkbox, radio group, dropdown, and date field.
5. Leave required fields empty and confirm the intended behavior.
6. Save, close, and reopen the completed PDF.
7. Print a completed copy and check that values appear where expected.
8. Check the file on desktop and mobile if both are supported.
9. Remove accidental editing restrictions that prevent legitimate completion.

Common problems and fixes

Problem	Likely cause	Fix
The PDF looks like a form but cannot be typed into	It contains visual blanks, not interactive fields	Add PDF fields in Acrobat or export from Writer with Create PDF Form enabled
Word controls disappear after export	Word content controls were treated as document layout	Open the exported PDF in a PDF form editor and add or verify fields
Fields are in the wrong locations	Automatic field detection misread the layout	Move, resize, rename, or recreate each field and preview again
A checkbox behaves like a radio button	Controls were grouped incorrectly	Use separate checkbox fields for independent choices; use one radio group for a single choice
Long answers are cut off	The field is single-line or has a small fixed font	Enable multiline input, enlarge the field, or reduce the font size
Values do not remain after closing	The viewer does not support saving, or the file was not saved after completion	Use a compatible PDF viewer, save a new copy, and reopen it to verify
LibreOffice fields are missing	The control is not supported in PDF export or Create PDF Form was unchecked	Use a supported control and enable Create PDF Form during export
Validation or scripts fail	The target PDF format or viewer does not preserve advanced behavior	Keep validation simple, test in the target viewer, or use a dedicated PDF editor

Performance, reliability, and cost considerations

• Performance: Field count and complex page layouts affect editing time more than the final PDF’s completion speed. Keep repeated fields consistent and avoid unnecessary artwork.
• Reliability: The saved PDF is the artifact that matters. Reopen it after export, test in the intended viewer, and keep an editable source copy.
• Compatibility: Basic text, checkbox, radio, and choice fields are generally safer than scripts, macros, or data binding. Verify mobile and browser viewers separately.
• Cost: Acrobat is a paid dedicated PDF workflow; Word requires desktop Word; LibreOffice provides a free desktop option. Select based on required field behavior and existing software access.

Or skip the browser setup

If you need screenshots of a form workflow, documentation pages, or rendered PDF previews, ScreenshotNeo provides a website screenshot API and MCP server. Its one-call endpoint returns PNG, JPEG, WebP, or PDF output.

See the ScreenshotNeo API documentation for all options. This basic request captures a URL:

cURL

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Cookie banners, newsletter popups, and chat widgets are removed before the shot. Bot checks, blank pages, failed loads, timeouts, and cache hits are never billed, and response headers identify the page verdict and billing status. An MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots each month with no card, and paid plans start at $5 for 3,000 shots.

Sign up for ScreenshotNeo’s free plan.

FAQ

Can I make a fillable PDF without Acrobat?

Yes. Word desktop and LibreOffice Writer can create form controls, but confirm that the final export contains interactive PDF fields.

Is a scanned PDF fillable?

Not automatically. A scan is an image; add form fields over it with a PDF form editor.

Should I use checkboxes or radio buttons?

Use checkboxes when multiple answers can be selected. Use radio buttons when exactly one answer is allowed.

Why should I test in more than one viewer?

PDF viewers differ in support for saving, validation, scripts, and advanced fields. Test where recipients will actually complete the form.