Fill PDF Form Online - Complete AcroForm Fields Free

An online PDF form filler completes interactive AcroForm fields inside a PDF without desktop Acrobat. Tax forms, HR onboarding packets, rental applications, and government PDFs ship with text boxes and checkboxes wired to a form dictionary. This page uses pdf-lib getForm() to read that dictionary in your browser, renders inputs for supported field types, writes your answers with setText, check, or select, and optionally flatten() to bake values into static page content.

Processing is browser-only via helpers from @/lib/pdf-io: validatePdfUpload enforces the 50 MB cap, getPdfPageCount confirms readability, and fileFromBytes packages the download. Nothing is uploaded to a server - suitable for tax IDs, SSN fields, and HR data subject to your device policy.

We are honest about limits: text fields and checkboxes work fully; radio groups appear as dropdowns with partial support; dropdowns, list boxes, signature fields, and button actions are skipped; encrypted PDFs fail without a password prompt; XFA-only legacy forms (some government templates) are not AcroForm and will not scan. Filling forms is not the same as signing - use PDF sign for visual signature overlays after fields are complete.

Flattening is optional but important for submissions. When checked, pdf-lib form.flatten() burns values into page content and removes widgets so recipients cannot edit answers. Leave flatten off when a second party must complete remaining fields in Acrobat or Chrome. Flatten is irreversible - keep the original blank PDF if you might need to change answers.

Most fillable forms take three to five minutes depending on field count. Verify field detection before typing sensitive data.

1. Upload a fillable PDF - Drag and drop or browse. validatePdfUpload enforces PDF type and 50 MB. pdf-lib getForm() scans for AcroForm fields. Flat scanned images without interactive widgets show zero fields - that PDF is not fillable here.
2. Review detected fields - Text fields become inputs; checkboxes toggle on/off. Radio groups may show as dropdowns with partial support. Field names match internal AcroForm names (often verbose like topmostSubform[0].Page1[0].f1_1[0]) - match labels on the PDF visually.
3. Enter your answers - Type into text inputs and check boxes. Tab through fields in DOM order. No JavaScript calculations from the original form run in-browser - totals you see in Acrobat may not auto-update here.
4. Choose flatten option - Check Flatten form after filling to lock answers into page content for submission; leave off if someone else must complete remaining fields.
5. Fill and download - Click Fill PDF Form. pdf-lib writes values, optionally flattens, and saves locally. Download adds a processed copy; your original upload stays untouched.

A freelancer receives a W-9 tax form PDF from a new client. The file has AcroForm text boxes for legal name and business name plus a checkbox for exempt payee status. They need to return a completed copy tonight without installing Acrobat or uploading tax identifiers to a random cloud form filler.

Workflow on this page: upload the IRS-style PDF, confirm text and checkbox fields appear in the list (if zero fields, the PDF is flat or XFA-only), type the legal name and business name, check Exempt payee if applicable, enable flatten so accounting cannot accidentally edit the TIN field later, click Fill PDF Form, download, and open in Chrome to verify appearances. If a radio group for LLC classification appears as a dropdown, pick the option and verify visually - radio support is partial by design. Add a visual signature on PDF sign only if the form needs an ink-style overlay beyond AcroForm fields.

This page targets standard AcroForm widgets. Exotic field types and legacy XFA forms need desktop Acrobat or specialized tools. Visual signing is a separate workflow.

When getForm().getFields() returns an empty list, the PDF is not fillable in the AcroForm sense. Scanned paper is a flat image. When field count is high but dropdowns are missing, expect to finish unsupported widgets in Acrobat. Browser-only processing and 50 MB cap apply regardless of field type.

These are the failures the UI surfaces on purpose, plus jobs this page will not pretend to do.

• No fields detected. The PDF is likely a flat scan or XFA-only form, not AcroForm. getForm().getFields() returns zero widgets. Add fields in a desktop editor or request an interactive export from the form issuer.
• Encrypted PDF. pdf-lib cannot decrypt without a password prompt on this page. Open in a desktop reader, print or export an unencrypted copy, then upload here.
• Radio groups look wrong. Custom appearances vary by template; verify in Adobe Reader or Chrome after download. Partial support is intentional - we do not claim full parity with Acrobat for every radio layout.
• Flatten is irreversible. Keep the original blank PDF if edits may be needed. Flattened files have no editable widgets.
• 50 MB cap. Oversized forms are rejected by validatePdfUpload before getForm() runs. Compress externally or split attachments if the government template embeds large fonts.
• Field names are opaque. AcroForm internal names display as-is in the UI. Match labels on the PDF visually rather than expecting friendly names like first_name.
• Dropdowns and list boxes skipped. PDFDropdown and PDFOptionList widgets do not render inputs. Complete those fields in Acrobat or ask for a template revision.
• JavaScript not executed. Auto-calculated totals, date formatting scripts, and show/hide logic from the original form do not run in-browser. Enter final values manually.
• Memory on huge files. Files near 50 MB may spike RAM during save and flatten. Close other tabs if the browser warns about memory.

Form filling runs entirely in your browser. pdf-lib loads the PDF from memory, reads fields with getForm(), applies your inputs, and saves locally. Your document bytes are never POSTed to an API, never written to server logs, and never indexed. Suitable for tax identifiers, SSN fields, and HR data when local processing is required by policy. Clear downloads from shared machines after use.

We do not persist uploads or field values in localStorage. Closing the tab discards in-memory state except any file you explicitly downloaded. No account means no cross-device history. Sensitive answers exist only in the PDF you save - treat downloaded files like any other confidential document on your filesystem.