From installing to your first filled form, there are three clicks. The rest of this document is here for the times you want to do better than the default.
An extension is a small tool that adds itself to your browser, the way an app adds itself to a phone. It installs in one click from Chrome's or Edge's official store, and comes off just as easily.
Three things to know, and you'll know the essentials:
The rest of this page reads in order the first time, then works as a reference. Give it five minutes and you're independent.
Verifill installs from your browser's store. Chrome and Edge both work; Brave, Opera and Vivaldi accept the Chrome version.
Right after installing, do this once and you'll never hunt for the tool again: click the puzzle piece to the right of the address bar, find Verifill in the list, and click the pin next to its name. The icon now stays visible.
You then have two ways to open Verifill, and they serve different purposes:
Opens the full window: the five tabs, all the settings. It closes as soon as you click in the page. Perfect for setting up, analysing, exporting.
Shows the panel inside the page itself. It stays open while you work. It's the one you'll use most once you get used to it, and section 05 is devoted to it.
If your browser says “this extension can read and change site data” when you click, that is normal and temporary: the permission covers only the tab on screen, and it lapses as soon as you move to another page.
Open the form you want to fill, then click the Verifill icon. The window opens on the Fill tab.
Verifill reads the form and lists what it understood: a label, the field type, and the rule it intends to apply. Nothing has been written into the page yet.
This is the moment that matters. Untick a field to leave it aside, change a rule, force an exact value. Everything you set here is remembered for this screen: next time, there will be nothing left to do.
The values are written, every filled field is outlined in colour on the page, and a sentence tells you what happened: how many fields, and how many satisfy what the site demands.
A word on the sentence at the end: “6 field(s) filled · 4/4 valid” does not mean “4 out of 6”. The two numbers count different things. The first counts the fields written; the second covers only the fields for which the site declares a checkable requirement (a pattern, a length, bounds), the others having nothing specific to comply with.
Each line gives you three things, and leaves you in control of all three.
It decides whether the field gets filled. Untick whatever you want left empty: an unticked field stays unticked for this screen, next time included.
What Verifill understood the field to be: a first name, an adult's date of birth, a number between bounds, an email address… If it doesn't suit you, change it in the menu: your correction becomes the right answer for that field, permanently.
The text box under the rule. Whatever you type there is written as-is: the most direct route when a form expects one precise value that only you know.
For a drop-down or a radio group, the menu offers the page's real options, plus “Random”. For a checkbox, you choose “Tick” or “Untick”.
At the top, “Scope” decides what gets analysed. “Forms only” looks at the form itself: almost always the right choice, because it leaves search bars and filters aside. “Whole page” includes everything else; use it when Verifill reports skipped fields that you actually need.
Finally, “Reset settings”, at the bottom, erases what you set for this screen and nothing else. A confirmation states exactly what goes.
This is the feature you discover second, and never give up. The extension window closes as soon as you click in the page: handy for setting up, awkward for working. The panel solves precisely that.
Ctrl + Shift + V, on the page where your form is. The same shortcut closes it.
The panel appears inside the page, top right, and stays there. Grab its title bar to move it if it's in the way, “Close” to make it go. You can click anywhere in the form, scroll, move to the next step: it doesn't move.
The panel carries the essentials of the “Fill” tab, compactly: the scope, “Analyse the fields”, “Fill”, the “Only fill empty fields” and “Live follow-up” options, and the three value sources.
That's where it shines: a multi-step journey. You fill step 1, click “Next” in the page, step 2 appears, and the panel is still there: one click on “Analyse” then “Fill”, and you carry on. No trips back to the toolbar.
The “Learn this form” button is in the panel too: fill a screen by hand, click it, and Verifill remembers what you put in each field for next time.
At the bottom of the panel, four buttons: “Fields & rules”, “Values”, “Selectors”, “History”. Each opens the full tool in a small separate window, already pointed at that very form.
For anyone writing tests, it's the most comfortable way to work: the page stays in front of you, the Selectors window beside it. You spot a field in the page, read its verified selector in the window, copy it, paste it into your test. And because that window is separate, it doesn't close when you click in the page.
The panel and the window share the same settings: what you tick in one, you find in the other. They are two doors into the same tool, not two tools.
On Edge, extension shortcuts are not assigned by default. The “Settings → Appearance” tab shows the shortcut actually assigned, and tells you where to pick one if it is empty.
By default, Verifill composes plausible values. Perfect for a trial, but often you want yours: your test address, a case number, a company name. That is set in the Values tab, and it is set only once.
You declare a keyword and the value to write: as soon as a field carries that word in its label, your value is used, on this site and on others. The simplest way to impose your data once and for all.
Fill a screen by hand, then ask Verifill to “learn” it: it remembers the pairing between each field and what you put in it, and replays next time. This is what you want when the values are too specific for any rule.
Under the field list, “Value sources” shows three switches: Dataset, Learning, Custom fields. They say where values are allowed to come from. A value you typed yourself on the field's line beats everything else; then come these sources; last, the rule.
If you have to create twenty test records, you don't want the same values twenty times. Import a dataset: a CSV, Excel or JSON file where each row is one profile.
The rule is simple: one column per field, one row per profile. The column name should resemble the field's label; Verifill matches them itself, and tells you which ones it recognised.
On each fill, it takes the next row. You can also point at the row to use. And you can keep several datasets, one per test case, and switch between them.
A dataset applies to the fields whose column exists; the others keep being filled by the rules. A partial dataset is therefore perfectly fine: the form still gets filled completely.
Many modern applications reveal fields later: one choice uncovers others, a next step appears without the page reloading. Two settings handle these cases, under the field list.
Verifill keeps watching that same tab for the duration you choose, one to ten minutes, and fills fields as they appear, without you coming back. This is the setting to tick for a multi-step journey.
Nothing that already carries a value gets overwritten. Ideal when you come back to a step you already filled. Checkboxes are always handled: “unticked” is a value, not an emptiness.
Embedded frames are handled like the rest: if the form lives in a frame, Verifill finds it and writes into it.
And the panel (section 05) makes all of this even more comfortable: it stays on screen from one step to the next.
This part is for people who write automated tests. Everyone else can move on: the tool is complete without ever opening this tab.
In the Selectors tab, “Analyse” gives, for every field and button, a way to target it in a test: in CSS, in XPath, or in JavaScript. Every selector is replayed on the page before being shown to you: it matches that element, and only that one.
Next to each selector, a word: solid, ambiguous or fragile. It isn't an opinion, it is the result of the replay. An id that changes on every page load is recognised as such and replaced by a stable marker: exactly the trap that makes a test fail the following week for no visible reason.
At the top, “My test is written in” picks your language: Robot Framework, Python with Selenium, or JavaScript. “Export the script” then produces a complete, pasteable script, for one screen or for a whole journey if you let Verifill follow your steps.
The comfortable way: open the panel with Ctrl + Shift + V, then its “Selectors” button. The list opens in a separate window, the page stays in front of you, and you copy on one side what you paste on the other.
The History tab keeps every fill: the date, the screen, the value written into each field, and where it came from. It's what you open when someone asks “what data did you test with?”.
You filter by date, jump straight to a day, export to CSV, Excel or JSON, everything or only what the filter shows. Each fill can also be exported on its own. “Cleanup & space used”, at the bottom, says how much room all this takes and lets you prune it.
Everything Verifill remembers lives in your browser: your per-form settings, your values, your datasets, the selector memory and the history. That means two things: nobody else sees it, and nobody else backs it up. Five minutes once, and you're safe.
Click the Verifill icon, then the Settings tab. Scroll to “Full backup”.
Your browser asks you to allow access to that folder: accept. Choose a folder that is already synced by your company or your usual file service. That's what makes the backup useful: it travels with the rest of your documents.
From then on, the extension rewrites your data there after each fill, on its own. Nothing left to do, and nothing to dig out of your downloads.
Install Verifill, point at the same folder, then click “Load from the folder”. Your settings, your values and your history are back, identical.
After a browser restart, permission to write to the folder may be requested again: a “Re-enable access” button then appears, and one click is enough. Nothing is lost in the meantime: everything stays in the extension and is caught up when it resumes.
Under “Manual backup”, “Save to a file” writes everything into a single file you keep wherever you like, and “Restore…” reads it back. Handy before a big change to your settings, or to pass your configuration to a colleague.
Still in Settings, “All memory, by address” lists site by site everything Verifill has kept, and lets you erase part of it or all of it. What this view shows is everything there is: there is nothing elsewhere.
Three things to check, in this order. Was it ticked in the list? Is it outside the form, like a search bar (switch the scope to “Whole page”)? Does it appear only after a choice (tick “Live follow-up”)? In all three cases, one setting is enough, and it is remembered afterwards.
Two levers, your choice. Change the field's rule in its menu if the type is wrong; type the exact value on its line if it's one precise piece of data. Both are remembered for this screen, and next time there's nothing left to do.
That's the case of a number that must match an existing record. Put it as an exact value, or load a dataset with the matching column: Verifill will run through your rows one by one.
Browsers reserve their own pages (those starting with chrome:// or edge://, the extensions page, the store) and let no extension act there. Open your form in an ordinary tab and everything comes back.
Section 11 is made for that: point at the same backup folder on the new computer and click “Load from the folder”. Everything comes back.
In Settings, the “Copy report” button puts on your clipboard everything we need to reproduce the situation: version, browser, settings, and your last few fills. Paste it into an email. The sentence next to the button states exactly what it contains, read it before sending.
Six habits that, once acquired, change how the tool feels.
And if a form gives you trouble, send it to us: it goes into our test collection, and the engine improves for everyone.