Home » Blog » Passkeys Explained: What They Are and How to Set Them Up on Your Accounts

Passkeys Explained: What They Are and How to Set Them Up on Your Accounts

Illustration of a smartphone with a fingerprint symbol and a glowing key, linked to a laptop

Your bank, your email and your shopping accounts keep offering you something called a passkey — and quietly implying your password is no longer good enough. They are right, but the prompts rarely explain what a passkey actually is, where it lives, or what happens if the phone holding it ends up at the bottom of a lake.

This guide fixes that. It explains what a passkey is in plain English, shows how to set up passkeys on your accounts across Google, Apple, Android and Windows, and answers the question that stops most people: what happens when you lose your phone. You do not need to buy an app or a gadget. Everything below uses the phone and computer you already own, and every setup path was checked against the makers’ official support pages in November 2026.

Illustration of a smartphone with a fingerprint symbol and a glowing key, linked to a laptop

Passkeys in 30 Seconds: The Short Answer

A passkey is a digital key pair your device creates for one account: the website keeps a public key, your phone or computer keeps the private key, and you sign in by unlocking your device with your face, fingerprint or PIN. Start with your Google Account — go to its security settings and choose “Create a passkey.”

What Is a Passkey, and How Does It Work?

When you create a passkey, your device generates two mathematically linked keys. The public key goes to the website, which stores it next to your account. The private key never leaves your device — or the password manager you choose to hold it — and is never typed, displayed or sent anywhere.

Signing in works like this: the website sends your device a one-off challenge, you unlock the device with your face, fingerprint or PIN, and the device uses the private key to sign the challenge. The website checks the signature against your public key and lets you in. Unlocking your device is the sign-in — there is nothing to remember and nothing to type.

That design closes the two holes passwords keep falling through. A passkey is created for one exact website domain, so it will not work on a lookalike phishing page — your device checks where it is before signing anything. And if the website is breached, attackers get public keys, which are useless on their own. There is no shared secret to steal, guess or reuse elsewhere. Passkeys are an open standard, built by the FIDO Alliance and the World Wide Web Consortium (WebAuthn) — not one company’s product.

Passkeys vs Passwords vs Authenticator Apps

Illustration comparing a scribbled password note, an authenticator code on a phone, and a fingerprint passkey

Most accounts today offer some mix of three sign-in methods. Here is the honest comparison:

MethodHow you prove it’s youPhishing riskIf the site’s database leaksMain weakness
PasswordTyping a secret you rememberHigh — a fake page can harvest itYour actual secret can leak and be tried elsewhere
Authenticator app codePassword plus a 6-digit code from an appMedium — a fake page can trick you into typing the codeCodes themselves don’t leak, but the password still canAn extra step at every sign-in, and codes can be phished in real time
PasskeyUnlocking your device (face, fingerprint or PIN)Very low — the passkey won’t work on the wrong domainOnly the public key is stored; useless to attackersYour access depends on your device and its sync and recovery setup

A passkey quietly combines two factors in one gesture: something you have (your device) and something you are or know (your face, fingerprint or PIN). That is why sites that accept a passkey usually treat it as a complete sign-in, not as one step of two.

Authenticator apps still matter, though. Wherever an account keeps a password as a fallback — and most still do — that password can still be phished, so the second factor still earns its place. If you haven’t set one up yet, our guide to the best authenticator apps covers the free options.

Where You Can Use Passkeys Today

Support is broadest on the big platform accounts and the money-adjacent services. These are verified on the companies’ own pages:

  • Google Account — the setting lives at myaccount.google.com/signinoptions/passkeys.
  • Microsoft account — added from the account’s Advanced security options page, as the Windows steps below describe.
  • Amazon — in Your Account, open Login & security and choose Set up beside Passkeys. Note that signing in to a different Amazon marketplace (amazon.com vs amazon.co.uk, say) needs its own passkey.
  • PayPal — offered to eligible personal accounts. PayPal creates passkeys through a mobile browser (Safari or Chrome), and its help pages state passkeys are not supported on Windows devices — an unusual restriction worth knowing first.
  • WhatsApp — in the app, Settings → Account → Passkeys. WhatsApp uses it to verify it’s you when you register or re-register your account.

Beyond those, passkey support has reached services such as GitHub, eBay, Best Buy and Kayak, and password-manager makers maintain directories tracking new arrivals. Availability can still vary by country, app version and account type — if a service isn’t offering you a passkey yet, that’s the service’s rollout, not something wrong with your device.

How to Set Up Passkeys on Your Accounts, Platform by Platform

Every path below follows the same shape: sign in the old way once, find the passkey option in the account’s security settings, and confirm with your device unlock. Where the passkey is stored depends on the device you create it on.

On a Google Account

  1. On the device you want to use, go to myaccount.google.com/signinoptions/passkeys and sign in if asked.
  2. Select Create a passkey, then Continue.
  3. Confirm it’s you with your fingerprint, face or screen lock. The passkey is created and listed on that page, where you can also remove it later.

Google’s requirements are modest: a phone running Android 9 or iOS 16 or later, or a computer running Windows 10, macOS Ventura or ChromeOS 109 or later, with a screen lock turned on. On an iPhone, you also need iCloud Keychain on.

On iPhone, iPad and Mac (iCloud Keychain)

Apple devices don’t have a “create passkey” button in Settings — passkeys are created at the website or app and stored for you. Two settings need to be on first:

  1. Turn on two-factor authentication for your Apple Account (Settings → your name → Sign-In & Security).
  2. Turn on iCloud Keychain: Settings → your name → iCloud → Passwords (called Passwords and Keychain on some versions) and make sure sync is on. On a Mac, the same switch is in System Settings.
  3. Go to a supported website or app, sign in, and open its security settings. When you choose the option to create or save a passkey, tap Continue and confirm with Face ID, Touch ID or your passcode.

The passkey is saved in Apple’s Passwords app and syncs through iCloud Keychain to every iPhone, iPad and Mac signed in to the same Apple Account. Apple states passkeys in iCloud Keychain are end-to-end encrypted — not visible even to Apple.

On Android (Google Password Manager)

  1. Open Settings → Passwords, passkeys & accounts and confirm which password manager is selected — Google Password Manager by default, or a third-party manager if you’ve chosen one.
  2. Open the app or website, sign in, and go to its security settings.
  3. Tap Create a passkey, check the account shown, and confirm with your screen unlock.

Passkeys saved in Google Password Manager sync across Android devices and Chrome signed in to the same Google account, so a passkey created on your phone also works on your laptop.

On Windows and a Microsoft Account

  1. Set up Windows Hello if you haven’t: Settings → Accounts → Sign-in options, and set at least a PIN (add face or fingerprint if your PC supports them).
  2. In your browser, open your Microsoft account’s Advanced security options (account.live.com/proofs/manage) and choose Add a new way to sign in or verify.
  3. Select Face, Fingerprint, PIN, or Security Key and follow the prompts.
  4. Choose where to save the passkey: Windows device stores it on that PC, unlocked with Windows Hello; a synced manager such as Microsoft Password Manager carries it to your other devices.

You can review passkeys stored on a Windows PC later in Settings → Accounts → Passkeys. Remember that a passkey saved to “this Windows device” lives only on that machine — the lost-device section below explains why that matters.

What Happens to Your Passkeys If You Lose Your Phone?

Illustration of keys moving through a cloud from a broken phone to a new phone

This is the question that decides whether passkeys feel safe, so here is the direct answer: if your passkeys sync, losing the phone is an inconvenience; if they don’t, it can be a lockout. It depends entirely on where each passkey is stored.

Synced passkeys come back. Passkeys in iCloud Keychain return when you sign in to a new iPhone or Mac with your Apple Account and pass two-factor authentication — Apple designed keychain recovery so passkeys survive losing every device, provided you can still get into your Apple Account. Google Password Manager passkeys likewise reappear on a new Android phone or in Chrome when you sign in to the same Google account.

Device-bound passkeys don’t. A passkey saved only to one Windows PC, or one stored on a physical security key, exists only there. Lose that device and that particular passkey is gone — you fall back to the account’s other sign-in and recovery methods, then create a fresh passkey.

While you sort out a replacement, a QR code bridges the gap. On many services you can choose “sign in with a passkey” on a computer, scan the QR code it shows with a second device that still has your passkeys, and approve with your unlock — the passkey itself is never copied to that computer. Google and Apple both document this cross-device flow.

If your phone is actually gone, work through this order:

  1. Sign in to your Apple or Google account from another device, mark the phone lost, and remove it from your trusted devices once replaced.
  2. On the new phone, sign in to the same account. Synced passkeys arrive with iCloud Keychain or Google Password Manager — no separate restore step.
  3. Check your key accounts (email, banking, shopping) and re-create any passkeys that were device-bound to the old phone.
  4. Review active sessions on your email and platform accounts and sign out anything you don’t recognise.

Two habits make all of this painless. Create passkeys for key accounts on more than one device or provider — phone and laptop, say — so no single loss locks you out. And keep your recovery details current: a recovery email and phone number you can still access are what stand between you and a very bad week.

Storing Passkeys in a Password Manager

If your life spans ecosystems — an iPhone in your pocket and a Windows PC on your desk — a password manager is the tidiest home for passkeys, because it syncs them across platforms that don’t talk to each other. 1Password and Bitwarden both save passkeys in your vault and fill them in the browser and their mobile apps; Bitwarden includes passkey storage on all its plans, including free, and 1Password’s Watchtower flags which of your accounts now offer passkeys. Both also let you share a passkey with family members through a shared vault — genuinely useful for household accounts.

The trade-off is concentration: if every passkey lives in one vault, that vault’s security becomes critical. Protect it with a strong, unique master password and two-factor authentication, and keep its recovery kit somewhere safe. Our comparisons of the best password manager for families and the best password manager for small business cover the options.

The Honest Limitations

  • Not everywhere yet. Many sites still don’t offer passkeys, and some offer them on the web but not in their app, or the other way round. Passwords aren’t disappearing this year.
  • The password usually survives. On most services a passkey is added alongside your password, not instead of it. A weak or reused password remains an open door, so it still needs to be strong, unique and protected by 2FA.
  • Shared devices are shared access. Anyone who can unlock a family tablet can use the passkeys stored on it. Create passkeys only on devices that are really yours, as Google itself warns.
  • Mixing ecosystems has friction. iCloud Keychain passkeys don’t natively appear on a Windows PC; you’ll use the QR-code sign-in or a password manager to bridge the gap.
  • Rules vary by service. PayPal creates passkeys only from a mobile browser and doesn’t support them on Windows; Amazon wants a separate passkey per marketplace. Expect quirks while the rollout continues.

A Sensible Order: Which Accounts to Switch First

  1. Your platform accounts first — Google, Apple or Microsoft. They guard your passkey sync and your recovery routes for everything else.
  2. Your main email account next. Email is the reset button for your whole digital life, so secure it early — and if you suspect it’s already compromised, work through how to check if your email has been hacked before you change anything.
  3. Money accounts after that — PayPal, Amazon, and your bank or investment service if it offers passkeys.
  4. Add a second-device passkey for each of the above, so one lost phone can’t lock you out.
  5. Leave passwords and authenticator codes in place wherever they’re still offered as fallbacks. You can revisit in a few months, once signing in with passkeys feels routine.

You now know how to set up passkeys on your accounts — the only step left is starting with the account that matters most.

Frequently Asked Questions

What is a passkey and how does it work?

A passkey is a pair of cryptographic keys your device creates for a single account. The website stores the public key; your device keeps the private key and uses it to sign a one-off challenge when you sign in, after you unlock the device with your face, fingerprint or PIN. Nothing secret is typed or sent, so there’s nothing for a phishing page to steal.

How do I create a passkey for my Google account?

Go to myaccount.google.com/signinoptions/passkeys, select Create a passkey, and confirm with your fingerprint, face or screen lock. You need Android 9 or iOS 16 or later, or Windows 10, macOS Ventura or ChromeOS 109 or later, with a screen lock on. The passkey is saved to Google Password Manager or iCloud Keychain, depending on the device.

Are passkeys safer than passwords?

Yes, on the two attacks that catch most people. A passkey only works on the exact domain it was created for, so a phishing copy of a site can’t use it, and a website breach exposes only public keys, which are useless without your device. A password can be guessed, reused, phished and leaked. A passkey’s safety still depends on your device unlock and recovery details staying secure.

Do I still need two-factor authentication if I use a passkey?

A passkey already combines two factors — your device plus your face, fingerprint or PIN — so services generally accept it as a complete sign-in. But most accounts keep your password as a fallback, and that route still needs 2FA behind it. Keep two-factor authentication on until a service removes the password option entirely.

What happens to my passkeys if I lose or replace my phone?

Synced passkeys survive: sign in to your new phone with the same Apple or Google account and the passkeys in iCloud Keychain or Google Password Manager come back automatically. Passkeys stored only on the lost device — or on a security key — don’t transfer; for those accounts, sign in with your fallback method and create a new passkey. Creating passkeys on a second device in advance removes the stress entirely.

Can I use a passkey on a computer that isn’t mine?

Yes. Choose the passkey sign-in option on that computer and it shows a QR code; scan it with your phone (Bluetooth needs to be on) and approve with your unlock. The passkey stays on your phone — nothing is saved to the other computer — making it the safe way to sign in on a library, hotel or friend’s machine.

Setup paths, requirements and service support were checked against official support pages from Google, Apple, Microsoft, Amazon, PayPal, WhatsApp, 1Password and Bitwarden in November 2026. Rollouts are still moving — if a setting has shifted, the service’s own help pages will have the current version.

About Rehan

Rehan Khalid is a technology enthusiast with practical knowledge and experience in web development, e-commerce, search engine optimization (SEO), and digital marketing. He is passionate about exploring how technology, innovation, and artificial intelligence are transforming the digital world. His areas of expertise include website development, e-commerce solutions, website optimization, search engine visibility, content strategy, and online marketing. He enjoys building and improving digital platforms, researching emerging technologies, and exploring practical ways to use AI to make online experiences more effective and accessible. Rehan is also involved in independent digital publishing through TechHubMe.com, a technology-focused platform covering technology, artificial intelligence, digital trends, and useful online resources. He is also the founder of Thinkesta.com, an open publishing platform that gives writers, creators, and professionals an opportunity to share their knowledge and reach a wider audience. Areas of Experience Web Development & Website Management E-commerce & Online Business Search Engine Optimization (SEO) Digital Marketing & Content Strategy Artificial Intelligence & Emerging Technologies Technology Research & Digital Publishing Published Work Rehan shares insights, guides, and informative articles covering technology, AI, web development, SEO, digital marketing, and related topics through TechHubMe.com and Thinkesta.com. Editorial Responsibilities He oversees content planning, editorial review, website content management, and publishing activities across his digital platforms, with an emphasis on useful, informative, and reader-friendly content. Connect & Learn More Website: TechHubMe.com Contact: Get in Touch

View all posts by Rehan →