Skip to Content
Platform.Ontology

Autofill and autocomplete tokens

Form fields can ask the browser to fill saved name, email, phone, address and birthday.

Works without askingContacts and personal dataAutofillWeb browsersWhile you use it

In one line

Can ask your browser to fill saved name, email, phone and address

Form fields can ask the browser to fill saved name, email, phone, address and birthday.

Browser autofill puts personal data into inputs. Pages see it only after fill (often after user interaction on Chrome).

What it can and can't do

What the user does: You tap a form field and choose a suggestion, or click first on some sites.

It can

  • Fill name, email, phone, address and birthday from your saved details
  • Fill the fields it marks with the right label
  • Offer them as soon as you tap a field

It cannot

  • See saved details before you pick them, on most browsers
  • Fill details you never saved
  • Fill fields in a hidden form without your tap in most cases
  • Ignore your turning autofill off

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported142011-09-16None
EdgeSupported122015-07-29None
FirefoxSupported42011-03-22None
SafariSupported62012-07-25None
Safari on iPhoneSupported62012-09-10None
Chrome on AndroidSupported182012-06-27None
Samsung InternetSupported1.02013-04-27None

How a site asks for it

API<input autocomplete='name|email|tel|street-address|postal-code|cc-number|bday|sex|organization|one-time-code'>
Browser compat keyshtml.global_attributes.autocomplete
How access is grantedgesture
What the user seesAutofill dropdown; some sites need a click before values are readable
Needs a secure context (HTTPS)Yes
Needs a user gestureYes
How long it lastsPer origin
How to take it backSite settings
Inside an iframeSame as top level; cross-origin iframes need a permissions policy where listed

Typical flow

  1. Call the API
  2. Browser applies its access rules
  3. Page receives the result

Data you get

What comes back: Form fields can ask the browser to fill saved name, email, phone, address and birthday.
Shape: object
How often: on demand

FieldTypeUnitRangePrecision
name, honorific-prefix, given-name, family-namestringNonefree textNot listed
email, tel, tel-nationalstringNonefree textNot listed
street-address, address-line1, address-level1/2, postal-code, countrystringNonefree textNot listed
cc-name, cc-number, cc-exp, cc-cscstringNoneChrome fills cards after confirmation; csc needs extra stepNot listed
bday, sex, organization, usernamestringNonefree textNot listed

Technical limits

  • Hidden fields can be filled by some autofill; browsers mitigate
  • Payment fields need user confirmation
  • Not a read API: the site only sees what the form posts

The story

What it is

Forms can ask your browser to fill name, email, phone, address and more.

For you

You tap one form field, pick your saved info, and many fields fill at once. Some hidden fields can fill too, so check what you share.

For makers

Makers add the right labels so your browser can fill signup and checkout forms. It lifts signups, but hidden fields can collect more than you meant to share.

Where you see it

TypeExampleApps
shoppingA checkout form fills name, address and phone in one tap.Shopify stores
socialA signup page fills your email and birthday.Facebook, X
travelA booking form fills passenger details.Expedia
adsA lead form fills fields for you, and you send more info than you thought.None named
securityA hidden field on a form collects phone or address that you never saw.None named
bankingA loan form fills name and address, but you review the rest.None named

Risks

  • Hidden field harvesting
  • Over sharing

What the platform says

Good uses and abuse

Legitimate uses

  • Faster checkout
  • Sign up

Known abuse

  • Harvesting hidden field autofill (known abuse by ad scripts)

Scores

ScoreValueMeaning
Sensitivity5 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction1 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2012, Chrome 14: autocomplete tokens defined in the HTML spec (autofill honoured earlier)

Sources

How well checked: Based on official documentation.

On this page