AndroidLab From retrocomputing to AI, through Android.
Chrome Tests Biometric Password Fill on Android

Chrome Tests Biometric Password Fill on Android

by

Google is testing a feature that adds a biometric check — typically a fingerprint scan — before Chrome for Android fills saved passwords. The idea has surfaced before and was pulled before reaching stable, but a new flag in the latest Chrome Canary build suggests Google is giving it another try.

What is biometric password autofill?

Right now, when Chrome on Android has a saved password for a site, tapping the login field shows a “Use saved password?” prompt. One more tap and the credentials fill in — no further authentication required. That convenience is also a risk: anyone holding your unlocked phone can log into your accounts.

The biometric autofill feature adds a mandatory fingerprint scan between tapping the prompt and actually filling the credentials. Fail the biometric check, and the password stays hidden.

How to test it on your phone

The feature is only available in Chrome Canary (the most experimental build) and requires manually enabling a flag. Here’s the procedure:

  1. Install Chrome Canary from Google Play if you haven’t already.
  2. Open the browser and type chrome://flags in the address bar.
  3. Search for “Biometric reauth for password filling” in the flags list.
  4. Toggle the flag to Enabled.
  5. Tap Relaunch at the bottom of the page.
  6. Visit any website where Chrome has a saved password and tap the login field.

If the feature works on your device, tapping “Use saved password?” triggers the phone’s biometric prompt before Chrome fills the credentials. In testing on a Pixel 8, the flag was visible but the biometric prompt didn’t trigger, suggesting the backend rollout is still limited or tied to specific server-side configs.

What this changes for your security

For security-minded users, the value is obvious: an extra layer that prevents one-tap access to all saved passwords when someone borrows your phone. It’s not a replacement for a master password or a PIN — the biometric check sits after the phone is already unlocked — but it closes a significant gap in Chrome’s current autofill model.

The tradeoff is speed. Every login now requires a biometric scan. On devices where fingerprint sensors are fast and reliable, the delay is under a second. On phones with optical readers or poorly calibrated sensors, it could become annoying.

Previous attempts and what to expect

This isn’t Google’s first try. The same flag appeared in Chrome Dev and Canary in August 2025, then disappeared before reaching stable. The feature resurfaced now with the same flag name, which suggests Google is iterating rather than starting from scratch. Whether it reaches stable this time depends on testing feedback and, presumably, Android platform integration maturity.

The flag is visible in Chrome Canary 157.0.8083.0 and later. The feature works for some testers, but not all — a sign that Google is still tuning the rollout. There’s no guarantee it ships this year, but the fact that the flag has returned is a stronger signal than last year’s quiet removal.

Cosa cambia davvero

If and when this reaches stable, it means every autofilled password on Chrome Android requires a biometric check. That’s a meaningful security upgrade for anyone who hands their unlocked phone to a colleague, family member, or friend — the passwords won’t fill without a fingerprint. The same applies to lost or snatched phones that are still unlocked. The practical impact depends on implementation quality: a reliable, fast sensor makes it a minor friction; a flaky one makes users disable the feature.

In breve

  • Chrome Canary on Android now has a flag for biometric password autofill: fingerprint before filling.
  • To test: install Chrome Canary, enable Biometric reauth for password filling in chrome://flags, relaunch.
  • The feature works for some testers but not all — backend rollout is still limited.
  • Google tested and pulled the same feature in 2025; its return suggests renewed commitment.
  • If stable, it adds a security layer for unlocked phones without replacing the device unlock PIN.
  • Related: Chrome Tab Handoff: Keep Scroll and Form Progress and Chrome Updates Every Two Weeks on Android.

Primary: Android Authority (original reporting), Leopeva64 (flag discovery and screenshot evidence). Chrome Canary build verified independently.

AUTHOR

IT specialist, developer and systems engineer with a long history across code, Linux servers, retrocomputers and e-learning platforms. On AndroidLab he brings a technical, pragmatic eye: less brochure smoke, more attention to infrastructure, usability, privacy, updates and the real consequences of manufacturers' choices.

Leave a Comment