So I don’t know why but sometimes BitWarden creates a duplicate entry from a site that already has a password. Lovely. Don’t care. Other sites make me change my password every 30 days and BitWarden promptly creates a new entry. It got to the point where it’s absurd.
I use the web vault (mac) and also the application itself (Mac and PC). Only it’s a real pain in the butt. I have 30 or 40 for the same site. Which one is the new one. It should (IMHO) show the date. I’ve clipped this one to just show two, but there’re 14 (and more than one like it). Why can’t it have either a date created or a “495 days old” or something. Do you know how laborious it is to open each one and try to figure it out.
I made this separate because it’s not “removing duplicates” like another user posted. They aren’t identical. The passwords are different. And because there’s plenty of real estate, simply putting the date where the person can see it is very useful.
[I do not know if the fact BitWarden isn’t updating the original entry and creating a new one is a bug or not, but this happens on my Mac and PC using multiple browsers…..]
This is my first post here, so I’ve done something incorrectly feel free to let me know.
Could you share more details of your workflow for logging in to accounts?
What exactly are you doing when you want to login to an account? Do you get any prompts or popups by Bitwarden then?
That never happens completely automatically with Bitwarden. So, what exactly are you doing here? I guess you are using the BW browser extension then? Do you get a popup? What does it say and where do you click etc.?
PS: Could you also please make a screenshot of the Admin Dashboard of your self-hosted Bitwarden server?
You can get duplicate entries under some conditions, if you have enabled the option Ask to add login (found under Settings > Notifications in the browser extension).
If you disable this option, then the creation of duplicates should stop.
If you cannot live without this function (having Bitwarden prompt you to save a new account), then you must get in the habit of never logging in to or performing any password changes for your existing accounts unless your Bitwarden browser extension is first unlocked.
Basically, what happens is that whenever the browser extension is locked, all of your vault data is encrypted (unreadable), so it is impossible for the browser extension to know that there is already an existing account in the vault that could be updated (instead of creating a new account).
Possibly. It happens to a lot of sites. I don’t care that it happens. I just want to see a date so I know which ones to delete. I am happy with my workflow
I often do not log into Bitwarden. I add passwords to it by unlocking and adding one when it reminds me “unlock to add” (screenshot) – I use Firefox’s built-in password manager on my home desktop. I unlock Bitwarden on other machines.
I don’t think I have an admin dashboard. It asked me how I hosted BitWarden which confused me. I am a user and was directed here by tech support when I emailed them. (I pay for my Bitward subscription because I really like it except for this one thing.)
I use the BW extension in multiple browsers, so it collects passwords at home. Then I can log in and collect them if I am somewhere else. Maybe I am at work and need to log into my doctor’s site. While my work computer is secure, it is monitored by IT, so I don’t store passwords on it. I have the Bitwarden desktop app there as well as extension plugins, but Firefox/Edge/Google do not collect most passwords (just a few like work’s Dropbox).
Sorry this is so incoherent. I’m better than this, but I’m relatively new to BitWarden (under two years), having deleted robo-something and switching.
Thanks a lot for taking an interest in my suggestion to add dates and helping me through this.
Feature requests are posted in the Feature Requests category of the forum. FYI, there is an existing feature request thread that you may wish to support (you will be able to vote for it after your forum membership status has been upgraded from “new user” to “basic user”):
Well, I’m glad for you – but I’m confused about what we might do here for you then if you don’t want to change anything (and go on with producing duplicates).
I can give you some of my examples from this site. I would think BItwarden would differentiate between similar entries, that apply to other locations/purposes. The other day, when I tried to log in here, I didn’t know why my credentials were being rejected.
I eventually realized the “community” entry was the one I had to use. This image only shows a portion of all the entries, but it was was way down on the list. out of sight, and I had to scroll to see/find it. The one labeled bitwarden.com, at the very top of the list, which I would logically think is the appropriate entry to be selected, under the circumstances, is my vault login, which explains the rejection here, but it took me a while to realize that. We also have an entry labeled “vauit’.
If you have a newbie, not just with Bitwarden, but in general, confronted with this, they may not have a clue.
I’m still anxious about removing duplicates because even tho they look the same, maybe there is a slight difference that has a different application, depending on the site.
As we can see, I have multiples for each type. There were about 8 duplicates for “bitwarden.com alone. It’s not uncommon for me to get a prompt to save, even tho it’s already there, and I do save because i figure there’s a necessary reason I am being prompted to do so.
Why else would I be prompted unless the entries are not identical?
This is what mine looks like. This is why I wanted a date displayed, so I could just delete the old ones and not be bothered. I care less about the “why” than not having all these repeated entries. I expect you’re using your Bitwarden like I do because our problems look similar.
Before deleting bunches of vault entries, I would first create a .zip export, just in case things go horribly wrong.
Also, when on a webpage, the most-recently-used matching vault entry is displayed first; you might be able to use this to help figure out which of the entries can be deleted.
That is exactly my complaint. If I have 30 of the damned things that are the same, I don’t really want to click on all of them to see which is current. There is plenty of room(screen real estate) to add a “date modified” so I can just delete the old ones quickly.
Yes, actually it does matter. Some sites frequently make me change my password. I want to make sure the older ones which will not have the correct password. I want to keep the newest one with the most current password.
Perhaps pop-out the one you think is correct, test that it does indeed work, then rename the popped-out entry to something like “keep me”.
Then, you can go deleting all of the entries that have the original name, safe in the knowledge that the working one is not amongst them.
See, you’re missing the main point. You have 30 entries. How do you know which one “may be correct” – you don’t. You have to open every single one and try to find the most recent one. Putting the date on the main list solves a lot.
The whole point of a computer program is to reduce my work, and this whole mess is greatly increasing my work. Also, forgetting the date issue, why isn’t BitWarden bright enough to go “wait, I have this in here already” – many of the entries are totally duplicated, including login and password, not even old iterations.
It’s not quite that bad. When using auto-fill, the most recently used entry is listed first, so odds are good that the one you want is the first one on the list.
Forgive me if these issues have already been explained, but would you please respond to a few of my inquires
Why are we prompted to save logins identical to those that already that exist
Why are we seeing vault.bitwarden.com entries, or Bitwarden.com entries listed that on pages where they do not apply, i.e as in the case with community.bitwarden.com, asked in my previous post, citing, in the example of the Bitwarden community login list, the presence of login entries that do not correspond with the community website? Why can’t the app recognize the web addresses are different? You cite that the last used entry goes to the top, but when you go to the other website, i.e from here to the BItwarden vault, which has different login credentials, the last entry option selected for the BItwarden vault has now been usurped/replaced in that top position by one for the Bitwarden community, and vice versa, after you login to the vault, whenever you choose to return to the Bitwarden community.
These scenarios seem too obvious to be previously unrecognized, so are we to conclude there are no means to alter this behavior? I mean, If that is not the case, why would they not be dealt with.
Is this considered a “feature request”? It doesn’t feel like it fits into that category.
Hey @bituser, I didn’t read the lasts posts here in detail right now, but just a general remark at this point and in case you are not already aware of it: currently – beginning with extension versions 2025.11.0 – there is a bug with the “Update existing login” and “Save (new) login” prompts, so that they pop up much more frequently as they should: Frequent notices to 'Update existing login' / 'Save (new) login' with latest browser extensions
So, I (probably/personally) would postpone any further (extensive) discussion about those prompts until after this bug is fixed and those prompts function again as they should.
This is either because you are manually entering passwords (or using another password manager) while your Bitwarden browser extension is locked, or — perhaps more likely — the result of a recent bug that is supposed to be fixed in the next release.
This is because how you have configured your browser extension settings (or your choice to keep to default settings). For example, if you go to Settings > Autofill and change the selection for “Default URI match detection” from “Base Domain (recommended)” to “Host”, you will not have this problem.
Alternatively, you can customize match detection settings for each individual URL stored in your vault. Bitwarden offers fine-grained control over how it decides what login items are shown as matches to the active website, as you can read about in the documentation.
