Hi,
I was logged out of the browser extension today. I logged back in, and the password generator settings were reset to default. Does Bitwarden do this after a certain amount of time?
Or does it have something to do with this?
Greetings
Same here. My mobile app has been logged out, too.
1 Like
Same here, on windows client, browser extension and android app, and also the settings I set previously were restored to defaults.
1 Like
Very likely, as there were more reports on this (also on the Subreddit), so probably about everyone (?) experienced this. – And this can happen sometimes…
1 Like
But why are the password generator settings reset?
Logging out removes all local vault data. As settings like generator settings are not synced (and as the local data was “deleted” when logged out, as written before), then those generator settings have to be set up again.
1 Like
That could be a good Feature Request
I think those are already there:
(I think it is debatable and not entirely clear, if syncing the generator settings would also be included in “Sync (all) settings”…)
Would it perhaps make sense to combine the two suggestions under “Synchronize Bitwarden Settings”?
Seems like only the EU server was impacted: https://www.reddit.com/r/Bitwarden/s/XPDD9YiGNS (comment from Micah from BW)
Sometimes (but not always) we merge similar feature request topics.
However, when doing this, there is a risk of creating a “Franken-topic” in which too may distinct ideas are combined (e.g., see the feature request More Password Generator Enhancements (Comprehensive List)). When there are too many concepts in a single feature request topic, then it becomes impossible to meaningfully interpret the vote count (does a vote mean that the voter was in favor of all ideas, or only a subset? ).
The general rule is that each feature request topic should contain only a single proposed suggestion.
The resetting of the generator’s settings may be different. On Windows desktop, this is saved to the data.json file, which DOES persist even after logging out. The extension not doing the same thing is either a bug or an inconsistency.
The extensions do not have a data.json file, so it is probably a technical limitation related to the way that the extension stores its state.
In the Firefox extension, the storage seems to be a SQLite database. I can’t imagine what BW can’t store in the database. I can also confirm that the generator’s settings do persist across logout-login in the Firefox extension 2024.12.4. As for the Chromium extensions? 
1 Like
I also do confirm that Edge 2025.5.0 doesn’t keep the generator’s settings across the logouts.
1 Like
It should be possible to synchronize this setting.
I have confirmed that in Chrome, the browser extension generator settings do survive a log-out followed by clearing of browser data (by closing and restarting an Incognito browser after logging out from the browser extension).
Thus, all of this discussion about the effects of logging out are a red herring. Some non-synced data are cleared on logout (e.g., the global generator history and any PIN unlock settings), but most preferences are retained in the local cache.
What seems to have happened to OP is the known phenomenon that locally configured preferences are occasionally reset by some (not all) software updates. In fact, this behavior has been explicitly cited as a motivating factor (e.g., here and here) for supporting the feature request Sync Bitwarden settings, like "Lock after X minutes" or PIN.
It should be, but it is not currently possible. The relevant feature request to support is here:
1 Like