Privacy & Security

Passkeys in Chrome, Edge and Firefox: How They Work and How to Start Using Them

What passkeys are, where Chrome, Edge and Firefox store them as of November 2026, how sync and phone sign-in work, and a safe way to switch your accounts over.

Passkeys are the most important change to logging in since two-factor authentication. They replace passwords with a cryptographic key pair that lives on your devices. You unlock them with your fingerprint, face or device PIN, and they can’t be phished, reused or leaked in a website breach.

They’re also confusing at first, mostly because where your passkey is saved depends on your browser, operating system and password manager. This guide explains how it works in Chrome, Edge and Firefox as of November 2026.

How a passkey works, in plain terms

When you create a passkey for a website:

  1. Your device creates two keys. The private key stays with you, stored in a password manager or your device’s secure hardware. The public key goes to the website.
  2. When you sign in, the website sends a random challenge. Your device signs it with the private key after you unlock it with a fingerprint, face or PIN.
  3. The website checks the signature with the public key. No secret ever crosses the network.

Two consequences matter in practice:

  • Phishing doesn’t work. A passkey is tied to the real website’s domain, so a fake login page on a lookalike domain simply can’t use it.
  • A breach of the website doesn’t leak anything useful. The site only stores your public key.

Where your passkeys live

Where you create it Where it’s stored Syncs to
Chrome (signed in) Google Password Manager Your other devices signed in to the same Google account
Edge on Windows Microsoft Password Manager (Edge 142+) Your other Windows devices signed in with the same Microsoft account
Firefox Your operating system’s passkey store or a third-party password manager Depends on that store
Any browser with Bitwarden, 1Password etc. That password manager’s vault Everywhere that manager runs
Phone (iPhone/Android) iCloud Keychain / Google Password Manager That ecosystem

A few details from official sources:

  • Edge added passkey saving and syncing in Microsoft Password Manager in late 2025. On a new device you unlock synced passkeys with a password manager PIN (Microsoft Edge Blog).
  • Firefox supports creating and using passkeys, but doesn’t have its own synced passkey store. It relies on your operating system or a password manager extension.
  • Password manager extensions can intercept passkey prompts in any browser and save the passkey in their own vault. That’s often the simplest choice if you use several browsers. See our password manager comparison.

Signing in on a computer that doesn’t have your passkey

You don’t need your passkey on every device. When a site asks for a passkey on a computer that doesn’t have it, choose the option to use a phone or tablet. The browser shows a QR code. Scan it with the phone that holds your passkey, confirm with your fingerprint or face, and you’re signed in. Bluetooth is used to check the phone is physically nearby, which stops remote attackers from abusing this flow.

This is ideal for a borrowed or shared computer. Nothing is saved on it.

Setting up your first passkeys

Start with your most important accounts, typically your email and your Google, Microsoft or Apple account, because those can reset everything else.

  1. Sign in to the account normally.
  2. Go to its security settings and look for Passkeys (sometimes under “Sign-in methods” or “Two-step verification”).
  3. Choose Create a passkey. Your browser or password manager asks where to save it. Pick the place you’ll have with you, ideally one that syncs.
  4. Confirm with your fingerprint, face or PIN.
  5. Keep your recovery options. Leave a second sign-in method in place, such as a second passkey on another device or ecosystem, a hardware security key, or recovery codes stored safely.

Most sites let you register several passkeys. Having one in your phone’s ecosystem and one in your cross-browser password manager is a robust setup.

Managing passkeys in each browser

  • Chrome: open Google Password Manager (chrome://password-manager). Passkeys appear alongside passwords for the site, where you can view or delete them.
  • Edge: open Settings → Passwords. Saved passkeys appear in Microsoft Password Manager.
  • Firefox: passkeys are managed by whichever store holds them, such as your operating system’s settings or your password manager.

Deleting a passkey from your manager doesn’t remove it from the website’s account settings. Remove it there too, so the account doesn’t list a key you no longer have.

Common questions

Do passkeys replace two-factor authentication? For most sites, yes. A passkey already combines something you have (the device) with something you are or know (biometric or PIN), so sites usually skip the extra code.

What if I lose my phone? If your passkeys sync (Google, iCloud, Microsoft or a password manager), they’re restored when you sign in on a new device. That’s why the account protecting your passkeys deserves the strongest protection you have, plus recovery codes stored offline.

Can an extension steal my passkeys? Passkeys are designed so the private key isn’t exposed to web pages. But a malicious extension with broad access could still interfere with what you see and type on a page, so the usual extension safety checks still apply. Install password manager extensions only from the vendor’s official link.

Should I delete my passwords after adding a passkey? Not immediately. Many sites keep the password as a fallback. Once you’re comfortable, some sites let you remove the password entirely. Do that only after confirming your recovery options work.

The bottom line

Passkeys are already supported by most major services and every major browser. Add one to your email account this week, test signing in from a second device, and move on to banking, shopping and work accounts from there. It takes a few minutes per account and removes the most common way accounts get stolen: typing a password into the wrong page.

Keep reading