Security

Passkeys Explained: Why Your Fingerprint Is Not Sent to the Website

Your phone scans your fingerprint to unlock a passkey. Here is why websites never receive that biometric data — and how passwordless sign-in works.

You open a website, select “Sign in with a passkey,” and your phone asks for your fingerprint.

Seconds later, you're signed in.

It feels like the website has just authenticated you using your fingerprint. But something more interesting happened behind the scenes: the website never needed to receive your fingerprint at all.

Passkeys use cryptography to replace passwords with a different authentication process. Understanding that process can help you decide when to use them and how to protect your accounts.

What actually happens when you create a passkey?

When you register a passkey with a website, your device or credential manager creates a cryptographic key pair.

The pair contains two different keys.

The private key is protected by your device or passkey manager. The public key is registered with the website.

The public key can verify cryptographic signatures, but it cannot practically be used to reconstruct the private key.

When you sign in later, the website sends a fresh challenge. Your device signs the challenge using the private key, and the website verifies the response using its stored public key.

The password never needs to be typed, and the website does not need to store a password equivalent.

This mechanism is explained in Google's official passkeys documentation.

So where does your fingerprint go?

Your fingerprint, face scan or device PIN is used locally to authorize access to the passkey.

The biometric information is not transmitted to the website as part of the passkey authentication process.

In fact, biometrics aren't mandatory. A compatible device can authorize passkey use with a PIN or another supported screen-unlock method.

The website receives a cryptographic authentication response, not an image of your fingerprint.

The FIDO Alliance confirms that biometric processing remains on the user's device.

That distinction matters because passkeys aren't simply passwords replaced with fingerprint uploads. They're a different authentication architecture.

Why passkeys resist phishing

Imagine receiving a message containing a link to a convincing imitation of your email provider's login page.

With a traditional password, you might accidentally type your credentials into the fake website.

An attacker could then attempt to use those credentials on the legitimate service.

Passkeys work differently.

A passkey is associated with a particular website identity, called a relying party ID.

The browser and operating system enforce rules about which website can request that credential.

For example, a passkey created for example.com cannot ordinarily be used by a deceptive website at examp1e.com.

MDN's passkey security guide explains how relying party IDs and origin restrictions protect against this type of phishing.

This doesn't mean passkeys prevent every online scam. Attackers can still exploit compromised devices, insecure account recovery procedures or other weaknesses.

But passkeys remove a major risk associated with typing reusable passwords into fraudulent websites.

What happens when you lose your phone?

This is one of the most important practical questions.

There are two broad categories of passkeys.

TypeHow it works
Synced passkeyCan be securely synchronized through a compatible passkey manager across supported devices
Device-bound passkeyRemains associated with a particular device or hardware security key

If your passkeys are synchronized through a supported manager, you may be able to recover access after signing in to that manager on another device.

However, this depends on the provider, account recovery settings and compatible devices.

A device-bound passkey may require another registered credential or a recovery method if the original device is lost.

Before relying entirely on passkeys, review the account's recovery options. For important accounts, consider registering more than one supported authentication method.

Can your phone sign you in on a laptop?

Yes, on compatible devices and browsers.

For example, a website on your laptop may offer the option to use a passkey stored on your phone.

The browser can display a QR code. You scan it using your phone, approve the authentication locally and complete the sign-in.

The process can use Bluetooth-based proximity verification to help establish that the devices are near each other.

Google documents this cross-device experience in its passkey use-case guide.

You don't necessarily need the same operating system on both devices.

What developers need to know

For developers, passkeys are built around the Web Authentication API, commonly called WebAuthn.

A website must generate secure challenges, register credentials, store public keys and verify authentication responses.

The server must also validate details such as the expected origin, relying party ID, challenge and signature.

Simply adding a fingerprint button to a login page does not implement secure passkey authentication.

Google's server authentication guide explains the necessary verification steps and recommends established server-side libraries.

For existing websites, a gradual transition is usually more practical than immediately removing every other sign-in method. Users may still have older devices or need account recovery.

Should you switch to passkeys?

For services that support them, passkeys offer meaningful advantages over reusable passwords, particularly against credential phishing.

However, account security still depends on device protection, passkey-manager security and recovery procedures.

Start with an important account that supports passkeys. Register the credential, test sign-in on your usual devices, and verify that you understand how to regain access if your phone is lost.

The real innovation isn't signing in with a fingerprint. It's proving your identity without handing the website a reusable secret.

Sources

← All articles