Passwordless Future: A Comprehensive Passkeys FAQ

What is a passkey and how does it work?

Passkeys are a form of authentication that allow you to quickly create and sign in to accounts – without having to use a less secure password. This single-step, secure login method replaces traditional authentication methods, as well as the two-factor authentication (2FA) process. Even better, with passkeys, you’ll never create a weak password again, because you’ll never need to create a password again.

Do passkeys replace physical hardware keys, like Yubikeys?

A modern Yubikey can be used as a form of passkey. Specifically, they are what is known as a Security Key or “device-bound passkey” – where the key itself lives on the small device and is never synchronised or backed up. This can make them harder to use than a Synced Passkey, but they can be useful in certain scenarios.

Are passkeys the same as passwordless?

Yes. Because passkeys do not require a password, they are considered a passwordless method of authentication. Note that passkeys are generally safer than other means of passwordless authentication that can be phished more easily.

What’s the best way to use passkeys?

Using a passkey is much simpler than you might think. When you sign up for a new account, instead of creating a traditional username and password (and completing the additional two-step login enrolment), you create a single passkey. That passkey can be coupled with the biometrics on your device (such as a fingerprint scanner) or a PIN if the passkey requires user verification. So when you go to log in to the account, you'll only be required to authenticate via biometrics or PIN to gain entry. Biometrics are only used locally on your device and are never sent to the website.

What is the process for setting up a passkey? How does that process change when I visit a site or app in the future?

When a website or app that previously used a traditional username and password enables support for passkeys, you can often create your first passkey with the click of a button. The process is as easy as unlocking your device. In the background, when you create a passkey, it will generate a pair of cryptographic keys. The first is the public key, which is stored on the website for which you are creating the account. The second is the private key, which is stored on your device or in your Bitwarden Vault. This key pair is protected on your device by your biometric fingerprint or face scan.

What information is required when setting up a passkey?

When you create a passkey for a site, you will first have to log in with your existing username and password. The server will then push a request to your browser to provide specific encryption information. You will then have to approve the request using, for example, biometrics (fingerprint scanner or face unlock) or your device PIN. Upon successful verification, your device will generate the key pair and send the public key to the site. And that's all the information you'll be required to provide when setting up a passkey.

Where are my passkeys stored?

The public key is stored on the website and the private key is stored on your device or with your passkey provider, e.g. your Bitwarden Vault.

From a security perspective, how do passwords and passkeys compare?

Passkeys are more secure than the traditional username/password authentication method for a number of reasons. First and foremost, you won’t be able to use easy-to-crack passwords, such as “password.” Also, 2FA is built into the passkey and the only way someone could access your account would be to have both the private key and your biometric sign-in or device PIN code.

Do I need 2FA with my passkey?

No, because 2FA is built into the passkey that is provided to the website during the sign-in process. Each website may choose to include an additional step for signing in, though most do not.

Can my passkey be hacked?

Nothing is 100% foolproof. However, hacking a passkey would require considerable effort not only to gain access to the device where the private key is stored, but also to break into your device, e.g. by recreating your biometric sign-in (fingerprint or face) or device PIN code. Because of this, passkeys are far more secure than traditional methods.

What happens if I lose my phone? How do I recover my passkey when there’s no password to identify myself?

Passkeys can often sync across your devices; however, not all platforms support this yet. Bitwarden will allow you to store your passkeys in your vault, which is backed up and syncs across all your devices. Should you somehow lose your passkeys, most sites should have recovery options, so you can create a new passkey for your account. This will, of course, be on a site-by-site basis.

What happens if my device is stolen? Can a thief gain access to passkeys in that way?

The only way a thief could successfully use your passkeys on your device is if they can also unlock your device, effectively gaining full access to your data. However, each use of a passkey often requires user verification such as biometrics or re-entering your device PIN, so stealing your device while unlocked would not be enough.

Google recently announced passkey support. Is this the same thing that Bitwarden is announcing?

Partly. Google announced that it has added support for passkey authentication for Google Workspace accounts, meaning users can sign in to their Google Workspace with a passkey instead of their usual password. Similarly, Bitwarden users will be able to access their Bitwarden accounts with a passkey instead of their master password.

Bitwarden also announced that users will be able to save, store and manage registered passkeys associated with the websites and applications they use right within their vaults. So, Google now makes it possible to use passkeys for accounts and Bitwarden is capable of storing passkeys in vaults.

Do I use the same passkey regardless of the browser I’m on, or will each site require a different passkey depending on the browser or device?

The passkeys stored in Bitwarden are synced passkeys, meaning that on any browser where you are logged in to the Bitwarden extension, or where you have the Bitwarden mobile app installed, you can access your accounts using the same passkeys without needing to create new ones. If you don’t store your passkeys in Bitwarden, it will depend on how well the browser integrates with your device OS (where the passkeys are stored).

The growing list of sites that currently support passkeys includes Best Buy, Cloudflare, eBay, Google, Kayak, PayPal and GitHub. A community-sourced Passkey Index is available on GitHub.

Users can use a passkey to access their accounts without a master password for the web app using supported browsers. Passkeys can also be created and stored in Bitwarden vaults for accessing sites that support passkeys.

Can passkeys be used across platforms? If not, are there any issues with having different passkeys depending on the platform you’re using?

There are two types of passkeys: device-bound passkeys and synced passkeys. Device-bound passkeys are limited to the device where they were created. Synced passkeys can be stored inside a passkey provider like Bitwarden and used wherever they are logged in.

Will I be locked into using passkeys if I adopt them?

That will depend on the site or the account. Some sites may choose to offer only passkey authentication, while others may offer traditional username/password authentication or username/password/2FA authentication.

Can passkeys be shared with other trusted individuals?

That depends on the platform. Some platforms, including Bitwarden, make it possible to share passkeys with trusted individuals.

Is there support, such as a live chat representative to speak with if I’m having trouble with my passkey?

That will depend on the site. If a site supports passkey authentication and offers support, they will be able to answer your questions regarding passkey authentication for that particular site.

If I no longer want to use my passkey, can I remove it?

Yes. This will be done in the same way you would remove a password on your device.