RECIPES
Teach the tricky part.
A custom dropdown needs a click before a selection? Record those steps once as a Recipe in the side panel and let the next fill follow them. Each Action can run just the Recipes you pick.
See how Recipes work
FORM FILLER EXTENSION FOR DEVELOPERS & QA
A browser extension that autofills forms with realistic test data.
Fill in one click. Handle custom controls and save repeatable workflows for your next test.
Quick fill
Fill supported fields on this page.
MADE FOR THE FORMS YOU BUILD
FILL, CUSTOMIZE, REPEAT
Start with one click. Add control as your tests need it.
Names, emails, addresses, dates. Realistic test data for the fields in front of you.
Try a signup formSet the values that matter. Teach a custom control its clicks and selections with a Recipe.
Explore RecipesSave a site-specific Action. The next time you test that flow, your setup is already there.
Meet the Action builderYOUR FORM. YOUR PLAYBOOK.
Turn a form you test often into a one-click Action, built beside the page in four steps.
Pick the form to scope. Its fields are listed for you.
Set the values that matter. Edit the suggested value for any field.
Preview the result on the page before you commit.
It appears on matching pages and runs the same way every time.

BEYOND THE TEXT BOX
From familiar inputs to the controls that need a little teaching.
RECIPES
A custom dropdown needs a click before a selection? Record those steps once as a Recipe in the side panel and let the next fill follow them. Each Action can run just the Recipes you pick.
See how Recipes work
INPUTS, WIDGETS & EDITORS
Fill supported native inputs, common ARIA patterns, Radix/shadcn widgets, and editor-aware rich text.
Keep your app's state and validation in sync as supported fields are filled.
Names, dates, selects, checkboxes, and more.
Comboboxes, switches, sliders, and date pickers.
Editor-aware filling, including Tiptap.
Compatibility depends on the control. Try your stack in the demos. See support and limitations.
PROFILES
Give each project its own settings, field rules, Actions, and Recipes. Switch your active Profile right from the popup.
Build your testing setup
EVERYDAY TESTING
Restore the last fill on the same page, even after a reload. Keep the same values while you reproduce a bug.
For stable, supported fields during your browser session.
Fill the whole page, choose a named form, or fill just the focused field. Keep the rest of the page out of your way.
Shortcuts: Ctrl+Shift+X fills the page, Ctrl+Shift+8 the focused form, Ctrl+Shift+9 the focused field (Command on Mac). Change them in your browser's extension shortcuts.
Match fields by their label, name, ID, placeholder, or autocomplete attribute. Reuse fixed values or data generators.
Scope rules to a site and organize them by Profile.
Generate data in locales including English, Hindi, and French, or let the page and browser language guide it.
Review generated values against your own validation.
Fill supported fields inside iframes and open shadow roots. Values go in through real input events, so framework-controlled state stays in sync.
Saved Actions fill child frames only when you opt in.
See filled, skipped, and failed counts with reasons. Find the controls that need attention before you continue.
Inspect the completed form before submitting.
LOCAL BY DESIGN
Form inspection, data generation, and mapping happen locally.
Read the privacy detailsREADY WHEN YOU ARE
Add FillMatic from your browser's extension store, then pin it in your extensions menu.
Start with our signup demo or a page you're testing. You're in control of when filling starts.
Choose Fill all fields in the popup. Review the values and result summary before submitting.
Most of them. Every native input works out of the box: text, dates, numbers, selects, choices, and passwords, plus ARIA widgets and rich-text editors. Fields are matched by label, then autocomplete, then name, id, or placeholder, so accessible, semantic forms get the best support. Got a custom widget it doesn't handle yet? Record a Recipe in the side panel once and every fill replays it. Check every input type Teach it a custom widget
FillMatic fills fields by dispatching input and change events from JavaScript, and browsers always mark those as untrusted (event.isTrusted === false). A site that requires event.isTrusted, or otherwise only accepts real user input, ignores the fill. Fields named captcha are skipped by default (configurable in Settings). File inputs, closed Shadow DOM, and browser internal pages are not supported. A Recipe can drive a custom widget, but it cannot make a site accept scripted input. Check every input type
Field Rules decide what value a field gets, like "any field labeled Company gets Acme Inc." Actions are one-click buttons for a specific page or flow that can override fields, run steps first, or fill just part of the page. Recipes teach FillMatic how to operate one custom widget, like a dropdown that needs a click before you can pick an option. Profiles bundle your settings, Field Rules, Actions, and Recipes per project so setups never mix. You can ignore all of them: the plain one-click fill works with no setup. Read the full guide See how Recipes work
Form inspection, data generation, and mapping run locally. Settings, Profiles, Actions, and Recipes are stored in your browser, and repeat-fill values last for the browser session. Page access lets it find fields and fill supported forms across frames when you ask it to, so use it on pages you own or are authorized to test. Saved Actions fill child frames only when you opt in; the Action builder scans and previews the main page.
Use the feedback form below with a link to a public page where it happens. A small CodePen or StackBlitz repro works too. Screenshots do not show the markup behind a field. Tell us your browser, the control or library, what you expected, and what happened. Never share credentials or private data. We will do our best, but we cannot support every control or promise a fix or timeline.
BUILT WITH YOUR FEEDBACK
Tell us what you were testing and where it got stuck. A public test page or a small reproduction helps.
We will take a look and try our best. We cannot promise a fix or a timeline, but every report gets read.
LESS BUSYWORK. MORE BUILDING.
Desktop browser. Your workflow, saved locally.