Android's Three Biometric Classes Decide What Face Unlock Can Do

Two Android phones can both advertise face unlock and still treat your face very differently. One may use it only to open the lock screen. Another can let it approve a payment, release a saved password, or sign in to a banking app.

The difference is not simply whether the phone has a face scanner. Android grades each biometric implementation as Class 1, Class 2, or Class 3. The class reflects resistance to spoofing and the security of the full biometric pipeline, including where matching happens and how the result reaches the operating system.

Three classes, three different levels of trust

Class 1, previously called Convenience, is allowed to unlock the phone. It cannot connect to Android's BiometricPrompt interface, so apps cannot rely on it as their biometric sign-in method. This is why a basic camera-based face unlock can open the home screen yet leave a finance or password app asking for a fingerprint, PIN, pattern, or password.

Class 2, previously called Weak, can work with BiometricPrompt. An app may accept it for ordinary authentication, but Android does not allow it to release cryptographic keys protected by the Keystore. Developers can also require a stronger method for a sensitive action.

Class 3, previously called Strong, receives the broadest privileges. It can authenticate through BiometricPrompt and work with both time-based and operation-based Keystore keys. That makes it suitable for actions where an app needs a protected key immediately after a successful biometric check.

A phone can have more than one class at once. Its face system might qualify as Class 2 while its fingerprint reader qualifies as Class 3. If an app needs the stronger level, Android can offer the fingerprint even though face unlock works perfectly well on the lock screen.

The percentages describe spoof testing, not everyday odds

Android uses several measurements when assigning a class. One is the Spoof Acceptance Rate, which tests whether a system accepts presentation attacks such as a printed face, a video, a mask, or a replica fingerprint.

Under Android's current framework, Class 3 covers an overall spoof-acceptance range from 0% to 7%. Class 2 spans 7% to 20%, while Class 1 spans 20% to 30%. Secure processing is also part of the decision: Class 2 and Class 3 biometric acquisition, enrollment, and recognition must happen inside a secure isolated environment.

Those percentages are laboratory classifications, not a promise that a random person has a particular chance of unlocking your phone. Test materials, attack methods, sensor design, lighting, and the enrolled user all matter. The useful takeaway is simpler: a lower class receives fewer permissions because Android places less trust in it.

Google Wallet shows the difference clearly

Google Wallet accepts a PIN, pattern, password, or Class 3 biometric for purchase verification. It does not accept Class 1 or Class 2 biometrics for that job. A face unlock that opens the phone may therefore be unavailable when you tap to pay, even though the same phone recognizes you instantly at the lock screen.

Google's own Pixel lineup offers a practical example. Pixel 7 and Pixel 7 Pro face unlock can open the device, but Google says it is not supported for tap-to-pay verification. On Pixel 8 and later models, Face Unlock can also verify the user inside apps and approve purchases. Hardware, algorithms, and the certified implementation matter more than the presence of a front camera.

App behavior can be stricter than the phone's general unlock behavior. A developer may permit Class 2 for a low-risk sign-in, demand Class 3 for an encrypted credential, or allow the device PIN as a fallback. Seeing a different prompt in two apps is not necessarily an error.

Your settings may not show the class name

Android's class system is designed for device makers and app developers, and many phones do not display a simple “Class 3” label in Settings. Manufacturer documentation is the best place to check, but it is often vague. The ability to use a biometric for payments or a protected app is useful evidence, though it is not a universal certification test because each app chooses what it accepts.

Forced credential prompts are also normal. Android permits Class 1 and Class 2 implementations to require the primary credential after up to 24 hours, after four idle hours, or after three failed biometric attempts. Class 3 can allow up to 72 hours before falling back to the PIN, pattern, or password. A manufacturer may ask sooner.

Use Lockdown when convenience should stop

Even a Class 3 sensor is not a substitute for a strong screen-lock credential. Android's Lockdown command temporarily disables fingerprint and face unlocking, hides lock-screen notifications, and turns off Extend Unlock until the device is opened with its PIN, pattern, or password.

On phones using Google's standard controls, press the power and volume-up buttons together, then tap Lockdown. Some manufacturers move or rename the command, so check the device's security settings if it is missing.

For day-to-day use, keep the biometric method that feels quick, but know which jobs it can actually perform. If face unlock cannot approve a sensitive action, the phone is not being inconsistent. Android is applying the trust level assigned to that specific sensor and asking for a stronger proof when the action carries more risk.

Share: