Bitwarden: test synchronized locking on your computer

Contents
At a glance
Connect Bitwarden clients on one computer, check which timeout controls them and test that locking actually reaches each app. Includes compatibility limits.
Before changing your unlock settings
This guide is for someone who already uses Bitwarden on a personal computer and wants its browser extension and desktop vault to lock together. It also covers the web vault in the same browser. Have your normal account sign-in method and any required second factor available before changing settings. Do not experiment with your only accessible session if you cannot sign in again.
The intended result is a verified connection between named applications, with a timeout you understand. It is not remote locking of every device. Mobile clients are outside this connection. Work on a trusted computer, close any screen-sharing session and avoid exposing real credentials during the test. The steps below are based on official documentation reviewed today; the worked example is a proposed test, not a claim that we tested every operating system. [1]
Check the installation channel and versions
Write down your operating system, browser, desktop installation channel and client versions. Bitwarden requires version 2026.11.0 or later for the extension, desktop app and web app. Use the official download route linked in Bitwarden's documentation for updates. On a managed computer, ask the administrator about an unavailable update rather than installing another copy alongside it.
For the simplest initial test, use a supported Chrome or Edge installation and the regular desktop installer. The dedicated synchronized-unlock page excludes Safari, Linux browsers installed as Snap, the Microsoft Store desktop app, the command-line client and mobile apps. Do not infer support from a different feature's compatibility table. Installation channels can differ even on the same operating system. If your combination is excluded, keep independent locking and stop this setup here. [1][4]
Connect the extension to the desktop app
Open the desktop app and sign in normally. Open the Bitwarden extension in the browser profile you actually use, and verify that it is signed in to the same account. If you use several accounts, choose the intended one in both clients; record that choice without writing down passwords. The connection shares unlock state, not the initial login.
In the extension, open Settings, then Account security, and enable Synchronize unlock with desktop. If the browser asks for permission to communicate with native applications, approve the request only in this setup context. Keep the desktop app running. The extension links the desktop app and the web vault; those endpoints do not connect directly. Open the web vault independently using your known address if you want it included in the test. [1]
Choose the timeout in the controlling app
Check the timeout after connecting the clients. With the desktop connection active, the desktop app controls the timeout. With only the extension and web app connected, the extension controls it. A setting becoming unavailable in another client may therefore be expected behaviour, not a failed installation.
On Windows or Linux, open File → Settings in the desktop app; on macOS, use Bitwarden → Settings. For a temporary test choose a short, finite timeout and the Lock action. Record the previous setting so you can restore an appropriate daily value afterwards. Lock and Log out have different consequences for the next access attempt. Inactivity refers to interaction with Bitwarden, not simply whether you are using the computer. Do not select Never merely to avoid a failed test. [2]
Run a harmless lock-and-unlock test
Use an existing harmless test item, or create a clearly labelled entry containing no real password, payment information or recovery phrase. Keep the desktop vault and, if included, the web vault visible side by side. Unlock normally, then use the lock command from the account menu in a connected client. Inspect each other client: the item list should no longer be available without an unlock step. Record the result for each application separately.
Now unlock using your established method and check that the connected clients become accessible again. Do not copy a password to the clipboard as proof. Repeat the lock check from the other client rather than assuming the connection works in both directions.
Next leave Bitwarden untouched until the chosen timeout has elapsed. Other computer work is acceptable, but repeatedly opening the extension can disturb this observation. Check the clients afterwards. Treat any client that remains accessible as a failed result requiring investigation, not as something a checked setting can prove safe. [1][2]
Check restart behaviour and optional biometrics
After the initial test, close and reopen the desktop app, then repeat the lock check. This separates a working connection during setup from your everyday startup routine. Bitwarden offers an automatic-start setting; enable it only if that matches how you use this computer. Check the actual running app after the next sign-in instead of relying on the setting alone.
Biometrics are optional. First establish reliable locking with your existing unlock method. If you later enable supported operating-system authentication in the desktop app, test that path separately. On Windows the relevant desktop option is Unlock with Windows Hello; on macOS it is Unlock with Touch ID. Keep an alternative sign-in route available. Successful biometric unlock does not itself demonstrate that a timeout or a restart locks the other clients. [1][3]
If the clients do not lock together
Start with the failed observation: which app stayed accessible, which action triggered the test and whether the desktop app was still running. Recheck versions, the selected account, browser profile and installation channel. Then inspect the extension's connection setting and any browser permission prompt. Do not disable browser protection globally or grant unrelated permissions to make a test pass.
If the timeout options differ from the instructions, check whether an organisation policy controls them. If the setup still fails, turn off Synchronize unlock with desktop and configure independent locking in the clients you use. Repeat the basic lock test for each one. A disabled desktop connection does not remove the documented connection between the extension and web vault. For support, provide versions, installation channels and the failed steps, never a vault export or recovery secret. [1][2][4]
Keep a repeatable acceptance checklist
Keep a short local checklist: the account tested, participating applications, installation channels, chosen timeout and action, manual lock result, timed lock result and result after reopening. Store no secret values in it. A useful worked example is a desktop app plus an extension in one browser profile: mark each result independently, then add the web vault only after that pair behaves as expected.
Restore your intended everyday timeout and repeat the timed check once more. Confirm that other accounts and your phone still have their own appropriate settings. Review this checklist after a client update, a browser-profile change or a switch of installation channel. If behaviour changes, stop treating the earlier pass as evidence for the new configuration. The goal is observable locking in your actual setup, with a clear fallback when the connection is unsupported or unreliable. [1][2]
Frequently asked questions
Does this lock my phone too?
No. Synchronized unlock applies to connected apps on the same computer. Mobile clients retain their own settings. [1][2]
Evidence & sources
Source record: · Checked:
Record limits · Documentation-based setup and verification for synchronized unlock; checked against current vendor instructions. The test procedure is an editorial checklist, not a laboratory compatibility claim.
- Source reported
Synchronized unlock is limited to one computer.
Supporting excerpt: Bitwarden synchronized unlock
Synchronized unlock only applies to apps on the same computer.
Bitwarden synchronized unlock ↗ - Source reported
Timeout inactivity is measured within Bitwarden.
Supporting excerpt: Bitwarden session timeout
Inactivity is measured by time since interacting with Bitwarden—not system idle time.
Bitwarden session timeout ↗ - Source reported
Biometric settings are configured per account.
Supporting excerpt: Bitwarden biometric unlock
Security settings are set per account.
Bitwarden biometric unlock ↗ - Source reported
Desktop installation channels can offer different features.
Supporting excerpt: Bitwarden desktop installation channels
each channel may offer different functionality.
Bitwarden desktop installation channels ↗


