Chrome 154 brings Google’s Email Verification feature to Android. Participating websites can now confirm that you own an email address through the browser itself. That replaces the usual confirmation link or one-time code. Google announced the change on its Chrome Developers blog on October 5, writing that “Starting in Chrome 154, Chrome for Android supports email verification.” The feature has been running as a desktop origin trial since Chrome 150.
How Chrome’s Email Verification works on Android
The idea is to remove the tab-switching ritual from account signups. Chrome acts as the go-between. The site asks for proof of your address, and your email provider vouches for it through Google’s protocol. You never open your inbox.
That handoff needs three pieces to line up:
- The website — acting as the verifier, it has to implement Google’s protocol
- Your email provider — acting as the issuer, it has to support the protocol separately
- You — you must already be signed in to that email provider inside the browser
In other words, this will not work everywhere on day one. Until both halves of a site-and-provider pairing are on board, you are back to the confirmation email.
Where the setting lives
On Android, the controls sit under Settings > Addresses and more > Verified Email. Inside is a toggle labelled Automatically confirm your emails. It decides whether Chrome hands over that confirmation without asking you each time.
That toggle deserves a look rather than a shrug. A manual one-time code is a deliberate act. You see the request and choose to complete it. Automatic confirmation moves that decision into the browser’s hands. That is a genuinely different trust model, so it is worth knowing which mode your browser is in.
The parts still in flux
This release is not a finished product. Google notes multiple backwards-incompatible changes in Chrome 154 for both verifiers and providers. That is a developer-facing warning that the specification is still shifting. Chrome 154 also adds third-party origin trial support. Sites can now embed verification through an identity SDK rather than wiring it up themselves.
One more point of confusion is worth clearing up. Android has its own separate Verified Email system for apps, built on digital credentials. That is a different feature from this browser one. Google says it is working to make the two more consistent, but today they are not the same thing.
For more Chrome and Android platform context, see our coverage of the UK regulator’s push for a yearly search choice screen. We have also reported on ChromeOS updates ending in mid-2034.
Source: Google Chrome Developers
