
ZDNET's key takeaways
- Passkeys let you sign in without typing or remembering passwords.
- Unlike passwords, they're resistant to phishing.
- Syncable passkeys make secure sign-ins easy across devices.
Over the past year or so, passkeys have hit the mainstream. The rate of adoption for this technology has been remarkable, and it shows no sign of slowing down. If your experience is like mine, you're probably invited to save a new passkey at least once or twice a week.
All told, I now have at least 40 saved passkeys. I can use those passkeys to skip the password prompt completely and sign in with biometrics (face or fingerprint) at dozens of websites, including mainstream shopping destinations like Costco, Target, Amazon, and Walmart, as well as more technical sites like Dell, Adobe, and Dropbox. The company that manages my domain name registrations uses passkeys, as does the power company, my credit union, and my physician's office.
But I still hear from readers who don't quite understand what a passkey is, how it works, or why it's better than a password.
After a lengthy online exchange on the subject with a friend who finally achieved an "Aha!" moment, I think I figured out why the topic is so confusing: A passkey is not a tangible thing -- it's an abstraction. As a result, most attempts to explain the technology get bogged down in technical details.
Even the least technical person you know can tell you what a password is -- some combination of letters and numbers, with maybe a symbol thrown in. You can create your own password using a common word or a name or a date, and you can even write it down on a sticky note. If you're like most people, you regularly reuse the same password, or some variation of it, even though you know that's probably a bad idea.
A passkey, on the other hand, is difficult to describe. If I tell you it's a secure digital credential generated from a public key and a private key, can you form a mental image to go with those words? Probably not. Burying the definition in more technical details won't help.
But I think we can get there, together, in plain (mostly) non-technical language without a bunch of jargon, just by going through the questions I keep hearing from readers.



