Security & Privacy

Vaultwarden Passkey Support: Setup & Admin Guide

J
James Eriksson
··16 min read
Enable vaultwarden passkeys: version requirements, HTTPS setup, browser autofill config, troubleshooting. Managed hosting handles infrastructure burden for teams.
TL;DR
  • Vaultwarden supports passkey storage for external websites since v1.23.0; passkey login to Vaultwarden itself is v1.30.2+ and experimental.
  • Passkeys require valid HTTPS, correct reverse proxy headers, and Bitwarden set as your default autofill provider.
  • Desktop passkey setup is straightforward; mobile autofill experience is less polished but functional.
  • Not all websites support passkeys yet; passwords will coexist with passkeys for years.
  • Managed Vaultwarden keeps certificates current and reverse proxy configured so you focus on security, not infrastructure.

Vaultwarden supports passkeys natively, letting you store and sync credentials across devices without being locked to one device. But it comes with prerequisites: valid HTTPS, a reverse proxy, and the right browser extension or app version. This guide walks you through what actually works today, what doesn't, and why managed Vaultwarden handles the heavy lifting.

What Are Passkeys and Why Self-Hosters Care

Passkeys replace passwords with cryptographic keys stored on your device. The problem: they are device-locked by default, so you cannot use the same passkey on multiple phones or computers. Vaultwarden solves this by storing your passkeys centrally in your vault, synced across all your devices via the Bitwarden clients.

A passkey is not a password. It is a private key--just math--that lives on your phone, your laptop, or your hardware security key. When you create a passkey for a website, you are generating a unique key pair. You keep the private key; the website stores only your public key. To log in, the website challenges your private key to prove you have it. No network transmission of secrets. No phishing vector. No password to forget or reuse.

The beauty is also the limitation: that passkey is usually locked to the device where you created it. If you set up a passkey on your iPhone, your MacBook cannot use it unless you sync it through iCloud Keychain. Your Windows PC or Android phone get nothing. For teams, this is a nightmare. You end up with a passkey for each device, or you fall back to passwords.

Vaultwarden changes the equation. By storing passkeys in your vault like any other credential, and syncing them across all your approved devices, you get the security of passkeys without the device lock. You create a passkey on any device, and it appears in every other device's Vaultwarden instance. One passkey per website, usable everywhere.

This is the core appeal for self-hosters. You own the vault. You control where the passkeys live. No cloud vendor deciding when to sync, what to encrypt, or whether to let you export them.

Current Passkey Support in Vaultwarden (November 2026)

Vaultwarden passkey support came in two waves. The first, in May 2023 with v1.23.0, added the ability to store and sync passkeys FOR external websites. The second, arriving in v1.30.2 with Web Vault 2024.1.0, added (experimentally) the ability to log INTO Vaultwarden ITSELF with a passkey instead of your master password. This guide focuses on the former--the stable, production-ready feature. The latter is not yet recommended for critical deployments.

The difference is critical. "Vaultwarden passkey support" in practice usually means: when you visit amazon.com and create a passkey, Vaultwarden prompts you to save it. That works. You sync the passkey across your devices. You use it to log into amazon.com from your phone, your laptop, anywhere. That is v1.23+ and it is solid.

Logging INTO Vaultwarden itself with a passkey--replacing your master password with a WebAuthn credential--is different. That feature exists in v1.30.2+ but is still experimental. Most self-hosters should keep their master password as a fallback. The reason: WebAuthn is finicky with infrastructure. If your TLS certificate expires, if your reverse proxy misconfigures, if your domain changes, your passkey login breaks. Your master password does not.

Here is what you need to know about versions:

ComponentCurrent (Nov 2026)Minimum for Passkey StorageMinimum for Passkey Login
Vaultwarden1.37.51.23.0 (May 2023)1.30.2 (experimental)
Web Vault2026.10.12023.5.02024.1.0
Browser Extension2026.7.0+2023.5.0+2026.7.0+
iOS AppLatest2023.5.0+2026.7.0+
Android AppLatest2023.5.0+2026.7.0+

If your Vaultwarden instance is running 1.37.5 (current as of this writing), passkey storage is already enabled. You do not need to flip a configuration switch. The feature is always-on. Access your Vaultwarden admin panel to check your version number. If you see 1.30.2 or later, passkey login is theoretically available--but keep your master password close.

For the latest release notes and known issues, check how Vaultwarden updates work. Updates matter for security and stability.

Prerequisites: What You Need Before Enabling Passkeys

Passkeys rely on WebAuthn, a web standard that the browser enforces strictly. Several things will break your passkey setup:

Valid HTTPS certificate required. WebAuthn will not work over HTTP, a self-signed certificate, or a certificate mismatch. Your Vaultwarden instance must be reachable at a real domain (e.g., vault.example.com) with a valid, non-self-signed TLS certificate. Let us Encrypt is free. Cloudflare, AWS Certificate Manager, or your hosting provider can issue one. If you are running Vaultwarden on a Tailscale-only IP, you need a valid certificate even for Tailscale access. WebAuthn does not care that your traffic is already encrypted by Tailscale; it cares about the domain name and the TLS handshake.

Reverse proxy must pass headers correctly. Your reverse proxy (nginx, Caddy, HAProxy) must pass the request headers correctly to Vaultwarden. Specifically, it must preserve the Host header and forward X-Forwarded-Proto: https and X-Forwarded-For (your IP). Vaultwarden reads these to construct the correct domain for WebAuthn origin validation. If your reverse proxy strips or rewrites these, Vaultwarden will reject the passkey as coming from the wrong origin. The fix: check your reverse proxy config and ensure these headers are passed through unchanged.

Domain and port must match. The domain you use to log into Vaultwarden must match the domain Vaultwarden thinks it is. If your reverse proxy domain differs from what your Vaultwarden instance thinks its domain is, passkey creation will fail. To verify: log into your Vaultwarden instance and check the browser console for errors. If you see "origin mismatch," your reverse proxy is not communicating the right domain to Vaultwarden.

Browser support matters. Passkeys work on Chrome, Firefox, Edge, and Safari (partial). The Bitwarden browser extension must be installed and set as your autofill provider in the browser. On macOS, you must allow the extension in Safari Preferences under Extensions. On Windows, pinned browser extensions are more reliable than non-pinned ones. If the extension is pinned, your browser trusts it more fully. Linux has the fewest browser extension issues with passkeys, though some users report Firefox quirks.

App versions must align. If you are using the Bitwarden iOS app or Android app, update to 2026.7.0 or later. Older versions do not prompt you to save passkeys, and they cannot restore passkeys from your vault. Desktop clients (Windows, macOS, Linux) follow the same rule: 2026.7.0+. If you mix old and new clients, passkey sync may stall.

How to Enable and Store Passkeys in Vaultwarden

Enabling passkeys is not a checkbox. It is a workflow:

1. Ensure the prerequisites are met. HTTPS is working, your reverse proxy passes headers, your Vaultwarden version is 1.23.0+. Test by logging into Vaultwarden from your browser extension. Create a new vault entry with a dummy website URL. No errors should appear in the browser console.

2. Set Bitwarden as your default autofill provider (critical). On macOS, System Preferences > Passwords > Autofill > Bitwarden. On Windows, Settings > Passwords > Windows Hello. (Bitwarden will compete with Windows Hello; make sure Bitwarden is checked.) On iOS, Settings > Passwords > Password Options > Autofill > Bitwarden. On Android, Settings > Digital Wellbeing > Autofill services > Bitwarden. This step prevents your OS's built-in password manager (iCloud Keychain, Windows Hello, Google Password Manager) from hijacking the passkey creation prompt.

3. Visit a website that supports passkeys. Start with Amazon, Microsoft, Google, or GitHub. Do not try passkeys on a random forum. These sites have tested WebAuthn thoroughly. Click "sign up" or go to account security settings and look for "add a passkey" or "passwordless sign-in." When the browser prompts you to create a passkey, you will see options: "This browser," "This phone," or "This computer." Choose the one you are on.

4. When the prompt says "Which password manager do you want to save this to?," select Bitwarden. The Bitwarden extension will show in a dropdown. Click it. Bitwarden will ask you to confirm. Click "Save." That is it. The passkey is now in your Vaultwarden vault.

5. Check your vault. Log into Vaultwarden on the web. Find the vault entry for that website. You will see a new field: "Passkeys." It will show the passkey you just created, with a fingerprint and creation date. This confirms Vaultwarden is holding the passkey.

6. Sync and test across devices. Wait 30 seconds for sync (or force a refresh by closing and reopening Bitwarden on your other devices). Go to the same website on your phone or laptop. Log out if logged in. Try to sign in with the passkey. The website should prompt you to use the passkey from your vault.

Desktop vs. mobile:

  • Desktop (macOS, Windows, Linux). Bitwarden browser extension handles passkey creation and use. Most reliable. You see the passkey right after creation.
  • Mobile (iOS, Android). The Bitwarden app integrates with OS autofill. When you visit a website in Safari or Chrome, tap the autofill suggestion (usually at the top of the keyboard) and Bitwarden shows your saved passkeys. The flow is less obvious than on desktop, but it works.

Passkey Setup Troubleshooting: Common Issues and Fixes

Issue: Passkey creation prompt does not appear. Most common cause: Bitwarden is not set as your default autofill provider, or the browser extension is not installed. Fix: Check System Preferences / Settings for autofill provider. Ensure Bitwarden extension is installed and enabled. On Safari (macOS), go to Safari > Settings > Extensions and confirm Bitwarden is allowed.

Second cause: The website does not support passkeys yet. Not every site has WebAuthn enabled. Try Amazon, Google, or GitHub to test. If the prompt appears there, your setup is fine and that website just lacks passkey support.

Issue: I get an "origin mismatch" error. Your reverse proxy is not passing the correct domain to Vaultwarden. Check your reverse proxy config (nginx, Caddy, etc.) and confirm:

  • The Host header is preserved correctly
  • X-Forwarded-Proto is set to https
  • X-Forwarded-For is set to the client IP

If you are using Caddy: configure it with reverse_proxy localhost:80 { header_up X-Forwarded-Proto https } If you are using nginx: set proxy_set_header X-Forwarded-Proto https;

Then restart Vaultwarden and try again.

Issue: Passkey works in cloud Bitwarden but not my Vaultwarden instance. Three possible causes:

  1. Your Vaultwarden TLS certificate is self-signed or expired. Replace it with a valid Let us Encrypt certificate.
  2. You are accessing Vaultwarden from inside a VPN or Tailscale tunnel, but you logged in with a different domain before. WebAuthn ties passkeys to the domain. You must always access from the same domain.
  3. Your Vaultwarden version is below 1.23.0. Update it.

Issue: On mobile, the passkey autofill suggestion does not appear. On iOS: Vaultwarden was not added as an autofill provider in Settings > Passwords. Go to Settings > Passwords > Password Options and confirm Bitwarden is listed. Restart the browser.

On Android: The Bitwarden app is not set as the autofill service. Go to Settings > Digital Wellbeing & parental controls > App permissions > Autofill. Ensure Bitwarden is checked and set as the default.

Issue: Passkey login to Vaultwarden itself does not work (for v1.30.2+). First: Do you have v1.30.2+ and Web Vault 2024.1.0+? Check your admin panel. If not, update.

Second: Go to Settings > Security > Passkey and set a passkey for unlocking your vault. This is different from enabling passkey support. You must explicitly create one.

Third: Log out fully (from all Bitwarden clients). Try logging back in. You should see "Log in with passkey" as an option. Click it. If it fails, keep your master password written down somewhere very safe. This feature is experimental. Use master password as your primary login method.

Passkey Limitations You Should Know

Vaultwarden passkey support is not perfect. Here are the gaps:

Not all websites support passkeys. As of late 2026, passkey adoption is growing but incomplete. Major tech companies (Google, Microsoft, Amazon, GitHub, Apple) support them. But many smaller sites, legacy platforms, and regional services do not. You will still need passwords for most logins. Passkeys are a supplement, not a replacement.

Mobile passkey experience is less polished than desktop. The Android and iOS autofill integration works, but it is not as intuitive as the browser extension. You need to remember to tap the autofill suggestion, and the suggestion may not always be at the top of the keyboard (especially on Android with system password managers competing). Desktop is the reliable experience. Phone is "okay if you know the flow."

You cannot use a passkey to decrypt your entire Vaultwarden vault. You still need your master password to unlock the vault and view your items. The passkey login (available in v1.30.2+) logs you INTO Vaultwarden, but it does not unlock the vault contents for biometric auto-unlock. That is a different feature (still a discussion on GitHub). Your master password remains the gateway.

Linux browser extension oddities are rare but real. Firefox on Linux sometimes does not prompt for passkey creation if the extension is not pinned. Chromium-based browsers on Linux are more reliable. If passkeys fail on your Linux desktop, try pinning the extension and restarting Firefox.

TLS expiry will lock you out of passkey login. If your HTTPS certificate expires and you have set up passkey login to Vaultwarden, you will not be able to log in with the passkey. WebAuthn will reject it because the origin (domain + certificate) changed. You MUST renew certificates before expiry. Let us Encrypt certs auto-renew if you set up renewal (most hosting providers do this for you). If you self-host, use certbot with a cron job to automate renewal.

Why Managed Vaultwarden Removes the Friction

Every prerequisite above is one more thing your team has to get right. HTTPS setup, reverse proxy headers, version tracking, certificate renewal. In a DIY deployment, these are YOUR responsibility. One misconfiguration, and your whole team loses passkey access. One forgotten cert renewal, and passkey login is broken until you fix it.

Managed Vaultwarden handles this.

With Opsily's managed Vaultwarden, your reverse proxy is preconfigured. Your TLS certificate is valid, non-self-signed, and auto-renewed. Your instance is always running the latest stable version (1.37.5 as of this writing). When Bitwarden releases a new client version, your extension and mobile apps receive updates automatically. You do not track GitHub releases or schedule maintenance windows. You do not wake up at midnight because a certificate expired.

Instead, you log in, set Bitwarden as your default autofill provider, and start creating passkeys. The infrastructure is invisible. The feature just works.

For teams between 10 and 100 people, this is the difference between a passing project and a forgotten ticket. DIY self-hosting often falls to one person. That person leaves, and the next team member does not know that certificate renewal runs on the 15th of every month. Managed hosting removes that tribal knowledge.

Understand the hidden costs of DIY self-hosting and why comparing self-hosted to cloud Bitwarden matters for your team.

Frequently Asked Questions

Does vaultwarden support passkeys? Yes. Vaultwarden has supported storing and syncing passkeys for external websites since v1.23.0 (May 2023). In v1.30.2+, you can also use a passkey to log into Vaultwarden itself, though this feature is still experimental. For production use, focus on passkey storage for your login credentials.

What are the downsides of passkeys? Passkeys are device-locked by default unless you sync them centrally (which Vaultwarden does). They also work only on websites that have implemented WebAuthn. Most important websites support them, but many smaller or legacy sites do not. You will still need passwords for years to come.

How do I enable passkey authentication in Vaultwarden? Passkeys are enabled by default on Vaultwarden 1.23.0+. You do not need to configure anything server-side. Just ensure you have a valid HTTPS certificate, set Bitwarden as your default autofill provider, and visit a website that supports passkeys (Amazon, Google, GitHub are good test sites). When the browser prompts you to save the passkey, select Bitwarden. It is automatically stored in your vault.

Where can I locate my passkey in Vaultwarden? Log into your Vaultwarden vault on the web. Find the vault entry for the website where you created the passkey. A new "Passkeys" field will appear below the password field, showing the passkey fingerprint and creation date. The passkey itself is stored encrypted in your vault, synced across all your devices.

Why won't the passkey autofill suggestion appear on my phone? On iOS, ensure Bitwarden is set as your autofill provider in Settings > Passwords > Password Options. On Android, go to Settings > Digital Wellbeing & parental controls > App permissions > Autofill and ensure Bitwarden is checked. You may need to restart your browser after changing these settings.

What should I do if I forgot my Vaultwarden master password? Master password reset is separate from passkey support. If you have no backup, you will lose access to your vault. Set up a master password recovery email in your Bitwarden account before you forget it. Or enable master password reset in your Vaultwarden instance settings (if your admin has enabled it) so you can receive a recovery link.

Do I need to update Vaultwarden to use passkeys? Not if you only want to store passkeys for external websites. Version 1.23.0+ supports this out of the box. If you want to log INTO Vaultwarden with a passkey, you need v1.30.2+. Either way, updating is a good habit. Check release notes regularly for security patches.

Can I use passkeys on Bitwarden Cloud but not on my self-hosted Vaultwarden? You should be able to use the same passkey on both, assuming both have valid HTTPS, correct reverse proxy setup, and client version 2026.7.0+. If passkeys work in cloud Bitwarden but not on your Vaultwarden instance, the issue is usually the TLS certificate, domain mismatch, or reverse proxy headers. See the troubleshooting section above.

The Bottom Line

Vaultwarden passkeys are production-ready for storing and syncing login credentials. They work reliably on desktop with the Bitwarden browser extension, okay on mobile, and they eliminate the device-lock problem that makes standalone passkeys impractical for teams.

But passkeys are not a complete password replacement. You will still need passwords for many websites. And making passkeys work requires valid HTTPS, correct reverse proxy setup, and ongoing version management.

Managed Vaultwarden removes that infrastructure burden. Your certificates renew automatically, your reverse proxy is pre-configured, and your instance is always current. If you are evaluating Vaultwarden for your team, weigh the time your admin will spend on infrastructure against the cost of managed hosting.

Get started with Opsily's managed Vaultwarden hosting today.

Deploy passkeys. Skip the infrastructure.
Opsily manages your Vaultwarden instance with auto-renewing certificates, pre-configured reverse proxy, and always-current versions.
Get Started Free

Ready to self-host your own apps?

One server. Multiple apps. No per-app fees.

Get started →
Vaultwarden Passkey Support: Setup Guide (2026)