Can respondents fill out these forms in standard web browsers?

Yes. Forms created with our tool strictly adhere to ISO 32000 AcroForm standards, allowing users to type, check boxes, and select dropdowns directly inside Google Chrome, Microsoft Edge, Safari, and Firefox.

Can I convert an existing non-fillable PDF into a fillable form?

Yes! Simply upload your existing static document (created in Word, InDesign, or Canva) into our builder and drag interactive form fields over the designated form lines and boxes.

How do radio button groups work?

To create mutually exclusive radio buttons, assign the exact same field name to all buttons in the group, but assign a different export value to each button. The reader will automatically ensure only one button is selected at a time.

Will entered form data be saved when users download or print the PDF?

Yes. Modern PDF readers allow users to save filled-in copies of AcroForms with their responses fully preserved for submission or archiving.

Can form data be exported to Excel or databases?

Yes. Because fields have standardized names and types, software like Adobe Acrobat or automated Python/Node.js scripts can extract all entered data into CSV, JSON, or XML formats.

Are my files uploaded or stored on your servers?

Never. All form building, coordinate calculations, and PDF file compilation occur 100% locally inside your web browser. No document data is ever sent across the network.

Can I set certain fields as mandatory or required?

Yes. Setting the 'Required' flag activates Bit 1 in the field flags (/Ff 1), instructing compliant readers to alert users if they attempt to submit or print the form with the field left blank.

Add Interactive Form Fields

In-Depth Technical Guide•8 min read•2RUN Engineering Team

100% Client-Side • Zero Upload

The Authoritative Guide to Creating Interactive PDF Forms In-Browser with ISO AcroForms

⚡How to Create an Interactive PDF Form In-Browser

1. Upload Your Base PDF Document

Drag and drop your static PDF into the visual form builder, or click Browse to load it from your local storage drive.

2. Choose Form Field Types

Select from text inputs, multiline text areas, checkboxes, radio button groups, or dropdown selection menus from the toolbar.

3. Drag, Drop, and Position Fields

Click and drag fields onto the visual page preview. Use corner handles to resize and snap fields to alignment guidelines.

4. Configure Field Properties

Assign unique field names, default values, required status, font sizes, and dropdown choices in the properties panel.

5. Export Interactive PDF Form

Click 'Download Form PDF' to compile standard AcroForm dictionaries and appearance streams, saving your fillable PDF instantly.

Interactive PDF forms are the digital backbone of modern administrative, legal, corporate, and healthcare operations. From patient intake questionnaires, employment applications, and lease agreements to vendor purchase orders, expense reports, and compliance checklists, fillable forms enable organizations to collect structured data accurately without the chaos of handwritten paperwork or illegible scans.

Under the ISO 32000 standard, interactive forms are governed by the AcroForm architecture. Creating a fully compliant, multi-platform fillable PDF requires far more than merely drawing input boxes on a page. It necessitates defining a formal /AcroForm catalog dictionary, establishing a structured field tree (/Fields), binding default graphic resources (/DR) and fonts (/Font), configuring appropriate field flags (/Ff) for multiline text or required inputs, and synthesizing standard Appearance Streams (/AP) with Default Appearance strings (/DA). Without strict adherence to these technical specifications, form fields frequently malfunction in web browsers, display broken font metrics, or fail to export data into enterprise database systems.

Our client-side Create PDF Form tool provides an intuitive, high-precision visual drag-and-drop builder directly within your browser. You can import any static PDF document, place text inputs, checkboxes, radio groups, and dropdown menus with sub-pixel alignment, and export fully compliant ISO 32000 AcroForms—all with 100% client-side privacy and zero server data transmission.

Read the full technical guide

The ISO 32000 AcroForm Architecture: Catalog and Field Hierarchy

Under ISO 32000-1 Section 12.7, an interactive form is maintained at the root document level within the Catalog dictionary under the /AcroForm key. The /AcroForm dictionary serves as the master controller for all interactive fields across the entire document, defining global attributes such as:

1. /Fields: An array of indirect references pointing to the root terminal and non-terminal field dictionaries.

2. /DR (Default Resources): A resource dictionary containing font references (such as /Helv for standard Helvetica or ZapfDingbats for checkmarks) and color spaces required to render field values dynamically.

3. /DA (Default Appearance): A string containing default typographic operators (e.g., '/Helv 12 Tf 0 g') that instruct reader engines how to style newly entered text.

4. /NeedAppearances: A boolean flag that requests viewing applications to synthesize visual appearance streams on the fly if pre-compiled appearance streams are absent.

Each interactive field is simultaneously represented on its target page as a /Widget annotation within the page's /Annots array. This dual architecture binds the logical data model of the form field directly to its physical on-page visual geometry.

AcroForm Field Types (/FT) and Field Flags (/Ff)

The ISO 32000 standard defines four primary field types via the /FT key, each supporting specialized operational behaviors:

1. Text Fields (/FT /Tx): Single-line or multiline inputs for names, addresses, and narrative descriptions. Setting Bit 13 in the field flags (/Ff 4096) enables multiline wrapping, while Bit 14 (/Ff 8192) masks entered characters for password fields.

2. Button Fields (/FT /Btn): Encompasses push buttons, checkboxes, and mutually exclusive radio button groups. Checkboxes toggle between an '/Off' state and a custom export state (e.g., '/Yes'), while radio button groups share a common parent field name where only a single child widget can be active at any time.

3. Choice Fields (/FT /Ch): Includes combo boxes (dropdown menus) and scrollable list boxes. Setting Bit 18 (/Ff 131072) transforms a dropdown into an editable combo box where users can type custom entries in addition to selecting pre-defined options (/Opt).

4. Signature Fields (/FT /Sig): Designated placeholders for cryptographic digital signatures and approval timestamps.

Visual Drag-and-Drop Designer and Coordinate Precision

Our visual form builder bridges the gap between modern browser UI interactions and low-level PDF coordinate geometry. When you drag a text field or checkbox onto the document preview canvas, the interface captures screen coordinates in pixels and transforms them into 72-point PDF user units relative to the page's /MediaBox or /CropBox.

The engine accounts for high-DPI displays (window.devicePixelRatio), canvas zoom scaling, and page rotation angles (0, 90, 180, 270 degrees). It automatically generates the exact bounding rectangle array [xMin yMin xMax yMax] required by the field's /Rect key. Bounding boxes are snapped to an optional layout grid, allowing creators to align form columns, tabular rows, and signature lines with millimeter precision.

Logical Tab Order and WCAG 2.4.3 Accessibility in Form Navigation

A common complaint with amateur PDF forms is erratic tab navigation: pressing the Tab key causes the cursor to jump randomly across the page instead of moving down the column. Under WCAG 2.1 Success Criterion 2.4.3 (Focus Order), forms must provide a predictable, sequential tab order.

In PDF architecture, tab traversal is dictated by the /Tabs key on each /Page dictionary (/Tabs /S for structure order, /Tabs /R for column order, or array order in /Annots). Our visual builder allows authors to drag and reorder fields in a visual tab index drawer, automatically sequencing the /Fields array and setting /Tabs /A (array order). Keyboard-only users and assistive screen reader technologies can navigate from field to field seamlessly in logical reading sequence.

Appearance Stream Synthesis: Eliminating Cross-Platform Display Bugs

One of the most notorious defects in amateur PDF form tools is reliance on the /NeedAppearances flag without generating pre-compiled Appearance Streams (/AP). While desktop Adobe Acrobat can synthesize field appearances on the fly, modern mobile readers (Apple iOS Files, Android PDF Viewer) and embedded browser engines (Chrome, Edge, Safari) frequently ignore /NeedAppearances, resulting in blank form fields or uncheckable boxes.

Our client-side builder synthesizes full Normal Appearance streams (/AP << /N streamRef >>) for every field. For checkboxes, it compiles vector appearance states for both the checked ('/Yes') and unchecked ('/Off') conditions using compliant ZapfDingbats checkmarks or vector check paths. This guarantees that your forms render flawlessly and respond interactively across all hardware and software platforms.

100% Client-Side Privacy for Proprietary Business Forms

Designing corporate intake forms, patient registration templates, or proprietary legal contracts often involves sensitive organizational structures, draft legal clauses, and proprietary business logic. Transmitting these draft templates to cloud-based PDF conversion portals creates avoidable data leak risks and regulatory compliance headaches.

Our Create PDF Form tool operates 100% client-side inside your web browser. Utilizing WebAssembly and pdf-lib, the base PDF is parsed, AcroForm dictionary trees are constructed, and binary streams are assembled directly in your computer's RAM. Your documents never leave your device, ensuring complete enterprise confidentiality.

💡Pro Tips for Professional PDF Form Design

•Assign descriptive, unique names to every field (e.g., 'Client_FirstName' instead of 'Text1') to ensure smooth automated data extraction into CSV or databases.
•Set standard font sizes (such as 10pt or 12pt) rather than auto-sizing for single-line text inputs to maintain typographic consistency across fields.
•For multi-line comment boxes, always enable the 'Multiline' flag to allow automatic text wrapping as respondents type long answers.
•Test your exported form in both a desktop reader (Acrobat) and a mobile browser to verify that dropdowns and radio buttons respond intuitively.

🛡️Low-Level AcroForm Synthesis and Widget Annotation Binding

When exporting, our engine checks the document Catalog for an existing /AcroForm dictionary, creating one if absent with standard /DR font resources. For each placed field, it instantiates an indirect dictionary specifying /FT (field type), /T (field title string), /Ff (bitmask flags), /DA (default appearance), and /Rect (page coordinates). It links this dictionary into the document /AcroForm /Fields array and simultaneously appends the field reference into the target page's /Annots array as a /Widget annotation. Full normal appearance streams (/AP /N) are synthesized for each initial state, ensuring universal display.

Stack: WebAssembly • Multi-threaded Web Workers • HTML5 Canvas API

Privacy: Files never leave your device or touch a cloud buffer; analytics run only with your consent.