FormForge vs Fake Filler
Both extensions fill web forms with test data, and for a plain form either will do. The real differences are how you pay, what leaves your browser, and whether you can check the claims yourself rather than take them on trust.
Fake Filler is the established option: 400,000 users, and it runs on Chrome, Edge and Firefox. FormForge is new, costs $39 once instead of $40 a year, makes no network requests, and ships a test suite you run in your own browser. Which one fits depends on which of those you need.
Side by side
Every row is a fact with a source. Figures were read from the two Chrome Web Store listings and from fakefiller.com on 7 September 2026.
| FormForge | Fake Filler | |
|---|---|---|
| Price | $39 USD once | Lite $0; Pro $3.99/month or $40/year |
| Billing model | One-time payment. Nothing renews. | Subscription, monthly or yearly |
| Free tier | No daily limit, no account. 1 saved profile, 2 field rules, exportable self-test report. | 25 custom fields, sync settings across browsers, URL-specific custom fields. |
| Data collected, per the store's own disclosure | "The developer has disclosed that it will not collect or use your data." | Discloses handling of "Personally identifiable information" and "Authentication information". Declares data is not sold to third parties, not used for unrelated purposes, and not used to determine creditworthiness. |
| Host permissions | None held at rest. activeTab and scripting are granted for one tab, on a click, shortcut or context-menu action, and end when the fill completes. |
Not stated on the Chrome Web Store listing page. Chrome shows an extension's permissions on the install screen — read it there. |
| Network requests | None. The extension never contacts a server, including for licence checks. | Not stated on the listing. fakefiller.com states "No ads and no tracking" on all tiers. |
| Fields it says it skips | CAPTCHA, hidden, disabled, readonly, file pickers and anything invisible. | Listing states it "Ignores CAPTCHA, hidden, disabled and readonly fields." |
| Self-test you can run yourself | Yes — a page inside the extension that runs the real fill engine in your browser. Free tier included. | Not mentioned on its Chrome Web Store listing. |
| Version | 1.0.3 | 4.1.0 |
| Last updated | 7 September 2026 | 3 August 2024 |
| Users (Chrome Web Store) | 6 | 400,000 |
| Rating (Chrome Web Store) | 5.0 from 1 rating | 4.4 from 794 ratings |
| Size | 123KiB | 536KiB |
| Browsers | Chrome 116 or later; Microsoft Edge | fakefiller.com lists Chrome, Edge and Firefox, version 60 or later |
Sources: the FormForge Chrome Web Store listing, the FormForge Edge Add-ons listing, the Fake Filler Chrome Web Store listing, and fakefiller.com.
Where Fake Filler is the better choice
There are several, and they are not small.
- It is proven at a scale FormForge is not. 400,000 users and 794 ratings, against FormForge's 6 users and 1 rating. FormForge was first published in August 2026. Those are the numbers on the two listings; you can check both in a minute.
- Its free tier is more generous for custom fields. Fake Filler's free Lite plan allows 25 custom fields. FormForge's free tier allows 2 field rules. If custom fields are the whole reason you want a filler, that difference decides it.
- $3.99 is a much smaller commitment than $39. One month costs about a tenth of FormForge's one-time price, and you can stop after it.
- Settings sync across browsers on every tier, free included. FormForge has no sync feature; its settings live on the device.
- It runs on Firefox. Fake Filler's site lists Chrome, Edge and Firefox. FormForge is on Chrome and Edge only.
If any of those describe you, install Fake Filler. This page is not trying to talk you out of it.
Where FormForge is different
One payment, not a subscription
$39 once against $40 a year: from the second year onward the comparison is not close.
Nothing leaves the browser
FormForge makes no network requests at all, and holds no standing access to any website — activeTab and scripting are granted for a single tab when you click the icon, press the shortcut or use the right-click menu, and end when the fill finishes. Even Pro licence keys are verified on your own device against a public key built into the extension, so activating Pro contacts nothing. The two stores' disclosures are linked in the table above; read both rather than taking either developer's word for it.
You can verify the claims yourself
Every form filler's listing says it handles React. FormForge ships the suite that demonstrates it, and you run it — in your browser, on your build, on the free tier, with no account. This is covered in its own section below.
Specific coverage, not "modern frameworks"
The cases FormForge is built for, stated as a list rather than a claim:
- React, Vue and Angular controlled inputs — written through the native setter and the framework's own change tracking
- Shadow DOM, including nested shadow roots and custom elements
- Fields classifiable only by an
autocompletetoken - Fields with no useful signal at all — no label, no placeholder, no name
- Field names containing dots and dashes that break naive selector matching
- Same-origin iframes
- react-select and similar custom dropdowns, including the type-to-search kind
We have not tested Fake Filler against any of these and make no claim about how it performs on them.
Verify it yourself
This is the part worth your attention, because it is the only claim on this page you do not have to believe.
FormForge ships a self-test page inside the extension. It loads the same engine the extension injects — not a copy and not a test build — and runs it against dozens of deliberately awkward fields: controlled inputs, nested shadow roots, custom elements, iframes, and the fields it is supposed to refuse to touch. The last recorded run graded 84 cases from 73 fixtures: 71 passed, 0 failed, 13 correctly skipped. That figure is ours; the point is that you do not have to take it from us.
You do not have to install anything to start. Test your form filler is a free page on this site built out of the same awkward cases — controlled inputs, shadow roots, hidden tokens, fields that must be refused. Run whatever filler you already use against it and it will grade the result. It grades every tool the same way and has no idea which one you used, so it works just as well for testing Fake Filler as for testing FormForge.
The suite inside the extension goes further, and to run that one you do need FormForge installed: open the Settings page from the toolbar icon, then open Self-test and run it. Free tier, no account, and the report exports. If something fails on your build, that report is what makes it fixable — send it to support@flinthive.com.
The reasoning behind the suite, including where it does not help, is written up in Half my test suite asserts that nothing happened.
Questions
Is Fake Filler safe to use?
We have not audited it and make no claim about it either way. What can be checked is its Chrome Web Store listing, which as of 7 September 2026 discloses that the extension handles "Personally identifiable information" and "Authentication information", and states that data is not sold to third parties, not used for unrelated purposes, and not used to determine creditworthiness. Whether that is acceptable depends on what you fill in and on whose machine. Chrome shows an extension's permissions at install time, so read that screen for any filler before you accept it.
Is there a free alternative to Fake Filler?
Fake Filler itself has a free tier: the Lite plan costs nothing and allows 25 custom fields, syncs settings across browsers and supports URL-specific custom fields. FormForge also has a free tier with no daily limit and no account, which includes one saved profile, two field rules and the exportable self-test report. If what you need is a lot of custom fields and nothing else, Fake Filler's free tier is more generous than FormForge's.
Does Fake Filler work with React forms?
We have not tested it, so we do not say. Do not take any form filler's word for it, including ours. Test it yourself: open a React form, run the filler, then read the value back from the application rather than from the screen. React keeps its own record of each input's value; if something writes to input.value directly, React sees no change and never fires onChange, so the text appears on screen while the application never receives it. Submit the form and check what actually arrives.
What is the best form filler for QA testing?
It depends on which problem you have. If you fill straightforward forms across several browsers and want a large, long-established user base, Fake Filler has 400,000 users and works on Chrome, Edge and Firefox. If your forms break other fillers — React, Vue or Angular controlled inputs, shadow DOM, custom dropdowns, same-origin iframes — or if the browser must make no network requests at all, that is what FormForge is built for. The way to decide is to run both against your own hardest form.
Does FormForge work offline?
Yes. FormForge makes no network requests at all — no analytics, no telemetry, no remote code and no language model. Everything happens in your browser on your device. The Pro licence key is verified against a public key built into the extension, so even activating Pro does not contact a server. Its Chrome Web Store listing states that the developer will not collect or use your data.
Try it
The free tier has no daily limit and no account, and the extension includes a 7-day Pro trial that needs no card. Read what FormForge does first if you have not.
Comparison checked 7 September 2026 against the public Chrome Web Store listings and fakefiller.com. Figures on those pages change; if something here is out of date or wrong, tell us and it will be corrected. Corrections: support@flinthive.com
Fake Filler is the product of its own developer. Its name is used here only to refer to it. There is no affiliation between FlintHive and Fake Filler, and none is implied.