Google Introduces Selfie Video Sign-In for Secure Account Recovery
Google has introduced selfie video as a new sign-in option, expanding a biometric verification feature first tested in Brazil earlier this year. The new method helps users regain access when they cannot use their usual device or standard authentication tools.
Instead of replacing passwords, passkeys, or two-factor authentication codes, the feature works alongside them. As a result, users have another secure way to verify their identity during account recovery.
How the selfie video verification works
Users can enable the feature by opening their Google Account’s Security & sign-in settings and selecting the selfie video option. If their device has a camera, they can complete the setup immediately. Otherwise, they can scan a QR code with a phone to continue the enrollment process.
During setup, users must turn their head as instructed while the camera records a short video. This process helps prevent impersonation attempts, including deepfake videos, and confirms the user is physically present.
Google encrypts the recorded selfie video and stores it securely. Later, if identity verification is required, users record a new selfie video. The system then compares the new recording with the enrolled version to confirm the user’s identity. Additionally, users can delete their stored selfie video at any time through the Video Verification page in their account settings.
Availability and current limitations
However, the feature is not available for every account. Workspace accounts, child accounts, and accounts enrolled in the Advanced Protection Program cannot use the selfie video option at this time.
Google began testing the feature in Brazil in February 2026 before expanding it more broadly this week. Meanwhile, the company has continued adding new identity verification tools, including recovery contacts and biometric security features.
The selfie video sign-in strengthens account recovery by offering another verification method when traditional recovery options are unavailable. Consequently, users gain an additional layer of protection while maintaining access to existing authentication methods.
