A fillable PDF carries an invisible layer most people never see directly: the AcroForm, a structured list of named fields sitting on top of the visible page content. A form's printed labels tell a human what to type where, but the actual field names, which are what a script, an e-signature platform or a data pipeline reads, often look nothing like the labels and are sometimes inconsistent or duplicated in ways that only become obvious once you look at the underlying structure.
Nothing is uploaded to check this. The document is parsed entirely inside your browser using a PDF library that runs on your own device, so a form containing a client's partially filled in personal details never has to leave your machine just to be inspected.
Running a pdf form field viewer before a form goes out for signatures
This is useful whenever the actual field names in a document matter more than its visible labels. Preparing a template for an automated document generation pipeline, debugging why a pre-fill script is writing values into the wrong boxes, or confirming a form vendor delivered every field a contract specified are all situations where you need to see the field structure directly rather than trust the printed form.
It is also the fastest way to check whether a PDF is a real fillable form at all. Plenty of documents look like forms, with boxes and underlines printed on the page, but have no actual AcroForm fields behind them, which means no field can be filled in programmatically and no data can be extracted from it later.
- Use a pdf form field viewer to confirm a template has the exact fields an automation pipeline expects.
- View pdf form fields to debug a pre-fill script that is writing values into the wrong boxes.
- Check fillable pdf fields before trusting that a document can be completed programmatically.
- Run an acroform field inspector pass on a vendor supplied template before accepting delivery.
- Confirm a scanned looking document has no real form fields behind its printed boxes.
Reading field types and values
Each field is shown with its type, since a PDF form supports several distinct kinds of field and each behaves differently. Text fields hold typed characters, checkboxes hold a checked or unchecked state, radio groups hold a single selection from a named set of options, dropdowns and list boxes hold one or more selected options from a list, and buttons and signature fields typically hold no simple value at all.
The current value shown is exactly what is stored in the file right now, which matters when checking whether a form template was distributed blank or whether a partially completed copy is being inspected by mistake. A dropdown or radio group also lists its full set of available options, not just whichever one is currently selected, which is useful for confirming the choices a form actually offers.
Field names versus visible labels
The name shown for each field is its internal identifier, the string a script or an e-signature integration uses to target it, and it is frequently different from the text printed next to the field on the page. A box labelled Full Name on screen might internally be named something like topmost_subform.page1.name_field, especially in forms exported from certain enterprise authoring tools.
Seeing this mismatch directly is often the fastest way to understand why an automated fill script is not working as expected, since the script has to reference the internal name, not the label a person reads.
What this tool does not do
This is a read only inspector. It does not fill in values, does not save changes back to the file and does not flatten the form. If the goal is to actually complete a form and produce a filled copy, this tool is the diagnostic step before that, not a replacement for a form filling tool.
A checkbox is not read the same way as a text field
A PDF document library running entirely inside your browser tab opens the file and reads its AcroForm dictionary, walking every field it defines to collect each one's internal name, its field type and its current value or selection. None of that requires rendering the visual page content, which is why even a form with dozens of fields lists in well under a second.
Because the parsing happens locally, there is no upload wait and no size limit beyond what your device's memory can hold. Walking a field dictionary is a lightweight structural read rather than a rendering pass, which is why a form with dozens of fields, some holding a client's personal details, lists in well under a second without ever being handed to anything outside the tab.
How to view PDF form fields
- 1
Open your PDF
Drag a PDF onto the drop area or click to browse. The form is parsed immediately.
- 2
Review the field list
Scan each field's name, type and current value in the table that appears.
- 3
Check the options on choice fields
Expand a dropdown or radio group entry to see the full set of options it offers.
- 4
Copy the list if needed
Copy the field list as text to paste into a script, a spreadsheet or a bug report.
Related tools worth bookmarking
Sources and further reading
Frequently asked questions
Common questions about the pdf form field viewer.
No. A PDF library walks the AcroForm dictionary field by field, reading each one's internal name, its field type and its current value directly from the parsed document object in memory. A client's partially completed intake form is inspected the same way a script would read it internally, without any of those field values ever being packaged into a request.
Some documents that look like forms, with visible boxes and underlines printed on the page, have no actual AcroForm structure behind them. Only a genuine fillable PDF, created or exported with form fields explicitly added, will list any entries here.
No. This is a read only viewer intended to let you inspect an existing form's structure quickly. Filling in values or saving a completed copy requires a dedicated PDF form filling tool.
The name shown is the field's internal identifier, used by scripts and automated systems, while the label is separate text drawn on the page for a human reader. Forms exported from certain authoring tools often generate internal names that bear little resemblance to their visible labels.
Text fields, checkboxes, radio groups, dropdowns, list boxes, buttons and signature fields are all recognised and labelled by type, with the available options listed for any field that offers a set of choices rather than free text entry.
No fixed limit is imposed by the tool. The practical ceiling is the memory available in your browser tab, which comfortably handles forms with hundreds of fields, since listing field names and values is a lightweight operation compared with rendering page content.
Yes. Drop the file onto this page and the table populates immediately with every field, its type and its current value, which is faster than opening a full desktop PDF editor just to check a form's structure.