Passkey Support on Old Devices and Browsers (Compatibility Table)
Whether a passkey works for you is decided by three layers — the operating system, the browser, and the website itself. All three must agree, and the weakest one wins. This page shows what to check, how to test your setup in about a minute without installing anything, and what to expect on older hardware.
Three independent layers decide support
A passkey needs three things to line up at once:
- The operating system (or platform). It stores and unlocks the passkey — the built-in credential store that shows a fingerprint, face, or PIN prompt. If the OS has no place to keep a passkey, a browser on it usually cannot offer one either.
- The browser. It has to be able to reach that credential store through the operating system's own interface. The same computer can behave differently in two browsers, and an out-of-date browser may lack the plumbing entirely.
- The website's own implementation. A site chooses where and how it offers passkeys: on desktop but not mobile web, in its app instead of the browser, or only on certain browsers.
A fourth, quieter layer trips people up: account state. Even a supported setup offers no passkey if the site has not enabled the feature for your account, or has buried the option. Because any one layer can say no, the result is limited by the weakest — and when they disagree you usually fall back to a password plus a second factor, with no message naming the layer that failed.
How to test your own setup in 60 seconds
You do not need to install anything.
- Open a site you trust and go to its account security settings. Look for wording like "add a passkey" or "sign in with a passkey." If the option exists, that site supports it on your current browser and device.
- Prefer a throwaway first: several projects publish a public demo page for trying passkeys. Search for "passkey demo" and watch the flow without touching a real account.
- Tap the button and watch. If your device shows a system prompt (unlock with fingerprint, face, or PIN), the OS layer works. If the option is greyed out or does nothing, that combination does not support it yet.
- Confirm your browser is up to date and your OS is on a version its maker still supports. Both are prerequisites, not details.
Note the result; it saves time later when a login misbehaves on this combination:
Device / operating system: __________
Browser and version: __________
Was a passkey offered? yes / no
One caution: creating a passkey on a demo account risks nothing; on a real account it is a real change. Add it while your password and second factor still work, and confirm you can sign in on a second device before you rely on it.
Compatibility by device generation
The table describes generations of gear, not exact version numbers, because cut-off points differ by maker and shift with each release. Read each row as what to expect from that kind of device, then verify with the test above.
| Setup | What to expect | If no passkey is offered |
|---|---|---|
| Modern desktop OS, up-to-date browser | Passkeys are usually offered and stored by the OS or the browser; unlock uses the system PIN or biometrics. | Password plus an authenticator app; a security key if you want one factor that travels between machines. |
| Older desktop OS, current browser | The browser may run, but the OS credential store may be missing, so the passkey option can be greyed out or stored inconsistently. | Password manager plus an authenticator app; a security key over USB or NFC where the browser supports it. |
| Older desktop OS, older or unsupported browser | No passkey option at all, and possibly no security updates either. | Keep it for reading; do account sign-ins on a supported device instead. |
| Recent phone, current OS | Passkeys are usually offered and stored in the phone's keychain or in your password manager; unlock uses the device biometrics. | Password manager plus an authenticator app, with the email recovery path left open. |
| Old phone, OS no longer updated | No passkey support, and often no security updates — which matters more than the missing feature. | Password plus an authenticator app, and a plan to retire the phone for anything account-related. |
| Tablets | Behaves like the phone or desktop it is based on; a connected keyboard makes it desktop-like, and some apps lag behind the browser. | Same fallback as that device's generation. |
| Shared, borrowed, or public computer | The hardware may well support passkeys, but anything you create there can be tied to a shared profile others can reach. | Do not create or store a passkey; if you must sign in, use a password manager that locks itself and sign out completely. |
Two notes. A device that supports passkeys can still fail at the site layer, so a row is a ceiling, not a promise. And compatibility shifts with each release — check your browser's and OS maker's current documentation rather than trusting any table.
Why a security key travels where the rest do not
Most setups above depend on the device having a built-in place to keep credentials. A hardware security key sidesteps that: it holds its own credential and does its own cryptography, so it does not need the host OS to have a passkey store. As long as the browser and OS can talk to a key over the standard USB or NFC interface, it works where the built-in store is missing — including machines you do not own.
That portability makes a security key the closest thing to one factor that works across otherwise-unsupported setups. It is not magic: an old browser with no support for external keys will still refuse, and a lost key is gone. Register a second key, or keep another factor and offline codes alongside it.
If your gear will never support passkeys, do not force it. Keep a password manager for logins, an authenticator app as a second factor, and recovery codes offline, then move account work to a supported device. Our notes on backup and recovery and troubleshooting go deeper; if you are still deciding where to begin, see the order to set things up in.
When passkeys are unavailable, the way back in is usually email plus a code, so protect the mailbox first. See vaults that can recover passkeys and, if a device is already gone, losing the phone. To compare how vaults handle these cases, see the comparison page.
Last updated: 2026-10-16
Margelab is an independent publication. We are not affiliated with, endorsed by, or sponsored by any device, browser, operating system, or password-manager vendor named on this page. Product names are used for identification and commentary only.
Some links on this site are affiliate links. If you buy through them we may earn a commission at no extra cost to you. This never changes what we recommend.