How does browser form filling read and order AcroForm fields?
Browser form filling inspects the PDF’s /AcroForm field tree inside a Web Worker, extracts each widget’s position and tooltip label, and renders clean HTML controls in reading order with 0 bytes sent over the network. Tax forms, onboarding packets, and medical questionnaires stay strictly inside your browser’s memory.
Sorting fields in reading order across rotated pages
PDF forms do not always store fields in visual top-to-bottom order. The parser locates each widget’s page reference (falling back to the page’s /Annots array when /P is omitted) and computes its vertical position relative to the visible page box across 0, 90, 180, and 270 degree page rotations.
Grouping fields under Page 1, Page 2, and so on lets you tab through long multi-page contracts cleanly without hunting around a zoomed-out canvas. If you are starting from a static document that lacks interactive boxes altogether, you can turn static PDF pages into interactive forms first.
Reading tooltip labels and respecting read-only locks
For every field, the reader checks the /TU tooltip entry documented in the Library of Congress PDF 1.7 Format Description to build a human-readable label. When /TU is missing, it cleans up the internal field name by splitting camelCase and stripping array indices like [0].
Fields flagged as readOnly appear disabled in the grid and are skipped when writing values back, ensuring pre-populated case numbers or calculated totals remain untouched. Your sensitive tax or personal data stays secure inside your local browser tab throughout editing.
Supported interactive field types and input limits
Every AcroForm widget maps to a native browser input so keyboard navigation, screen readers, and mobile touch targets work reliably. The table below lists how each PDF field class behaves during reading and saving.
| PDF field class | Browser control | Behavior and limits |
|---|---|---|
PDFTextField (single-line) |
Text input | Enforces maxLength if defined in field |
PDFTextField (multiline) |
Expandable textarea | Preserves line breaks and maxLength |
PDFCheckBox |
Checkbox toggle | Reads and writes checked boolean state |
PDFRadioGroup |
Radio button group | Selects one option or clears group |
PDFDropdown |
Select menu | Picks one item from field options |
PDFOptionList |
Multi-select checkboxes | Allows toggling multiple list entries |
Push buttons and cryptographic signature widgets are intentionally left out of the form grid because they do not store typed text values. All file bytes stay local via the MDN File API Documentation, and the Filled in sidebar counter tracks how many editable fields have values.
If you need to place freeform text outside existing form boxes, open the document in our browser PDF editor to type anywhere on the page.
Why do some PDFs show no fillable fields?
When a PDF reports zero fillable fields, the page contains flat printed lines or scanned pixels rather than interactive /AcroForm widget objects. Even when a form looks like a structured table with blank boxes, a PDF viewer cannot generate typed inputs unless those boxes were authored as form fields.
Distinguishing flat scans and XFA forms from AcroForms
Standard interactive PDFs use AcroForm dictionaries defined in the PDF Association ISO 32000-2 Specification. By contrast, PDF 2.0 formally deprecated Adobe’s proprietary XML Forms Architecture (XFA), which embeds an XML template instead of native PDF widgets and fails to render in most modern browsers.
Scanned paper forms and exported Word tables also lack AcroForm dictionaries, which is why the tool displays an inline notice instead of an empty form grid.
Adding text or signatures to non-interactive documents
When a form has no interactive fields, you can still complete it in your browser without printing and scanning. Use the direct links in the notice to add running text or apply a handwritten or typed signature right on top of the flat page layout.
Locking answers and flattening completed forms before sharing
Leaving form fields editable after submission allows recipients or automated email previews to alter values or display blank boxes in lightweight mobile viewers. Locking your answers bakes the filled text and checkmarks directly into the page content stream.
Using the Lock the answers checkbox before download
Check Lock the answers in the options sidebar before clicking Save filled PDF to run form.flatten() during save. Flattening draws each field’s appearance onto the page and removes interactive widget inputs, so the document renders identically across every desktop and mobile viewer.
Tip: Keep an unlocked copy if you plan to update dates or figures later, because flattening permanently converts interactive fields into static page graphics.
If you receive an already-filled PDF from someone else and need to freeze both its form fields and markup comments together, use our dedicated tool to lock interactive form fields and annotations.
Handling fonts, character limits, and post-fill signing
Completed files conform to the IETF RFC 8118 PDF Media Type (application/pdf) for universal archiving and email attachment. If your form’s embedded font rejects non-Latin characters or emoji, replace them with standard Latin letters, numbers, and punctuation before saving, then hand off directly to signing or merging from the result panel. Flattening before emailing also prevents form fields from appearing blank in mobile preview panes that omit interactive AcroForm rendering.