Reviewed by: Y. Garcia
Google has extended to iOS and Android the advanced autofill capabilities that desktop users gained over the past eight months, letting Chrome pull passport numbers, driver's license details, Known Traveler Numbers, flight confirmations, and vehicle data directly from Google Wallet to fill web forms, Google announced last month.
The June 2026 mobile launch also deepens the Wallet integration itself: Chrome can now write credentials to Wallet when a user enters them on a site for the first time, not just read them back.
That enrollment capability marks a meaningful shift in what the feature is. Chrome is no longer moving data from point A to point B. It is becoming the interface through which sensitive credentials enter Google's infrastructure in the first place.
How the advanced autofill on iOS and Android arrived
The mobile launch is the third act of a rollout that started eight months ago.
In November 2025, Google introduced what Android Police called the browser's biggest autofill change in years: desktop Chrome gained the ability to fill passport numbers, driver's license numbers, and vehicle identifiers including VIN and license plate. That update went live globally in all languages from day one, per Google, which also signaled that more data types were coming.
Something quieter also happened in that November update. For signed-in users, Chrome began pulling names, email addresses, and home and work addresses from the Google Account. Identity and vehicle information, however, is stored in Google Wallet rather than treated as Google Account contact data. In
December 2025, it added loyalty card details and flight bookings. When a travel form asks for flight information, Chrome can find the relevant booking confirmation stored in Google Wallet and fill in the confirmation number and dates automatically, Google noted. What had required digging through email or a travel app became a single tap. Vehicle details for tasks like insurance quotes and car rentals also arrived on desktop at this point.
The June 2026 mobile launch extends those same Wallet-backed credential types to Android and iOS. If the credentials are not already stored in Wallet, Chrome offers to save them there the first time a user enters them on a website, according to Google.
Chrome autofill passport and driver's license: what's supported on mobile
The credential types now available on mobile match the desktop expansion:
Driver's license details
Passport information
Known Traveler Number
Flight details and confirmation numbers
Vehicle license plates and VIN
Loyalty card details
Chrome 150 for Android ships a restructured settings menu that makes Google's intentions plain. The old catch-all "Passwords and Autofill" section is replaced by five distinct categories: Google Password Manager (passwords and passkeys), Payments (credit and debit cards, IBANs, loyalty cards), Contact info (addresses), Identity docs (driver's licenses, identity cards, passports), and Travel (travel info and vehicles), 9to5Google reported.
Five dedicated categories replace one. That restructuring reflects an expectation that each will matter to a significant share of users, and it makes it considerably easier to audit exactly what Chrome has access to, which matters more when the data in question is a passport number rather than a shipping address.
What this means for third-party autofill providers
Chrome on Android formally supports third-party autofill services. As of Chrome 135, users can designate a third-party password manager or autofill provider for passwords, passkeys, addresses, and payment data via a dedicated setting, the Google Developers Blog noted.
When another autofill service is selected in Chrome on Android, Google says all autofill data is sourced from that third-party provider. Whether identity or travel fields are supported therefore depends on the provider, not on a Google Wallet-only restriction documented by Chrome.
The June 2026 documentation describes Wallet-backed support for identity documents, Known Traveler Numbers, and flight bookings, and says nothing about comparable pathways for third-party providers to fill those fields. Based on what Google has published, a user who wants Chrome to autofill a passport number on a travel booking site currently has one viable option: store that credential in Google Wallet.
The tradeoff is concrete. Chrome becomes substantially more capable if you centralize identity and travel credentials in Google Wallet. If you prefer to keep that data in a third-party manager or out of Google's infrastructure entirely, the advanced autofill capabilities will apply to a narrower slice of your web activity. Chrome 150's redesigned settings make that fork more visible than it used to be.
Whether third-party providers develop any response to the identity-document gap is one of the more consequential competitive questions the June rollout opens up.
What Google has and has not said about security
Google's security commitments are specific in some areas and absent in others.
Chrome will only save or fill information with explicit user permission. A confirmation step is required before Chrome fills saved identity data on any form. All sensitive data is encrypted, per Google. Private passes, the category that includes digital IDs, have their own dedicated controls within Wallet. Each pass carries a "Use private pass across Google" toggle that lets users restrict whether a given credential is available outside the Wallet app itself, 9to5Google noted.
Stored data can be reviewed, updated, or deleted at any time through Google Wallet settings or Chrome's "Autofill and passwords" page. Android Police observed last November that the ability to remove this data is not a UX nicety when the credentials involved include passport numbers and government IDs; it is a practical requirement.
What Google has not addressed publicly: the specific encryption standard applied to identity documents, whether that data resides on-device or in Google Account cloud storage, and whether Chrome will require biometric or device-unlock authentication before filling passport or license fields. Those gaps become more pressing given that Google confirmed in November 2025 that support for additional data types was planned, and the eight-month rollout since has confirmed that trajectory. More credential types combined with the same unanswered authentication questions is worth watching closely.
The practical checkpoint for Chrome users on mobile
The June 2026 mobile rollout, paired with Chrome 150's restructured settings, is the point at which this shift reaches most Chrome users. Not a preview, not a gradual opt-in the current product.
For anyone using Chrome on Android or iOS: open Settings, find "Autofill and passwords," and check each of the five new categories deliberately. For any digital IDs stored in Wallet, locate the "Use private pass across Google" toggle and decide whether that credential should be available outside the Wallet app.
The feature defaults toward convenience, which is fine as a deliberate choice. Chrome offering to save a passport number is a different kind of prompt than Chrome offering to save a shipping address, and the controls exist to treat it differently.
What to track from here: regional availability of digital ID support, since Wallet pass coverage varies by country and is not fully detailed in current documentation; how third-party autofill providers respond to the growing identity-document gap; and whether Google introduces stronger authentication requirements as the credential categories continue to expand.
Comments
Be the first, drop a comment!