Passkeys or passwords — what to choose when building login from scratch

The "passkeys or passwords" debate is usually about convenience: one tap is faster. True, but that's not the point.
The point is what sits in your database. With passwords you store a dangerous thing and guard it forever. With passkeys there's nothing to store. Let's go axis by axis.
The fundamental difference
When someone signs up with a password, they hand you a secret and you promise to protect it. You don't store the password itself but its hash — still material that can be hauled away and brute-forced.
When someone signs up with a passkey, they hand you a public key. The secret stays with them. Your database stops being loot.
Compared by criteria
What the server stores. Password: a hash you must salt and compute properly. Passkey: a public key you could print and hang on the wall.
A database leak. Passwords: disaster. Weak ones fall in hours, and people reuse them elsewhere — so it's not only your product that suffers. Passkeys: a stolen database can't log anyone in, there are no private keys in it.
Phishing. A password can be typed into a lookalike site — and on a bad day even careful people do it. A passkey is bound to the domain: on a fake page the browser simply finds no key. Protection by mechanics, not by vigilance.
Losing a device. A password lives in your head or a manager, the device is irrelevant. A passkey is tied to a device or a cloud set; a synced one returns with your Apple or Google account, a device-bound one doesn't.
Sign-in convenience. Password: recall, type, occasionally reset. Passkey: one tap, nothing to type, nothing to reset.
What you have to maintain. Passwords come with email resets, attempt limits, complexity rules, breach checks and 2FA. With passkeys most of that just disappears from your project.
Where passkeys honestly lose
Three real pits that promo posts rarely mention.
Recovery. Forgot a password — reset it by email. Lost every device holding your passkeys — and without a backup route you're locked out. A fallback way in is mandatory.
Ecosystem lock. Synced passkeys live in iCloud Keychain or Google Password Manager. Your users effectively park the keys to your service inside someone else's account, and moving between ecosystems is still awkward.
Shared and borrowed devices. A family account, a coworking computer, a managed work laptop — a password is still simpler there. Cross-device sign-in over QR saves the day but needs explaining.
Who should pick what
Building something new — make passkeys the primary method. Make the fallback a one-time email code or a magic link, not a password. That way you never grow a password database you'd have to defend for years.
Already have an app with passwords — add passkeys alongside. Don't break the existing login and don't force a migration. Offer to add a passkey after a successful sign-in: roughly half will accept, and that's half your accounts that can no longer be phished.
Enterprise audience with old devices — passwords plus 2FA for now. Add passkeys as an option and watch the share grow.
What you definitely shouldn't do is invent your own login scheme. Everything above is already handled by off-the-shelf auth services; wiring one up is covered in how to add login to your app.
How to tell whether the switch worked
If you're adding passkeys to a live product, you can't decide by vibes. Watch three numbers.
Share of accounts with at least one passkey. The headline metric: while it's low, you're running both systems and saving nothing.
Success rate of sign-ins per method. There's often a surprise here: passkeys usually win by a wide margin, because there's nothing to forget or type. If yours go the other way, the interface is almost always to blame, not the technology.
Support tickets about "can't log in". Passwords produce a steady stream of reset requests. Passkeys produce a different case — rarer but heavier: lost devices. Count them separately, or you'll conclude things got worse.
A sensible threshold for dropping passwords: consistently more than half of active accounts on passkeys, and fewer tickets than before.
FAQ
Are passkeys safer than a password manager plus 2FA?
On phishing — yes, noticeably. A password manager can still fill a password on a lookalike domain if the person insists. A passkey doesn't offer that possibility at all.
Should I require 2FA on top of a passkey?
Usually no. A passkey already combines the device and biometrics, which is two factors. Adding an email code on top is friction without a payoff.
Will passwords disappear soon?
Not soon. For the next few years the real choice isn't either/or but "passkeys first, password as the fallback" — with that fallback used less and less over time.
The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.





