Google is taking Chrome's autofill capabilities up a notch, announcing on June 23, 2026 that the browser will soon handle far more than just passwords and credit cards. On Android and iOS, Chrome will gain the ability to autofill complex identity documents—including passports, driver’s licenses, and Known Traveler Numbers—by pulling data directly from Google Wallet. The move marks a significant expansion of Chrome’s built-in form-filling tools, which have long been limited to addresses, payment methods, and basic contact details. By tapping into the secure enclave of Google Wallet, Google aims to make filling out travel, vehicle, and identity forms on mobile devices both faster and more secure.
The rollout, slated for the coming weeks on Android and iOS, will initially support a narrow but impactful set of document types: flight confirmations, vehicle registration details, passport numbers, driver’s license information, and Known Traveler Numbers (KTN). Google says the feature leverages existing Wallet passes and digital IDs to pre-populate web forms, but does so only after a biometric verification—fingerprint, face scan, or device PIN—ensuring that sensitive data isn’t handed out casually. While the announcement focused on mobile platforms, the underlying technology hints at a broader cross-device strategy that could eventually bring the same convenience to Chrome on Windows and Mac.
Beyond Passwords: Chrome’s Expanding Autofill
Chrome’s autofill engine has been a cornerstone of the browser’s user experience for years, automatically filling names, email addresses, phone numbers, and physical addresses from a local or synced profile. In 2020, Google extended this to payment cards via Google Pay, allowing users to complete purchases with just a CVC code. But identity documents present a different challenge: they contain more sensitive, government-issued information that, if stolen, can lead to identity theft or fraud. Until now, autofill for such documents has been largely absent from mainstream browsers, with most users resorting to manual entry or local password managers that store custom fields.
Google’s solution centers on integration with Google Wallet, which already stores digital versions of credit cards, transit passes, loyalty cards, event tickets, and—in some regions—digital IDs. By treating a passport number or driver’s license much like a saved credit card, Chrome can read the structured data from Wallet’s secure element and inject it into web forms that use standardized autocomplete attributes. This approach not only speeds up checkouts for travel bookings, car rentals, and visa applications but also reduces typing errors that can lead to failed transactions or flagged documents.
What’s New: Passports, Licenses, and Travel Numbers
The new autofill logic extends beyond the typical “address” and “payment” categories to encompass three distinct identity buckets:
- Passport data: number, issuing country, expiration date, and name as it appears on the document.
- Driver’s license: license number, issuing state or province, and expiration.
- Known Traveler Number (KTN): the identifier used in programs like TSA PreCheck, Global Entry, or NEXUS.
- Flight information: confirmation numbers, seat assignments, and itinerary details pulled from Wallet’s saved boarding passes.
- Vehicle registration: plate number, VIN, and make/model.
When a website requests any of these fields using modern HTML autocomplete tokens (e.g., autocomplete="passport-number", autocomplete="drivers-license", autocomplete="ktn"), Chrome will present a dropdown menu with matching entries from the user’s Google Wallet. Tapping the entry triggers a biometric authentication prompt before the data is populated. Importantly, the feature is opt-in: users must manually add documents to Google Wallet and grant Chrome permission to access them. Nothing is shared without explicit consent.
How It Works: Google Wallet as the Secure Vault
Behind the scenes, Google Wallet acts as a digitally signed, hardware-backed vault on both Android and iOS. On Android, sensitive document data can be stored in the Secure Element or backed by the Titan M security chip; on iOS, it uses the device’s Secure Enclave. When a user adds a passport or driver’s license to Wallet—either by scanning the physical document or importing from a partner app—the information is encrypted and tied to their Google account, but only the device(s) with the corresponding biometric key can decrypt it.
When Chrome encounters an autofill-able identity field, it sends a request to the Wallet service, which returns one-time tokens for the requested fields. The user must then authenticate using their device’s biometric mechanism: on Android, that’s fingerprint or face unlock; on iOS, Face ID or Touch ID. Only after successful authentication does Chrome fill the form. The plaintext data never leaves the secure memory of the Wallet service, and the website receives only the necessary values. Google does not store a copy of the biometric template, and the entire process adheres to FIDO2 and WebAuthn principles for phishing-resistant authentication.
When and Where to Expect It
The initial rollout is mobile-only: Android devices running Chrome 126 or later and iPhones running iOS 20+ (or whatever the equivalent version will be in late 2026). Google has not yet announced a timeline for desktop browsers, but a Chrome support document hints that the feature could arrive on Windows and macOS later in the year, provided the desktop Wallet integration matures. In the interim, users who rely on Chrome across devices will benefit from the fact that autofill entries for addresses and payments already sync. However, identity document syncing will be more restricted—likely limited to devices with biometric sensors to meet Google’s security bar.
Much will depend on regional availability of digital ID support in Wallet. In the U.S., several states already allow driver’s licenses to be stored in Google Wallet, and Apple Wallet has similar programs. Airline and hotel apps that integrate with Wallet already pass frequent-flyer numbers and booking references, meaning the autofill feature could piggyback on existing Wallet data that many users already have. Known Traveler Number support is particularly straightforward, as it is essentially a text string that can be safely stored per user profile.
Privacy and Security Considerations
Storing government-issued IDs digitally invariably raises privacy concerns. Google emphasizes that all identity data remains on device and is only accessible after biometric verification. The Wallet ecosystem does not share the actual document images unless explicitly required by a verifier, and the autofill system transmits only individual fields—never a full copy of the document. Users can review, edit, or remove any autofilled entry at any time via Chrome’s settings menu or the Wallet app.
Skeptics will note that no system is impervious, and a compromised device could theoretically leak decrypted data. To mitigate this, Google enforces the use of verified boot and requires devices to pass integrity checks before allowing access to the secure element. On Android, this means SafetyNet (or, by 2026, the more robust Play Integrity API) must attest the device hasn’t been rooted or tampered with. iOS devices similarly require that the user has a passcode set and an active Apple ID with two-factor authentication. For corporate users, Google also plans to support managed profile restrictions so IT administrators can disable autofill of identity documents for work profiles.
The Competitive Landscape
Google isn’t alone in pushing the envelope on digital identity. Apple’s Safari has offered similar autofill for contact info, payment cards, and even one-time codes for years, and iOS 17 extended Identity AutoFill to support driver’s licenses in supported states. Microsoft Edge, Chrome’s closest desktop competitor, has a robust password manager and payment autofill, but lacks the tight integration with a digital wallet. Edge relies on Microsoft Wallet (which stores loyalty cards and Microsoft Points) but hasn’t yet announced plans for passport or license storage. Microsoft’s Authenticator app supports verified IDs and digital cards, but those aren’t yet directly bridged into Edge’s autofill. Thus, Google’s move puts Chrome ahead in the race to become the de facto identity browser for mobile users.
For users who juggle multiple browsers, the fragmentation could be annoying: a passport added to Apple Wallet won’t auto-populate in Chrome unless Google builds a bridge (unlikely, given the platform rivalry). On Android, however, Chrome’s dominance means that the vast majority of mobile users will see immediate benefits. And because many travel sites are optimized for Chrome’s autocomplete model, adoption could be swift.
What This Means for Chrome on Windows
While the announcement centers on Android and iOS, the implications for Chrome on Windows are significant. Chrome syncs most autofill data across devices when the user enables the “Sync everything” option, but payment and address syncing have historically been siloed behind additional consent. Google’s privacy framework for the new advanced autofill suggests that sync might be disabled by default for identity documents, or at least require a separate explicit opt-in. However, once a user has stored their passport and license in Google Wallet, it wouldn’t be technically challenging to surface those entries on the Windows version of Chrome—provided the desktop Wallet app or an equivalent web-based Wallet manager exists. Google currently offers wallet.google.com for viewing passes and transactions, but it does not yet allow editing of digital IDs. A future update could bridge that gap, making identity autofill available on any desktop Chrome that is signed in and passing device integrity checks.
Windows Hello integration would be a logical next step. Microsoft already allows websites to leverage Windows Hello biometrics for authentication; a similar API could bridge Wallet and Chrome, making the biometric unlock flow seamless on Windows laptops with fingerprint readers or IR cameras. Until then, Windows users will have to rely on synced passwords and addresses, while mobile users enjoy the full suite.
Travelers Rejoice: Practical Use Cases
For frequent travelers, the new autofill promises to eliminate a major pain point. Consider booking an international flight: a user typically needs to enter their full name (as on passport), passport number, expiration date, issuing country, and sometimes a redress number or KTN. With traditional autofill, many of these fields would be left blank or require manual input. With the new system, Chrome detects the fields and offers to fill them from the saved passport and KTN entries—all after a quick fingerprint scan. Car rentals become simpler too, as driver’s license and vehicle details can be filled in one go. Travelers enrolled in TSA PreCheck or Global Entry will appreciate the automatic KTN insertion, avoiding the common mistake of forgetting to add the number and losing out on expedited screening.
Even mundane tasks like updating personal information on a banking site or verifying identity for financial services can benefit. In many countries, proof of identity requires a driver’s license or passport number; having that data instantly available reduces friction and the temptation to store sensitive documents in insecure notes apps or email drafts.
Developer Adoption and Web Standards
For autofill to work, websites must use the correct autocomplete attributes in their HTML forms. The WHATWG HTML Living Standard already defines a rich set of autofill detail tokens, including autocomplete="passport-number", autocomplete="passport-issue-country", autocomplete="one-time-code", and many others. Google’s own Chrome Platform Status page has been tracking the implementation of these tokens, and the new roll‑out marks the practical activation of several previously dormant attributes. Developers who have already adopted the standard will see instant compatibility; those who haven’t will need to update their forms to benefit. Google is expected to release updated documentation and a developer blog post to encourage adoption, especially among travel and mobility companies.
Moreover, because the feature relies on Wallet rather than a proprietary API, any browser or app that integrates with Google Wallet could theoretically tap into the same data. This opens the door for third-party Android browsers like Firefox or Brave to offer similar functionality if they choose to integrate with Google’s Wallet SDK. That interoperability could be a boon for the broader web, as it decouples the convenience of autofill from a single vendor’s browser.
A Step Toward Digital Identity
Beyond convenience, the enhanced autofill is part of Google’s broader push toward a digital identity ecosystem. Google Wallet already supports digital driver’s licenses in a handful of U.S. states, and the company has been working with the ISO 18013-5 standard for mobile driving licenses. By bridging these credentials directly into the browser, Google is effectively turning Chrome into a identity agent—one that can present verifiable credentials to relying parties without exposing raw private keys. This mirrors the vision of decentralized identity frameworks like W3C Verifiable Credentials, though Google’s implementation is more centralized. It’s a pragmatic step that balances security with usability, and it could pave the way for browser‑based attestations of age, residence, or vaccination status.
For now, though, the focus is squarely on travel and identity documents. As the feature rolls out to millions of Android and iOS devices over the summer of 2026, the real test will be adoption by websites and user trust. If successful, it may not be long before Chrome users wonder how they ever manually typed a passport number.