This is true if the browser extension remains logged in. Most users do keep their apps and extensions logged in at all times (@bwuser10000 doesn’t, but they are in the minority), and therefore will normally be able to access their vault contents even when there are internet connectivity issues.
However, as you discovered, apps and extensions can sometimes be logged out automatically, which erases the locally cached vault copy. This happens when you make changes to your account security settings (master password, KDF, etc.), or when you use the option to de-authorize all active sessions, or when a login session token is too old. However, on occasion, a forced logout can also be triggered without any user action, when Bitwarden initiates a session reset from the server side during certain maintenance tasks; in my experience, this happens rarely (once every year or so), but one should be prepared for it.
For this reason (and for disaster recovery purposes), it is important to periodically make vault backups. The easiest and safest way to make a backup is to create a Password-Protected .JSON export from the Web Vault, as we already discussed. All your data (except any uploaded file attachments, which are not included in vault exports) will be available in this encrypted file. However, decrypting and accessing the contents of this export can be a bit cumbersome, especially if you are having internet connectivity issues.
To have a readily accessible backup for rare situation in which one has been completely logged out of all Bitwarden sessions and also is experiencing internet connectivity problems (or if one does have an internet connection, but does not want to go through the trouble of creating a new Bitwarden account and importing the .JSON backup, just to look up a single password that is needed quickly), it can be convenient to have an off-line password manager. @bwuser10000 uses KeePass for this purpose, but you can actually use Bitwarden itself as an off-line password manager that accesses a backup copy of the local vault cache.
What I do personally is to have the portable version of the Bitwarden Desktop App (which is available for Windows only) installed on a USB stick. Periodically, I plug in the USB stick and log in to my Bitwarden accounts using the portable app, which syncs the cached vault data. I then close the app without logging out (timeout action is set to “Lock”); in Windows Explorer, I then right-click the Bitwarden data folder (bitwarden-appdata
in the same location where I installed the portable app) and select Send to > Compressed (zipped) folder.
If I am ever logged out of my usual Bitwarden apps, I just plug in the USB stick, disconnect the computer from the internet, and then launch and unlock the portable app from the USB. If I happen to make a mistake and forget to disconnect the internet, then the local vault cache will be erased from the bitwarden-appdata
folder — this is the reason for creating the .ZIP file, as I can simply unzip the file and restore the bitwarden-appdata
folder contents after disconnecting from the internet.
You don’t need to use an external USB stick to employ this strategy, and you don’t even need the portable version of the Desktop app. All that is needed is to periodically create a copy (the .ZIP file) of the Bitwarden data folder as it exists while the app is still logged in. The location of the data folder depends on the app and the operating system; information about where to find the data folder is available here: