To use Word to create a fillable PDF, use Word for the wording and a separate AcroForm builder for the interactive controls, because the PDF itself—not the Word document—must contain the fillable fields. The Create Fillable PDF tool handles that second job: it builds a new form from blank A4 or US Letter pages, gives each control a visible label and internal field name, and produces a downloadable PDF with traditional AcroForm text boxes or checkboxes. A form can contain up to 30 fields. This is not a conversion of an existing Word export. The tool never opens or modifies an existing PDF, so you must transfer any needed wording and questions into the editor yourself. The result is suitable for a basic registration sheet, feedback form, consent checklist, intake page, or request form that starts from an empty layout. It is not a Word template converter, response-collection system, or full document-design application. Distribution, saving, and any later handling of completed files remain outside the browser builder. Recipients can complete the generated fields, save their copy, reopen it, and print it in a compatible PDF viewer. However, the generated file has no submit button, email action, server endpoint, or response database, so creating the form and collecting its answers are separate tasks.
There are two distinct stages in a Word-assisted workflow: preparing the content and adding interactive PDF controls. A Word-exported PDF can contain fixed text, tables, and lines, but it does not become a fillable AcroForm merely because it was exported. The browser builder instead creates the PDF structure and places the interactive fields on blank pages. That distinction explains why a Word draft can guide your field plan but cannot serve as an uploadable template for this particular tool.
Word's role in a fillable-PDF project
Word remains useful for drafting questions, consent language, response instructions, and other supporting copy. Keep the draft concise because this builder places a title and visible field labels on the generated pages; it does not reproduce paragraphs, tables, fonts, logos, or other formatting from a Word document. Decide which information needs an answer and which information can remain in an accompanying message.
| Task or need | Word PDF export | Create Fillable PDF |
|---|---|---|
| Start from a Word document | Can export a static PDF with the document layout | Cannot open, upload, inspect, or modify the exported PDF |
| Add true interactive fields | This tool cannot import a Word-exported PDF or add AcroForm fields to it | Creates text boxes and checkboxes from a blank page |
| Choose a page size | The document page setup determines the exported size | Choose A4 or US Letter when creating the form |
| Preserve an existing design | The exported PDF can retain the Word document's design | Uses a simple sequential layout without drag-and-drop positioning |
The practical choice depends on your starting material. If you need a new, uncomplicated form with a title, labels, and up to 30 controls, start with the browser builder. If you need to retain a detailed Word layout, add controls to an existing PDF, or reproduce a scanned document, this workflow is not the right fit.
Using Word to create a fillable PDF
- Draft the wording in Word. Open a blank Word document and type the questions or consent text you want recipients to see. A simple table can help you record each requested answer, its field type, and whether it should be required. If useful, choose File > Save As and select PDF (.pdf) for a static reference copy, but do not treat that export as a fillable template.
- Build a field plan. Decide where a recipient needs to type a response and where a checkbox is sufficient. Use text boxes for short written answers and checkboxes for yes-or-no choices or individual selections. Mark only genuinely necessary fields as required.
- Open the browser builder and define the blank document. Enter a form title and choose A4 or US Letter. Keep at least one field in the editor because a form cannot be generated without any fields.
- Add and configure the controls. Add up to 30 text boxes or checkboxes. Give every field a unique internal name, a visible label, and an optional required setting. Transfer only the wording that belongs in the title or labels; the Word draft itself will not carry over.
- Create and download the PDF. Generate the separate fillable PDF file and save it locally. The output uses conventional AcroForm fields that work with many desktop and browser PDF viewers, although you should confirm behavior in the exact viewer your recipients use.
- Complete the quality check. Open the downloaded file, enter test responses, save a copy, close it, reopen it, and print or preview the pages. This final check is part of creating a reliable form, not an optional finishing touch.
Field rules that keep the form valid
Plan the form within the builder's accepted limits before adding many fields. The title and visible labels use a built-in standard PDF font, which explains their printable English-character restriction.
| Setting | Accepted input | Limit or behavior |
|---|---|---|
| Form title | Printable English characters | Maximum 100 characters |
| Visible field label | Printable English characters | Maximum 100 characters; a required field also receives an asterisk |
| Internal field name | English letters, numbers, spaces, underscores, and hyphens | Maximum 64 characters and unique within the form |
| Field type | Text box or checkbox | At least 1 and no more than 30 fields in total |
| Page size | A4 or US Letter | The form starts from blank pages |
| Required option | Optional on or off setting | Sets the PDF field flag; viewer enforcement varies |
The checks reject blank values, control characters, unsupported characters, duplicate names that differ only by capitalization, and unsupported field types rather than silently changing the PDF structure. Internal names become part of that structure, so use stable, meaningful names and avoid changing them after another person begins maintaining the form.
How the finished pages are arranged
The generator lays out fields in the order shown in the editor. A text control spans the usable page width beneath its label, while a checkbox appears beside its label. When the current page no longer has safe vertical space, the generator adds another blank page and continues without dropping fields. The result summary reports the actual page and field counts, so confirm those values before distribution.
The layout is deliberately simple rather than fully design-controlled. It does not provide drag-and-drop coordinates, columns, logos, colors, custom fonts, branding, accessibility tagging, tab-order editing, or print-production controls. A long label can meet the input limit yet still be unsuitable for a particular page design, which is another reason to inspect the downloaded result. Changing the title, page size, field type, name, label, or required option clears the previous result so that an outdated download cannot be mistaken for the current configuration. Generating again replaces the prior temporary download URL, and leaving the page releases that URL.
Test the file in the recipient's viewer
- Open the PDF in the target viewer. Use the same desktop or browser PDF application that recipients will use rather than assuming every viewer behaves identically.
- Exercise every control. Type into every text box, toggle every checkbox in both directions, and check that labels are clear and fields are easy to identify.
- Save and reopen it. Save a completed copy, close the document, reopen the saved PDF, and confirm that the typed text and checkbox states remain in place.
- Print or preview every page. Check that labels and controls fit, continuation pages appear in the expected order, and no important content is clipped.
- Probe the required fields. Leave a required field empty and observe the viewer's response. Also confirm that ordinary users can navigate, save, and print the form without encountering an action the tool does not provide.
Some PDF viewers highlight required fields, some enforce them only during a submit action, and others provide little visible indication. The generated form has no built-in submit action, so the required option should be treated as PDF metadata rather than a guarantee that every viewer will block an incomplete form. Testing also confirms that the conventional AcroForm fields behave as expected for your audience.
Keep privacy and response handling in view
Generation and download happen locally in the browser using the installed pdf-lib library. Nothing is uploaded to Lizely, and the original data entered in the form builder remains in the current browser session. The generated PDF is downloaded as a separate file and does not connect to a response database.
The downloaded document is not encrypted, certified, signed, access-controlled, or connected to a server. Anyone who receives it may copy or alter it. Completed responses remain inside each recipient's saved PDF unless the recipient sends that file elsewhere. Do not rely on a blank local form as the sole secure collection system for passwords, payment card details, health records, identity documents, or other sensitive information. Use an appropriately secured service when submissions must be collected, authenticated, retained, audited, or deleted under a policy.
If a completed form must become a fixed, non-editable document, use Flatten PDF after it has been filled. If the document needs a drawn handwritten signature, use Sign PDF. The form builder itself does not create a digital signature field, JavaScript validation, calculations, or a server-side submission action.
Choose another workflow when the form needs more
- An existing PDF or scan: Use a professional PDF authoring application if you must preserve an existing design, place controls over an uploaded template, or turn detected lines into fields.
- Advanced controls: Use an authoring tool with dropdowns, radio groups, date pickers, signature fields, calculations, JavaScript validation, or a submit action.
- Brand or accessibility requirements: Recreate the form with control over columns, logos, colors, fonts, tagging, and tab order, then perform the relevant accessibility and compliance review.
- Regulated or high-risk collection: Use a secured form and response platform rather than an unprotected local PDF when identity, health, payment, retention, or audit rules apply.
For a straightforward form that starts from nothing, Word can help you draft the questions while the browser builder supplies the interactive PDF fields. Keep the draft focused, recreate only the necessary labels and controls, and complete the recipient-viewer test before sending the file.