Find what can be filled
Visible native inputs are gathered in page order, then checked again after the page settles for late-mounted fields.
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
Autocomplete token wins → field type: email
Native setter → input event → change event → framework state stays in sync
The simple popup button starts a sequence designed for real, messy web forms—not just clean demo inputs.
Visible native inputs are gathered in page order, then checked again after the page settles for late-mounted fields.
Autocomplete, labels, names, IDs, placeholders, rules, and saved mappings decide what data belongs there.
Inputs receive browser events. Dropdowns open and select. Rich-text editors update their document model.
Custom widgets, editable regions, shadow DOM, and supported frames are filled without one failure killing the run.
Writing a value into the DOM is easy. Keeping the application’s own state correct is the part that matters.
Text, email, dates, numbers, checkboxes, radios, and selects receive native setters and real event sequences.
FillMatic opens controls, waits for their popovers, chooses an option, and confirms the result like a user.
Editor-aware filling keeps the underlying document model synchronized instead of replacing visible HTML.
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.
Teach FillMatic the interaction once with a Recipe. It will replay those declarative steps before the built-in widget adapters on future fills.
Install FillMatic, open a form, and run your first fill. No setup is required for the common case.