Which Password Managers Actually Support Passkeys

"Passkey support" is easy to advertise and hard to check. This page breaks the question into three things you can verify before you pay for anything.

Three questions that actually separate these products

Two products can both print "passkey support" on a landing page while doing completely different things. One stores passkeys of its own. Another only fills passwords and lets your operating system hold the passkey. Feature tables blur the two together. Run these three questions in order and let each one knock products out.

1. Does it store passkeys at all?

Storing and using are not the same thing. A manager can use a passkey your device already holds without keeping one of its own. The question is whether it has a passkey vault under its control.

Where to check: the product's documentation and release notes, or the sign-in screen of a test account. Look for wording about storing or managing passkeys — not just "sign in with a passkey."

2. Do they sync across my devices?

A passkey that lives on exactly one device is a single point of failure. How a product syncs matters as much as whether it does.

Platform-native keychains usually sync only among devices on the same account and ecosystem.
Cross-platform managers sync through the vendor's own account — a different dependency entirely.
Hardware security keys do not sync at all: the credential lives on the key, so you carry or plug it in.
How to check: create a passkey on your primary device, then sign in with the same account on a second device. Write down what happened, not what the marketing promises.

3. Is there a real recovery path if my device dies?

This is where "supports passkeys" and "supports recovery" split apart, and where most product pages go quiet. Storing is not recovering. We unpack the mechanisms to look for on our page about passkey backup and recovery.

What to verify in each kind of setup

The table below deliberately does not rank products. It maps the criteria you should check against four common kinds of setup. Read every cell as an instruction, not a verdict: confirm or deny it yourself during a trial.

Criterion	Platform-native keychain	Cross-platform manager	Open-source manager	Hardware-key only
Stores passkeys	Verify in your OS password and passkey settings on the version you run.	Verify in the vendor's docs that passkeys are stored, not merely filled.	Verify in the project's release notes or source that storage exists now.	Verify your key is WebAuthn-capable; storage is on the key.
Sync scope	Verify it syncs only across devices on the same account and ecosystem.	Verify which platforms are covered; sync runs through the account you create.	Verify whether sync exists, or whether you self-host or move a file.	Verify that nothing syncs — the same key works by being present.
Recovery if a device dies	Verify the account-recovery options (a second device, a recovery key) in OS settings.	Verify exportability and any emergency-access feature; ask support directly.	Verify where the encrypted vault file lives and whether you hold its key.	Verify you have a second key enrolled; without one, access is gone.
Export and portability	Verify whether passkeys can be exported at all — many cannot.	Verify the export format and whether it includes passkeys or passwords only.	Verify the format is documented and readable by tools you control.	Verify there is nothing to export; the key is the credential.
Cost model	Verify it is included with the OS, with no separate purchase.	Verify subscription versus one-time, and what happens if you stop paying.	Verify any hosting or server cost if you run it yourself.	Verify the cost of a spare key you are willing to store off-site.
Lock-in	Verify how, or whether, your passkeys leave if you switch ecosystems.	Verify how much depends on keeping that vendor account open.	Verify that the data stays in your hands, not the project's.	Verify the standard is vendor-neutral, so other keys work the same way.

The ordering trap

The most common way to waste money here is to subscribe before checking what you already own. Most phones and computers ship with a free keychain that stores passkeys. If that default is good enough for the accounts you care about, a paid manager may be a subscription you never use.

The default wins by inertia. Passkeys get created wherever the system prompt points — usually the OS.
A tell-tale sign: you pay for a manager, then notice new passkeys landing in the OS keychain, not in the app.
This is not an argument against paid managers — cross-platform sync and real recovery can be worth paying for. It is an argument for deciding which problem you are solving first.
For the deeper version of this choice, see passkey versus password manager first.

How to verify a claim yourself during the trial

Free trials exist so you can test the three questions under real conditions. Do these once, on a throwaway account, before you pay.

Install the manager and make it the active passkey provider on your primary device.
Create a passkey for a test account. Note where the system offered to store it.
Open the manager and the OS settings and confirm which one actually holds the passkey.
Sign in to the same account from a second device — ideally a different operating system — and check whether the passkey is already there.
Open the manager's recovery and emergency-access settings. Read what they claim to restore, and whether passkeys are covered.
Try to export your vault. Check whether passkeys come out with the passwords, and in what format.
Ask support the questions on our recovery page. A vague answer is a real answer.

If a product fails step 3, 4, or 6, that is why the trial exists. If it fails the recovery question, treat its passkeys as single-device credentials until you can enroll a second one.

Where a recommendation would go

When we have run the checks above ourselves, the names we would use will appear here. For now the space stays empty: better blank than an untested claim.

We list no paid links until we can verify the claims below ourselves.

To be explicit: we have no affiliation with, and receive no endorsement from, any vendor or platform named on this page. Product names, where they appear, are editorial references only.