Skip to main content
Inside the autofill engine

One click on top. A deliberate pipeline underneath.

FillMatic does more than paste random text. It reads what each field expects, creates matching test data, and interacts with the page the way its framework expects.

No account · No cloud processing · Works without AI

fill-run / checkout.example.com
01
Read the field
<input autocomplete="email" name="billing_email">
02
Resolve the meaning

Autocomplete token wins → field type: email

03
Generate matching data
nora.ali@example.com
04
Write it like a user

Native setter → input event → change event → framework state stays in sync

The fill run

Four jobs, in the right order

The simple popup button starts a sequence designed for real, messy web forms—not just clean demo inputs.

01 / DISCOVER

Find what can be filled

Visible native inputs are gathered in page order, then checked again after the page settles for late-mounted fields.

02 / UNDERSTAND

Work out what it means

Autocomplete, labels, names, IDs, placeholders, rules, and saved mappings decide what data belongs there.

03 / INTERACT

Use the right interaction

Inputs receive browser events. Dropdowns open and select. Rich-text editors update their document model.

04 / CONTINUE

Handle the rest of the page

Custom widgets, editable regions, shadow DOM, and supported frames are filled without one failure killing the run.

More than text boxes

Different controls need different moves

Writing a value into the DOM is easy. Keeping the application’s own state correct is the part that matters.

Native and framework inputs

Text, email, dates, numbers, checkboxes, radios, and selects receive native setters and real event sequences.

  • React controlled inputs
  • Vue v-model fields
  • Angular reactive forms

ARIA and custom widgets

FillMatic opens controls, waits for their popovers, chooses an option, and confirms the result like a user.

  • Comboboxes and autocomplete
  • Date pickers and radio groups
  • Switches, sliders, and steppers

Rich-text editors

Editor-aware filling keeps the underlying document model synchronized instead of replacing visible HTML.

  • ProseMirror and Lexical
  • Slate and Quill
  • Trix and contenteditable
Control without repetition

Your intent gets first priority.

FillMatic starts with smart defaults, but it never forces you to accept a guess. Pin exact values, save a field map, switch profiles, or create one-click Actions for the flows you repeat every day.

ActionsSaved mappingsProfile rulesHeuristicsType fallback
Highest
Active Action overrideA one-click workflow pins values for matching fields.
Next
Saved field mappingA reviewed side-panel map is reused without running a model.
Next
Profile field ruleSite-specific exact, contains, or regex matches apply.
Default
Page semantics and heuristicsAttributes and labels identify the expected data.
Fallback
Input typeThe browser input type provides a safe final hint.

Custom widget still refuses to cooperate?

Teach FillMatic the interaction once with a Recipe. It will replay those declarative steps before the built-in widget adapters on future fills.

Learn about Recipes →

Ready to stop filling test forms by hand?

Install FillMatic, open a form, and run your first fill. No setup is required for the common case.

Add to Chrome