Bluebeam Revu adds fillable fields to any PDF by switching the document into Edit Form mode, right-clicking a page, and selecting the field type from the right-hand panel. Revu remains the most recognized desktop application for turning static PDFs into fillable forms, and its Forms mode can scan a PDF and detect existing form-field shapes that already conform to the AcroForm layer. Construction, engineering, and architecture teams rely on it because markup, measurement, and form editing share the same interface. The same AcroForm output Revu produces can also be generated without installing the software. A browser-based form builder creates the same fillable files — text boxes, checkboxes, the PDF required flag, and printable labels — and is useful when no Revu license is available, when the form is small enough not to need a full authoring program, or when the document should start from a blank page rather than from an existing scanned template. The rest of this article walks through the exact Revu steps first, then shows how to produce a compatible file in your browser without uploading anything.
The Bluebeam Revu fillable form workflow
Bluebeam Revu organizes form creation under a dedicated Forms mode, which keeps the rest of the markup tools out of the way while you build fields. The standard workflow a Revu user follows looks like this:
- Open the PDF you want to make fillable in Revu, or open a blank PDF you have already prepared at the page size you want.
- Switch to Forms mode from the toolbar so the right-hand panel switches to form-field options instead of markups.
- If the PDF already contains form fields, Revu can scan the document and highlight shapes that match the form layer; right-click any highlighted shape to convert it into a usable field.
- To add a new field, right-click and pick the field type — text box or checkbox — from the context menu, then drag on the page to draw it.
- Configure each field in the right-hand panel: give it a name that the underlying PDF structure will use, set the visible label, and toggle the required flag if a recipient must complete it before submission.
- Save the PDF locally and open it in a viewer to confirm the fields respond to clicks and typed input.
These steps match how Revu is typically described in vendor tutorials and customer write-ups. The end result is a regular AcroForm PDF that any compliant viewer can open and fill.
Where Revu stops being the right tool
Revu's strength is also its weight: the program is paid, oriented toward Windows desktops, and aimed at professionals who already live inside its markup and measurement tools. Several recurring situations push users toward a lighter alternative:
- A one-off registration sheet, consent checklist, or feedback form that does not justify installing a full Revu license.
- A team that needs to share a quick fillable file on a Mac, on a Chromebook, or on a computer where Revu is not available.
- A blank starting layout — no existing PDF to scan — where converting an existing document is unnecessary.
- A user who needs to produce a file locally and does not want to upload form text, labels, or field names to any server.
In each case, a browser-based AcroForm builder is enough. It cannot replicate Revu's markup review, dynamic stamps, or measurement tools, and it does not try to. Its purpose is the narrower one of producing a valid fillable PDF that opens the same way a Revu export would.
Build the same AcroForm in your browser
When the goal is "a small fillable PDF I can email today," the browser path takes three short stages. The tool used here is Create Fillable PDF, which runs entirely inside the browser using the open-source pdf-lib library.
- Enter a form title — for example, "Volunteer Registration" — pick A4 or US Letter for the page size, and keep at least one field in the editor before generating. The title is what the recipient sees in their viewer's window title bar.
- Add between one and thirty fields. For each field, choose text box or checkbox, type a unique internal name (letters, numbers, spaces, underscores, or hyphens, up to 64 characters), type a visible label up to 100 characters, and tick the required flag if the recipient must complete it.
- Click Create, save the resulting PDF, and open it in the same viewer your recipients will use. Type into every text field, toggle every checkbox, save a copy, close and reopen the file, and print one page to confirm the layout holds.
That last stage — testing in the actual viewer — is the one Bluebeam users sometimes skip, and it is the one that prevents most field-related complaints. Different PDF viewers display the required flag differently: some highlight required fields, some only enforce them during a submit action, and some provide no visible indication at all. The downloaded file is built around the conventional AcroForm model that the pdf-lib PDFForm API exposes, so the file behaves like a standard export from any compliant form tool. For a deeper AcroForm walkthrough with field layout examples, see Build a Simple AcroForm PDF With Text Boxes and Checkboxes.
Field types, labels, and the required flag
The browser builder intentionally supports a narrow set of controls so the output stays predictable. The table below summarizes what is and is not available on each path.
| Capability | Create Fillable PDF (browser) | Bluebeam Revu Forms mode |
|---|---|---|
| Text box field | Yes | Yes |
| Checkbox field | Yes | Yes |
| Required flag | Yes (asterisk added to label) | Yes |
| Dropdown or radio group | No | Yes |
| Digital signature field | No | Yes |
| Submit button or email action | No | Yes |
| JavaScript calculation | No | Yes |
| Adds fields to an existing PDF | No — starts blank | Yes — opens and edits |
| Auto-detect form shapes on a scan | No | Yes |
The browser path is therefore the better fit for short, simple forms, while Revu remains the right tool for documents that already exist as PDFs, that need richer controls, or that have to ship with calculations, signatures, or a submit endpoint.
A second table is useful for limits, because both tools fail gracefully when those limits are reached:
| Limit | Create Fillable PDF |
|---|---|
| Minimum fields | 1 |
| Maximum fields | 30 |
| Page size | A4 or US Letter |
| Internal field name | Letters, numbers, spaces, underscores, hyphens; up to 64 characters; must be unique |
| Visible label | Printable English characters; up to 100 characters |
| Pages | Automatically extended when the field list overflows one page |
| File encryption | None — the PDF is not password-protected |
Test the downloaded file in the recipient's viewer
A fillable PDF is only as useful as the viewer it lands in. Before sending the file to anyone, open it in the exact program or browser your recipients will use, and walk through these checks:
- Type into every text box and confirm the keystroke actually appears in the field, not on the page underneath.
- Toggle every checkbox and save the file. Close it, reopen it, and confirm the checkmark is still there. A field that forgets its state after save is a broken field.
- If the required flag is used, look at how the viewer represents it. Some viewers highlight required fields; some viewers add a small marker; others show no visible cue at all. If your recipients may not notice the flag, do not rely on it to block empty submissions.
- Print the form or open the print preview. Long labels can wrap awkwardly, and checkboxes placed next to long labels can shift their alignment on the printed page.
- Decide whether the form should stay editable or be locked. To make filled answers permanent so they cannot be edited later, run the file through a separate Flatten PDF step.
If a polished or regulated document is needed — one with custom fonts, branded colors, accessibility tags, a precise tab order, or a formal compliance review — recreate the form in a professional authoring application. The browser builder is a starting point, not a substitute for that workflow.
If you're weighing options, When AI Form Detection Fails: Use a Blank-Page Builder covers this in detail.