Explainers · Explainer
What Is a Passkey? A Plain Explanation
Short answer
A passkey is a sign-in credential that replaces your password with a key pair held on your device. Your device keeps the private key and the site keeps only the public key. You sign in with your fingerprint, face scan, PIN, or pattern, and the key only works on the real site, so a fake login page cannot use it.
Key takeaways
- A passkey replaces your password with a key pair: the private key stays on your device and the site stores only the public key.
- You sign in with your fingerprint, face scan, PIN, or pattern, the same step you use to open your device.
- A passkey only works on the site it was made for, so a look-alike login page cannot reuse it.
- Synced passkeys copy to your other devices through a provider, while device-bound passkeys stay on one device.
- WordPress needs a passkey plugin and HTTPS, and you should keep password login until every admin has a working passkey.
- In a 2024 FIDO Alliance survey, 53% of people had enabled passkeys on at least one account.
What is a passkey?
A passkey is a sign-in credential that replaces your password with a key pair held on your device.
The FIDO Alliance defines a passkey as an authentication credential based on FIDO standards. You keep it on your phone or computer, or in a hardware security key.
You sign in with the same step you use to open your device, such as a fingerprint, face scan, PIN, or pattern. You type nothing and remember nothing.
With passkeys, you no longer need to enter a username and password, the FIDO Alliance says. That is the plain idea: the device proves who you are, and the site checks that proof.
How does a passkey work when you sign in?
A passkey works by signing a fresh challenge from the site with a private key that never leaves your device.
When you create a passkey, your device makes a pair of keys. The private key stays with your passkey provider, and the public key goes to the site server.
web.dev explains that the private key issues a signature after user verification on the valid domain. The site then checks that signature with the public key it stored.
The steps look like this:
- You choose to sign in with a passkey on the site.
- The site sends a fresh, one-time challenge to your browser.
- Your device asks for your fingerprint, face scan, PIN, or pattern.
- Your device signs the challenge with the private key.
- The site checks the signature against the public key and signs you in.
No secret travels over the network during sign-in. The site stores a public key, not a password, so a leak of that stored value gives an attacker nothing to sign in with.
Why is a passkey safer than a password?
A passkey is safer because it only works on the real site, and there is no shared secret to steal or reuse.
A password is a secret that both you and the site know. It can be guessed, phished, or leaked in a breach. A passkey has no shared secret.
web.dev states that passkeys use device screen lock methods like biometrics or PINs and reduce phishing risks and credential theft. The private key signs only after verification on the valid domain.
| Risk | Password | Passkey |
|---|---|---|
| Phishing on a fake site | A typed password can be sent to the fake site | The key only signs for the real domain |
| Reuse across sites | One leaked password can open many accounts | Each site gets its own key pair |
| Server breach | Stored hashes can be attacked | The server stores only a public key |
| Forgotten login | A forgotten password blocks sign-in | Your fingerprint, face, or PIN opens the device |
The FIDO Alliance says passwords are responsible for 80% of breaches, as of November 2026. That figure shows why a method with no password to steal changes the risk.
The FIDO Alliance also reports 20% more successful sign-ins with passkeys than with passwords. It cites 6x faster sign-in times from Amazon and a 4x improvement in sign-in success rate from Google.
What is the difference between a synced passkey and a device-bound passkey?
A synced passkey copies to your other devices through your passkey provider, while a device-bound passkey stays on one device.
The FIDO Alliance splits passkeys into these two kinds. Both resist phishing, but they differ in recovery and in what happens when you change devices.
Synced passkeys travel through a provider such as Google Password Manager or iCloud Keychain. When you create one on your phone, it becomes available on your laptop signed in to the same provider account.
Device-bound passkeys never leave one device, including those on a hardware security key. If that device is lost and you have no other passkey or recovery method, you need the site's recovery path.
The FIDO Alliance states that passkey syncing is end-to-end encrypted. That means the provider stores the synced copy in a form it cannot read in plain text.
Which type should you expect?
Most passkeys people create on a phone or laptop are synced passkeys. A hardware security key usually holds a device-bound passkey.
Check your passkey provider settings before you rely on sync. A synced passkey helps only if the same provider account is signed in on your new device.
Where is a passkey stored?
A passkey is stored by a passkey provider, which can be your browser, your operating system, a password manager, or a hardware security key.
The FIDO Alliance says a passkey provider can be a browser or operating system vendor, such as iCloud Keychain or Google Password Manager. It can also be a third-party app, such as 1Password or Dashlane.
web.dev adds that passkeys sync across devices using providers like Google Password Manager and iCloud Keychain. The private key stays with that provider, and the site keeps only the public key.
Your fingerprint or face data is not part of what is stored on the site. The FIDO Alliance says biometric information and processing stay on the device and are never sent to a remote server.
The site sees only proof that the device check passed. That proof is the signed challenge, checked against the public key.
What do you need before you can use passkeys?
You need a device with a screen lock, a current browser, and a site that offers passkeys.
A screen lock is the base. Your fingerprint, face scan, PIN, or pattern is the step that approves each sign-in, so the device must have one set up first.
You also need a secure connection. Chrome for Developers states that WebAuthn methods run only in secure contexts, so apps must run on HTTPS in production or on localhost for local development.
If your WordPress site still lacks HTTPS, fix that first. Our guide to how much an SSL certificate costs explains the price range, and a free certificate is often enough for a small site.
Each site must support passkeys before you can create one there. A passkey for one site does not work on another site, because each credential is tied to one domain.
Chrome for Developers states that every credential is tied to a relying party ID, which is essentially the domain name of the application. A look-alike domain cannot use the same credential.
How do you add passkeys to a WordPress site?
You add passkeys to WordPress with a passkey plugin, because the login form itself does not offer them on its own.
Start with a backup, so you can restore the site if a plugin change goes wrong. See our guide on how to back up WordPress before you install anything new.
Then pick a plugin from WordPress.org and check its page first. Our guide on how to find abandoned WordPress plugins shows the update date, tested-up-to version, and closure notice to check.
One example is Rapls Passkey, a WordPress.org plugin that adds passkey sign-in. Its page says Touch ID, Windows Hello, Face ID, or a security key takes the place of the password, and your server never holds a shared secret.
Rapls Passkey lists WordPress 6.0 or later, PHP 8.2 or later, and HTTPS except on localhost as requirements, as of November 2026. Check the same three items on any plugin you choose, because versions change.
After you install and activate the plugin, register a passkey from your profile screen. The plugin also offers the shortcodes [rapls_passkey_login] and [rapls_passkey_register] for a login button and a management form on a page.
Keep password login turned on while you move across. Rapls Passkey states that password login is never switched off in the free plugin, so nobody gets locked out during the change.
How do you check that passkeys work on your site?
You check passkeys by creating one on a test account, signing out, and signing back in with it.
Use a second account or a test user first, not your main admin account. That way a failed passkey does not block your own access.
Follow these checks:
- Create a passkey on the test account from its profile screen.
- Sign out, then choose the passkey option on the login screen.
- Approve the sign-in with your fingerprint, face scan, PIN, or pattern.
- Confirm you reach the dashboard or the page you asked for.
- Remove the test passkey, then confirm password sign-in still works.
If the passkey button does not appear, check HTTPS first. WebAuthn refuses to run on plain HTTP in production, so a missing certificate is the most common cause.
Also check the plugin page for a closure notice or a stale update date. Our guide on what happens when a plugin is closed on WordPress.org explains what a closure means for updates and downloads.
What happens if you lose the device with your passkey?
If you lose the device, a synced passkey can return on a new device, while a device-bound passkey needs a recovery method.
A synced passkey is the easier case. Sign in to the same passkey provider on a new device, and the passkey syncs to it. The FIDO Alliance says a new device set up with the same provider gets the synced passkeys.
A device-bound passkey does not sync. You need another way in, such as a second passkey on another device, a recovery code, or your password if the site still allows it.
Rapls Passkey states that if you lose a passkey, password login still works, so you can sign in with your password and remove or re-register passkeys from your profile screen. That fallback matters, so do not remove password login until every admin has a working passkey and a recovery path.
Cross-device sign-in can help in the short term. The FIDO Alliance says cross-device sign-in uses Bluetooth Low Energy to verify physical proximity, so your phone can approve a sign-in on a nearby computer.
Register at least 2 passkeys for an admin account when the plugin allows it, on 2 devices. That single step cuts the risk of a lost phone turning into a lost site.
What myths about passkeys are wrong?
The main myths are that a passkey sends your fingerprint to the site, that it works on any site, and that losing your phone always locks you out.
Each myth has a plain correction, and each correction comes from the sources above.
- Myth: the site gets your fingerprint or face scan. The FIDO Alliance says biometric data stays on the device and is never sent to a remote server.
- Myth: one passkey works everywhere. Each passkey is tied to one domain, so a passkey made for one site is not offered on another site.
- Myth: a lost phone always means a lost account. A synced passkey returns on a new device signed in to the same provider, and a password fallback can also restore access where the site keeps one.
- Myth: passkeys are a single company product. The FIDO Alliance says the term passkey is a cross-platform general-use term, not a feature tied to one platform.
- Myth: passkeys remove the need for any recovery plan. You still need a second passkey, a recovery code, or a password fallback, or a lost device can still block you.
A passkey is a FIDO credential, not a brand name. The standard behind it is FIDO2, which the FIDO Alliance describes as WebAuthn plus CTAP, with WebAuthn covering the browser API.
What mistakes should you avoid?
Avoid removing password login too soon, skipping HTTPS, and registering a passkey only on one device.
These mistakes cause most passkey problems on a WordPress site, and each one is easy to prevent.
- Do not turn off password login until every admin has a working passkey and a recovery path.
- Do not try passkeys on plain HTTP, because WebAuthn needs HTTPS in production.
- Do not register a passkey on a staging domain and expect it to work on the live domain.
- Do not skip the backup before you install a login plugin.
- Do not assume a passkey syncs, because a device-bound passkey stays on one device.
Rapls Passkey warns that a passkey is bound to the domain it was registered on, so a passkey registered on staging.example.com is not offered on example.com. Register again on the live site, and treat staging passkeys as disposable.
Also keep the plugin updated and watch its WordPress.org page. A login plugin that stops receiving updates needs a replacement before it becomes a security risk.
Frequently asked questions
Is a passkey the same as a password saved in my browser?
No. A saved password is a secret that can be copied, reused, or leaked. A passkey is a key pair where the private key never leaves your device and the site stores only a public key. You approve each sign-in with your fingerprint, face scan, PIN, or pattern, and the key only works on the site it was made for.
Do I still need a password if I use passkeys?
Often yes, at first. Many sites keep your password as a fallback while you move across, and some WordPress passkey plugins never switch password login off. Keep the password until every account that matters has a working passkey and a recovery method, such as a second passkey or a recovery code.
Can someone steal my passkey from a website database?
No, in the useful sense. The site stores only the public key, which cannot sign anything on its own. The private key stays with your passkey provider on your device. A breach that leaks public keys gives an attacker nothing they can use to sign in as you.
What happens to my passkeys when I get a new phone?
Synced passkeys return when you sign in to the same passkey provider on the new phone, such as Google Password Manager or iCloud Keychain. Device-bound passkeys do not sync, so they stay on the old device. Register a second passkey on another device before you switch phones, so you are not left with one copy.
Do passkeys work on all browsers and devices?
No. You need a device with a screen lock, a current browser, and a site that offers passkeys. Support is now common on current versions of Chrome, Safari, Edge, and Firefox, and on current phones and computers. Older devices and browsers may not offer passkeys, so check the site and your device before you rely on them.
Are passkeys free to use on WordPress?
Creating a passkey itself costs nothing, and several WordPress.org plugins offer passkey sign-in in a free version. You may still pay for a paid plugin add-on, a password manager, or a hardware security key if you choose one. Check the plugin page for its requirements, such as WordPress 6.0, PHP 8.2, and HTTPS, before you install it.
Sources
- FIDO Passkeys: Passwordless Authentication FIDO Alliance
- Create a passkey for passwordless logins web.dev
- Passkeys Orientation Chrome for Developers
- Rapls Passkey – Passwordless Login with WebAuthn WordPress.org
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
