Bulk submissions
Submit hundreds of forms from CSV rows or database records in one run.
Automated form filling that actually submits
Browserbase runs real browsers that fill web forms automatically, the way a person would. They handle dynamic fields, gated logins, and CAPTCHAs, then submit at scale.
The Problem
Why web form filling automation breaks
- Filling the same web forms by hand, one record at a time, across hundreds of submissions.
- Brittle scripts that snap the moment a field, label, or step order changes.
- Dynamic forms that reveal fields conditionally, so a fixed selector list never matches.
- Forms locked behind logins that log you out between runs.
- CAPTCHAs and bot walls that block scripted requests before the form ever submits.
The Solution
How Browserbase automates web form filling
- Real browsers: fill and submit web forms exactly like a person, including forms with no API.
- Dynamic field handling: read the page as it renders, so conditional and multi-step forms fill correctly.
- Verified: reach forms that turn away ordinary tooling, with no per-site tuning.
- Agent Identity: Web Bot Auth signs your agent's requests, so sites can verify it instead of guessing.
- Managed CAPTCHA solving: clears challenges inline so submissions go through.
- Persistent sessions: stay logged in to gated forms across runs.
- Parallel submission: fill and submit thousands of forms at once from one API key.
What you can automate
Dynamic and multi-step forms
Conditional fields, wizards, and pages that render as you go.
Gated forms
Forms behind logins that stay authenticated across sessions.
Frequently Asked Questions
How do I automate filling in web forms?
Point a Browserbase browser session at the form, then drive it with your automation code or the Stagehand SDK. The browser loads the page, fills each field the way a person would, and submits. Because it is a real browser, it handles dynamic fields, logins, and CAPTCHAs that break request-only scripts.
Can it handle dynamic forms where fields appear conditionally?
Yes. Browserbase reads the page as it renders, so fields that appear based on earlier answers, along with multi-step and wizard-style forms, fill in the correct order instead of against a fixed, brittle selector list.
What about forms behind a login?
Persistent sessions keep your agent authenticated across runs, so forms locked behind a login stay reachable without signing in every time.