Chrome Autofill vs FillWise: When the Built-in Filler Is Enough
The most common question we hear about FillWise is a fair one: "Chrome already fills my forms, why would I install anything?" For a lot of forms Chrome is enough, and this article says so. For another set of forms it never triggers at all, and that is the gap an AI filler covers.
We build FillWise, a Chrome extension, so treat this as a vendor's view. The description of Chrome autofill below follows Google's own help page as of September 2026.
What Chrome autofill does
Chrome saves a fixed set of categories and offers to fill them when it recognises a matching field on a page. According to Google's help centre those categories are:
- Passwords, through Google Password Manager.
- Payments: cards saved in Chrome or in Google Wallet.
- Contact info: name, email, phone, addresses.
- Identity docs: identification details saved in Google Wallet.
- Travel: travel details, also stored in Wallet.
Saving and filling is on by default for each category, you must be signed in to your Google Account, and Google notes that not all autofill features are available in all regions. Everything stays in your Google account, and nothing is sent to a third party. It is free, it is already installed, and for the forms it recognises it is the right tool.
Where it stops
Chrome autofill works by recognising standard fields: an input the browser can tell is a first name, a postal code, a card number. Three kinds of forms fall outside that:
1. Fields with no standard meaning. "Purpose of visit", "Have you been refused a visa before", "Employer's address in the country of destination", "Policy start date", "Reason for leaving". Chrome has no category for these, so it offers nothing. Visa applications, insurance applications and government portals are mostly made of such fields.
2. Data that is not yours. Chrome fills you: your name, your address, your card. A travel agent filling a client's booking, an HR coordinator onboarding a hire, a paralegal completing a client's application, all fill someone else every time. Chrome has no notion of "the person in this passport photo".
3. PDF forms. Chrome autofill fills web pages. A PDF application form opened in the browser is a document, not a web form, and stays empty.
There is a fourth, smaller limit: one form, one profile. A family of four on one booking page is four sets of fields, and Chrome fills at most the one that matches you.
What FillWise adds
FillWise is a side panel in Chrome. Open a form, give it the source, click Fill web form. The difference from Chrome is where the data comes from and how fields are understood:
- Any source, not a saved profile. Paste text in any format: a client's email, notes, a CRM export. Or attach a photo, scan or PDF. Passports and IDs in 100+ languages, including non-Latin scripts, are read by the AI.
- Fields by meaning, not by category. The AI reads the labels on the page and decides what belongs where, in the form's own language. "Purpose of visit" gets the purpose from your text; "nationality" gets the nationality from the passport.
- PDF forms. Fillable PDFs are completed field by field in your browser. Flat PDFs, the ones with no real fields, get values placed by position, with an editor to adjust before download. Scans without a text layer are not supported.
- Several people at once. One block of text with four travellers lands in four passenger sections.
- Known forms fill free. A form FillWise has filled before, filled again from typed text, does not spend a fill: unlimited on paid plans, 20 a week on the free plan.
What it does not do: it does not store your card, it does not fill passwords, and it does not run in the background. Chrome keeps those jobs.
Side by side
| Chrome autofill | FillWise | |
|---|---|---|
| Source of data | Your saved profile in Chrome and Wallet | Any text, photo, scan or PDF you provide |
| Fields it fills | Recognised standard fields | Any field, matched by its label |
| Whose data | Yours | Anyone's: clients, hires, family |
| Free-text questions | No | Yes, from your source |
| PDF forms | No | Fillable and flat PDFs |
| Multiple people per form | No | Yes |
| Passwords and cards | Yes | No |
| Runs on | Any page, automatically | When you click, on the page you are on |
| Cost | Free | Free tier, then from $15 for 100 fills a month |
Deciding per form
A quick rule: if the form asks only who you are and where you live, let Chrome fill it. If the form asks about someone else, asks questions, or is a PDF, reach for FillWise.
Three examples:
- Online shop checkout. Chrome. Name, address, card. Done.
- Schengen visa application for a client. FillWise. Passport photo as the source, forty fields including purpose, host address and previous visas.
- Your own job application. Chrome for the contact block, FillWise (or a job-specific tool) for the rest of the questions, from your resume pasted as text.
Both can coexist. FillWise fills only when you click, and Chrome's suggestions keep appearing as before.
What to check by hand
Whatever fills the form, you submit it:
- Names spelled exactly as in the passport.
- Date formats the form does not label.
- Dropdowns with look-alike options.
- Questions your source does not answer. FillWise leaves those empty rather than guessing.
Privacy
This is the honest trade-off. Chrome autofill keeps everything inside your Google account. FillWise sends the field labels and your source data to its server for one fill and to the AI provider that processes it, and does not store them. Fillable PDFs are parsed in your browser, so only the list of fields and your data leave it; flat PDFs send page images. The full breakdown, subprocessors and what the account does keep, is on the privacy and data security page. If a form is nothing but your own contact details, Chrome is the more private choice and you should use it.
Pricing
Chrome autofill is free. FillWise is free for 20 fills to start and 5 a week after that, with no card; paid plans start at $15 for 100 fills a month, listed on the pricing section. A fill is one web form or one PDF page.
FAQ
Will FillWise replace Chrome autofill? No, and it should not. Keep Chrome for passwords, cards and your own contact details.
Can Chrome fill a visa application? The contact and identity fields it recognises, yes. The rest of the form, which is most of it, no.
Does FillWise fill passwords or card numbers? No.
I turned Chrome autofill off because it filled the wrong thing. Does FillWise have the same problem? It can put a value in the wrong place, which is why you review before submitting. It fills only when you click, so it never changes a form you did not ask it to.
Get started
Leave Chrome autofill on. Install FillWise for the forms Chrome leaves empty, and try it on the next one that asks a question instead of an address.