Why Chrome Autofill Fails on Half the Internet (And What I Use Instead)

I used to trust Chrome autofill. Then I booked a flight to the wrong city.

True story. Last March, I was booking a flight to Portland, Oregon. Chrome autofill decided to put my billing city in the destination field. I did not catch it until after I hit submit. The airline's change fee was $75.

That was the day I stopped trusting browser autofill with anything more complex than my email address.

But I didn't stop there. I got obsessive about it. I spent two weekends testing Chrome autofill on 50 different websites, tracking exactly where it worked and where it completely fell apart. The results were worse than I expected.

The real reason autofill puts your zip code in the phone field

Chrome's autofill system was designed in 2011. That is not an exaggeration. The core matching logic reads HTML field names and attributes, then tries to match them to your saved addresses and payment methods.

That worked fine when every form was simple HTML with predictable field names. But the web changed. Chrome's autofill didn't.

Here is what actually happens when autofill goes wrong:

• Modern sites build forms with React, Vue, and Angular. These frameworks generate field names dynamically, so Chrome sees input_7xk2m instead of phone_number
• Multi-step forms load new fields after the page renders. Chrome runs autofill once on page load and misses everything that appears later.
• Custom dropdowns, date pickers, and styled inputs don't use native HTML elements. Autofill cannot interact with them at all.
• Some fields share similar HTML attributes. "City" and "company" can both contain "co" in their name attribute, so Chrome just guesses. Often wrong.

Autofill is not bad software. The web just outgrew it years ago and nobody went back to fix the gap.

I tested autofill on 50 websites. It fully worked on 19.

Over two weekends, I systematically tested Chrome autofill on 50 popular websites. Job boards, e-commerce sites, government portals, booking platforms. My criteria was simple: did autofill correctly populate every field without manual corrections?

1. E-commerce checkout pages: 7 out of 12 worked correctly
2. Job application portals (Greenhouse, Lever, Workday): 2 out of 10
3. Government and tax forms: 1 out of 6
4. Travel booking sites: 4 out of 8
5. Insurance and financial quote forms: 2 out of 7
6. Account registration pages: 3 out of 7

Overall: 19 out of 50. A 38% success rate. And I was being generous. I counted partial fills where only one or two fields were wrong as "worked."

The worst offenders were job application portals. Workday forms? Chrome just stares at them blankly.

I spent more time correcting autofill mistakes than I would have spent typing from scratch. It gives you just enough hope to try it, then wastes your time with wrong data in wrong fields.

Three types of forms that defeat autofill every time

After enough testing, I noticed a pattern. Three specific form types break autofill almost without exception.

1. Multi-step wizards

Any form that splits across multiple pages or tabs. Job applications are the obvious example. Personal info on page 1, work history on page 2, education on page 3. Chrome might handle page 1. Pages 2 and 3? You are on your own.

2. Dynamic conditional fields

Fields that appear based on previous answers. Select "Yes" on "Do you require visa sponsorship?" and three new fields appear. Chrome has no idea those fields exist because they were not there when the page loaded.

3. Custom-styled inputs

Dropdown menus that are not native HTML select elements. Date pickers built with calendar widgets. Phone number fields with country code selectors. If it looks custom, autofill cannot touch it.

These three patterns cover roughly 70% of the forms I fill out in a given week. Which means browser autofill is useless for most of my actual form-filling needs.

What I actually use now (honest review, flaws included)

After the 50-site test, I tried four different autofill alternatives. Password managers with form filling (1Password, Bitwarden), a dedicated autofill extension, and Filliny.

I will be upfront: Filliny is the one that stuck. But it is not perfect, and I will tell you exactly where it falls short, because I don't trust reviews that read like advertisements.

What Filliny does differently is use AI to read the actual form. Not the HTML attributes. The visual layout, the labels, the context of surrounding fields. It figures out what each field is asking for the same way you would if you were looking at it.

• Correctly fills multi-step job applications on Greenhouse, Lever, and Workday
• Handles custom dropdowns and date pickers that Chrome ignores completely
• Fills conditional fields that appear after you interact with the form
• Lets you create different profiles for different contexts (I keep one for job apps, one for shopping)
• You can set the tone for open-ended text fields, which I didn't know I needed until I had it

Where it falls short: it occasionally picks the wrong option on very ambiguous dropdown menus. I have seen it choose "Mr." when the field was asking for a professional title like "Software Engineer." Happened maybe 3 times in a month of daily use. Small enough to not bother me, honest enough to mention.

The free tier is actually useful (not just a demo)

This is where I expected to get burned. Most free tiers in software are basically demos. You can look but not really use anything.

Filliny gives you 5 free form fills. Not 5 fields. 5 entire forms. That is enough to fill out a Workday application, a Greenhouse application, buy something on an e-commerce site, register for an account, and fill out a survey. Five real uses that show you exactly what the tool can do.

If you fill out fewer than 5 forms a week, you might never need to pay. I fill out way more than that, so the Pro plan made sense for me. But I respect that the free version is not crippled.

Five free fills doesn't sound like a lot until you use one on a Workday application that would have taken you 8 minutes to type out by hand. Then you get it.

The math, for people who need to see the ROI

I need to see numbers before committing to any subscription. Here is what I calculated after one month:

• Forms filled per week: roughly 25 (job apps, shopping, signups)
• Average time saved per form: about 3 minutes
• Weekly time saved: 75 minutes
• Monthly time saved: 5+ hours
• Monthly cost of Filliny Pro: $12
• Monthly value of saved time at $30/hour: $150+

So I pay $12 to get back $150 worth of time. The annual plan is $99, which works out to $8.25 a month. At that point you are paying about 27 cents per day.

Compare that to what you spend on streaming services or that gym membership you are definitely using every week. The math just works.

Setup takes less time than reading this section

1. Install Filliny from the Chrome Web Store. About 15 seconds.
2. Create a profile with your basic info (name, email, phone, address). Maybe 30 seconds if you type fast.
3. Navigate to any form on the internet and click the Filliny icon in your browser.
4. Watch every field fill correctly in about 2 seconds.

No configuration files. No importing data from other tools. No tutorial videos. The AI figures out the form on its own.

If you want more from it, you can add work history, education, and custom fields to your profile. You can create multiple profiles for different contexts. But none of that is required to start.

Should you actually switch?

If Chrome autofill works for you on every form you encounter, keep using it. It is built in. It is free. No reason to change what works.

But if you have ever watched autofill put your state abbreviation in the apartment number field, or if you regularly fill out applications on Workday and Greenhouse, or if you are just tired of typing the same information into slightly different boxes multiple times a day, give the free version a try.

You get 5 fills. It costs nothing. The first time the AI correctly fills a 15-field Workday application in 2 seconds, you will have your answer.

Here is the link to install: filliny.io/install-extension

I started using Filliny because autofill kept breaking. I kept using it because it actually works on the forms Chrome cannot handle. That is the whole story.