What does "interactive PDF" actually mean?

It means a PDF that the reader can do something with on screen, not just read — type into fields, tick boxes, pick from menus, press buttons, and follow links — using interactive objects the PDF format supports natively. The most common form of interactivity is a fillable form built from AcroForm fields: text boxes, checkboxes, radio buttons, dropdowns, and list boxes. Beyond fields there are push buttons that perform actions (submit the data, reset the form, print, or jump somewhere), automatic calculations and input validation, and navigational links and bookmarks. So "interactive" spans a range from a simple fill-in form to a document with calculating fields and submit buttons. The key thing to understand up front is that not all of these work everywhere — the basics are universal, the advanced behaviours depend on the viewer.

What field types can I add, and what is each for?

There are a handful of standard field types, each suited to a kind of input. Text fields capture free text such as a name, address, or comment, and can be single-line or multi-line. Checkboxes are for independent yes/no options where any number can be ticked. Radio buttons are for mutually exclusive choices — group them and only one can be selected. Dropdowns (combo boxes) and list boxes let the reader pick from a predefined set of options, which keeps answers consistent and saves typing. Choosing the right type matters for both usability and clean data: use radio buttons (not checkboxes) when exactly one answer is allowed, and dropdowns when the valid options are known in advance. These field types are universally supported, so a form built from them works in essentially any PDF viewer.

How do buttons and calculations work in a PDF?

Buttons are fields configured to perform an action when clicked, and calculations are field properties that compute a value automatically. A push button can submit the form data to a destination, reset all fields, print the document, or navigate — for example to a web link or another page. Calculations let a field derive its value from others (summing line items into a total, say) and validation can check or format what a user types. The important caveat is that calculations, validation, and many button actions are driven by the PDF’s JavaScript layer, and JavaScript support varies enormously between viewers — full in desktop Acrobat-class readers, partial or absent in many browser and mobile viewers. So buttons that just navigate or reset are fairly safe, while anything relying on scripted calculation should be treated as an enhancement, not something every reader will get.

Why do my interactive features work in one viewer but not another?

Because PDF viewers implement very different subsets of the interactivity spec. Basic AcroForm fields — text, checkbox, radio, dropdown — are supported almost everywhere, so a plain fillable form is safe. But scripted behaviour (auto-calculation, validation, dynamic show/hide) relies on a JavaScript engine that many lightweight, browser-built-in, and mobile viewers simply do not run, so those features silently do nothing there. Worse, the old XFA forms (a now-deprecated dynamic-form technology) are unsupported in most modern viewers and should be avoided entirely. The practical rule is to design for the lowest common denominator: build with standard AcroForm fields, treat JavaScript-driven calculations as a nice-to-have with a manual fallback, and always test your form in the viewers your audience actually uses before relying on it.

How do I make sure a completed form cannot be changed?

Flatten it. While a form is interactive, its fields remain editable — which is what you want during filling, but not once it is signed off or submitted, since anyone could alter the entries. Flattening merges the field values into the page as static content, so the answers become a permanent, non-editable part of the document while still looking identical. Flatten when you want to lock a completed form for the record, archive a final version, or send a copy that should not be tampered with. Keep an unflattened master if you will need to edit it again. The pattern is: interactive while in use, flattened when final — which gives you both easy completion and a tamper-resistant result.

Is it safe to build interactive PDFs with an online tool?

Prefer a tool that runs on your own device, since forms often collect or contain personal data. Many online form tools upload your file to a third-party server to process it, which is a poor fit for documents meant to gather names, addresses, or other personal information. Client-side (in-browser) tools build, fill, and flatten forms locally so the file never leaves your computer — ScoutMyTool’s PDF tools work this way. For any form handling personal data, confirm the tool is client-side before uploading, or use offline software, and remember that a submit button sending data somewhere is itself a data-handling decision worth checking.

7 min read

How to make a PDF interactive — form fields and buttons

By ScoutMyTool Editorial Team · Last updated: 2026-05-21

The first interactive PDF I built had a beautiful self-calculating total — and it worked perfectly on my machine and did absolutely nothing on half the phones my colleagues opened it on. That was my introduction to the real subject of interactive PDFs: not just what you can add, but what will actually run where your readers open it. PDFs can hold a rich set of interactive elements — typed fields, checkboxes, dropdowns, buttons that submit or calculate, links that navigate — and used well they turn a static page into something people fill in and act on. This guide walks through the full palette, what each element is for, and the viewer-support reality that separates the features that always work from the ones that sometimes do not.

The interactive palette

Element	Purpose	Viewer support
Text field	Free-text entry (name, notes)	Universal
Checkbox	Independent yes/no choices	Universal
Radio button	Pick one from a group	Universal
Dropdown / list box	Choose from defined options	Universal
Push button	Submit, reset, print, or navigate	Good (submit needs a destination)
Calculation / validation	Auto-total, format, check input	Viewer-dependent (uses JavaScript)
Links & bookmarks	Jump within or out of the document	Universal for links

Step by step — build an interactive PDF

Start from a clean layout. Lay out the page first, then add interactive fields on top — a tidy underlying design makes field placement and alignment far easier.
Add the right field type for each input. Text for free entry, checkboxes for independent options, radio buttons for one-of-many, dropdowns/list boxes for fixed choices — choose for both usability and clean data.
Add buttons for actions. A reset button, a print button, navigation links, or a submit button to a destination — keep critical flows to actions that do not depend on scripting.
Add calculations as an enhancement, with a fallback. If you use JavaScript-driven totals or validation, make sure the form is still usable when that scripting does not run.
Test in your audience’s viewers. Open the form in desktop, browser, and mobile readers your users actually use; confirm fields, buttons, and any calculations behave (or degrade gracefully).
Flatten the finished copy. When a form is completed and final, flatten it so the entries become permanent and tamper-resistant, keeping an unflattened master for future edits.

The principle: design for the lowest common denominator

Interactive PDFs reward a "build for where it will be opened" mindset. Standard AcroForm fields — text, checkbox, radio, dropdown — and simple buttons and links are supported almost everywhere, so a form built on them works for everyone. The advanced layer — JavaScript calculations, validation, dynamic behaviour, and especially the deprecated XFA forms — works inconsistently or not at all in many browser and mobile viewers, which is exactly where a lot of people will open your file. The fix is not to avoid the rich features but to treat them as progressive enhancement: the form must be fully usable with the universal elements, and the scripted niceties improve the experience where they run. Design that way, test in real viewers, and flatten when final — and your interactive PDF works for the reader on the old phone as well as the one in desktop Acrobat.

FAQ

What does "interactive PDF" actually mean?: It means a PDF that the reader can do something with on screen, not just read — type into fields, tick boxes, pick from menus, press buttons, and follow links — using interactive objects the PDF format supports natively. The most common form of interactivity is a fillable form built from AcroForm fields: text boxes, checkboxes, radio buttons, dropdowns, and list boxes. Beyond fields there are push buttons that perform actions (submit the data, reset the form, print, or jump somewhere), automatic calculations and input validation, and navigational links and bookmarks. So "interactive" spans a range from a simple fill-in form to a document with calculating fields and submit buttons. The key thing to understand up front is that not all of these work everywhere — the basics are universal, the advanced behaviours depend on the viewer.
What field types can I add, and what is each for?: There are a handful of standard field types, each suited to a kind of input. Text fields capture free text such as a name, address, or comment, and can be single-line or multi-line. Checkboxes are for independent yes/no options where any number can be ticked. Radio buttons are for mutually exclusive choices — group them and only one can be selected. Dropdowns (combo boxes) and list boxes let the reader pick from a predefined set of options, which keeps answers consistent and saves typing. Choosing the right type matters for both usability and clean data: use radio buttons (not checkboxes) when exactly one answer is allowed, and dropdowns when the valid options are known in advance. These field types are universally supported, so a form built from them works in essentially any PDF viewer.
How do buttons and calculations work in a PDF?: Buttons are fields configured to perform an action when clicked, and calculations are field properties that compute a value automatically. A push button can submit the form data to a destination, reset all fields, print the document, or navigate — for example to a web link or another page. Calculations let a field derive its value from others (summing line items into a total, say) and validation can check or format what a user types. The important caveat is that calculations, validation, and many button actions are driven by the PDF’s JavaScript layer, and JavaScript support varies enormously between viewers — full in desktop Acrobat-class readers, partial or absent in many browser and mobile viewers. So buttons that just navigate or reset are fairly safe, while anything relying on scripted calculation should be treated as an enhancement, not something every reader will get.
Why do my interactive features work in one viewer but not another?: Because PDF viewers implement very different subsets of the interactivity spec. Basic AcroForm fields — text, checkbox, radio, dropdown — are supported almost everywhere, so a plain fillable form is safe. But scripted behaviour (auto-calculation, validation, dynamic show/hide) relies on a JavaScript engine that many lightweight, browser-built-in, and mobile viewers simply do not run, so those features silently do nothing there. Worse, the old XFA forms (a now-deprecated dynamic-form technology) are unsupported in most modern viewers and should be avoided entirely. The practical rule is to design for the lowest common denominator: build with standard AcroForm fields, treat JavaScript-driven calculations as a nice-to-have with a manual fallback, and always test your form in the viewers your audience actually uses before relying on it.
How do I make sure a completed form cannot be changed?: Flatten it. While a form is interactive, its fields remain editable — which is what you want during filling, but not once it is signed off or submitted, since anyone could alter the entries. Flattening merges the field values into the page as static content, so the answers become a permanent, non-editable part of the document while still looking identical. Flatten when you want to lock a completed form for the record, archive a final version, or send a copy that should not be tampered with. Keep an unflattened master if you will need to edit it again. The pattern is: interactive while in use, flattened when final — which gives you both easy completion and a tamper-resistant result.
Is it safe to build interactive PDFs with an online tool?: Prefer a tool that runs on your own device, since forms often collect or contain personal data. Many online form tools upload your file to a third-party server to process it, which is a poor fit for documents meant to gather names, addresses, or other personal information. Client-side (in-browser) tools build, fill, and flatten forms locally so the file never leaves your computer — ScoutMyTool’s PDF tools work this way. For any form handling personal data, confirm the tool is client-side before uploading, or use offline software, and remember that a submit button sending data somewhere is itself a data-handling decision worth checking.

Citations

Build and fill interactive PDFs — in your browser

Create fillable fields, fill forms, and flatten the finished copy with ScoutMyTool — client-side, so a form full of personal data never leaves your computer.

Open the fillable-form builder →