Skip to main content
  1. Home
  2. Phones
  3. Android
  4. Mobile
  5. Social Media
  6. News

WhatsApp’s fingerprint unlock feature is now on Android

By
Add as a preferred source on Google

WhatsApp for Android now lets you unlock the app with your fingerprint on supported handsets.

The security feature has been available for compatible iPhones since February 2019, with iOS users also able to use Face ID to unlock the app. Face ID isn’t yet an option for WhatsApp’s Android users.

Recommended Videos

The new fingerprint feature means that after unlocking your handset, when you go to open WhatsApp you’ll be asked to press your finger on the phone’s sensor to enter the messaging app.

Yes, it’s an extra step, and yes, you’ll keep forgetting you’ve enabled it when you open the app expecting the main screen to appear, but the feature offers extra peace of mind for anyone keen to keep their chats and other WhatsApp data from prying eyes.

How to enable fingerprint unlock

To enable the new fingerprint unlock feature, first make sure you have the latest version of the app on your device. Then, tap Settings > Account > Privacy > Fingerprint lock. Next, turn on Unlock with fingerprint, and then confirm your fingerprint.

The setup screen within settings lets you choose whether to have the feature kick in immediately after you leave the app, or a minute after you leave, or only when you’ve been away for at least 30 minutes.

You’ll also see a button that lets you choose how much content to show in message notifications, in other words, whether you want to see a preview of the sender and message text when a notification comes through.

In a blog post announcing the new security feature, WhatsApp confirmed that users will still be able to answer calls if the app is locked.

Co-founders Jan Koum and Brian Acton launched WhatsApp in 2004.

In 2014, Facebook acquired the company for a colossal $19 billion, but then, amid reported tensions with its new owners over plans for the messaging app, Acton and Koum decided to leave WhatsApp in 2017 and 2018, respectively.

New to WhatsApp? Check out Digital Trends’ handy guide on how to get the most out of it.

Trevor Mogg
Trevor Mogg
Contributing Editor
Not so many moons ago, Trevor moved from one tea-loving island nation that drives on the left (Britain) to another (Japan)…
Topics
TSMC might set up a price hike that could come straight for your next phone, laptop, or tablet
Here's what TSMC's rumored 10% chip price increase actually means in dollar terms, and why your next phone or laptop could end up costing more.
TSMC Fab

My wallet flinched the second I saw the words "TSMC" and "price increase" in the same headline, and honestly, yours should too.

Turns out the company behind the silicon powering basically every flagship device out there, including Apple’s A-series and Qualcomm’s Snapdragon processors, is reportedly about to make all of it a little pricier.

Read more
Samsung’s free storage doubling for preorders is gone in Austria, and the replacement isn’t as sweet
Samsung's free storage doubling deal might just be history.
The back of the Galaxy Z Fold 7

If you've pre-ordered a Samsung foldable purely for the free storage bump, tomorrow's Unpacked event might sting a little.

For years, pre-ordering a new Galaxy meant automatically getting double the storage at no additional charge. Buy the 128GB model, walk away with 256GB for the same price. The same applied to the 256GB and 512GB models. However, that might change at the upcoming Galaxy Unpacked event. 

Read more
Apple fixes Hide My Email bug that exposed users’ real email addresses
Here's how Apple's Hide My Email flaw leaked real addresses for over a year, and why it only got fixed once the story went public.
apple-merging-sign-in-with-apple-hide-my-email-icloud+

Turns out the "Hide" part of Hide My Email wasn't doing its job quite as advertised, something that I covered early in July. Security researcher Tyler Murphy reported the flaw in June 2025, but despite Apple claiming it was resolved in March 2026, independent tests confirmed it remained exploitable, at least until July 3, 2026.

So how did this bug actually work?

Read more