@therave Welcome to the forum!
I moved your post into an existing feature request thread. To support this request, you may want to click the Vote button at the top of the thread.
Needed to look up an old credit card number today. Was bummed to find out that the history isn’t stored for card types.
@newwardenintown Welcome to the forum!
This is actually a bit surprising, since the card number is a “hidden” field (i.e., the card number is obscured until you toggle the 
icon), and Bitwarden does maintain a history of other hidden fields (passwords as well as custom hidden fields).
I agree. I’ve had two sites in the past that wouldn’t let me modify or remove old/expired credit cards unless I could enter the old card info in first, and I didn’t have it.
It would be helpful to pull up old credit card info, such as card number, expiration date, cvc, etc.in case it’s needed.
Upvoting
This feature is already available in Proton Pass (called “item history”). Bitwarden should implement this to stay competitive. I would love to use this to easily track my previous credit card numbers and the history of other important information that isn’t stored in the password field.
Pass keys can be accidentally deleted pretty easily (edit, click the ‘delete’, save). There’s seemingly no way to get them back.
You can re-import them from a backup which is nice for someone like me who’d bother to make automated encrypted backups, but if you’re not doing that then if you enter the edit dialog, click the ‘remove passkey’ button, then save, you’ve locked yourself out of that account. So every time you edit you’ve got to be real careful to preserve the key if you have no backups.
I have a cat, people have kids. Errant clicks happen. If this behaves similarly on a phone it’s even more likely this happens.
Or, why not allow for full record history? 1password does this well: any edit is preserved, and you can restore old versions at any point. The only way you can truly lose access is if you delete the whole record and let it sit in the ‘recently deleted’ bin for 30 days. (assume votes go towards this idea instead of one where only passkeys are restorable)
3 Likes
Are we there yet? Seriously this is one feature I’ve been waiting for since forever. A password manager should be treated as a secret manager ie every field should be considered important to have their own edit history. Keepass did it right but i prefer bitwarden for sharing. Please, consider to add this feature.
1 Like
I voted for this because, if we want to support full offline editing, having a history for all fields is crucial. Without this feature, later edits could overwrite earlier ones, resulting in lost work.
2 Likes
Could be helpful.
ABSO-BLOODY-LUTELY!
This is ESSENTIAL functionality.
Even if they made it a premium feature, I’ve already donated several times $20 is nothing when it comes to something we use MORE than Office! Just like A/V. We have to fork out the $30-$50/year or stick with restricted / limited free A/V.
The thing that annoys me the most, is that in 2025 if you export your Bitwarden databse, it DOES NOT export all fields! Plus the sequencing of thoe fields in the export are completely non-sensical! Even the names of the fielsd.
They have so uch work to do in order to bring it up to scratch and optimse performance. “Autofill and Save” for example - I hate having to wait 10-20sec for it to proceed. Quicker to copy the URL, edit, insert URL, copy password and save.
History for EVERY field is necessary! Show the last 3 changes to those fields with date and time.
A post was merged into an existing topic: Offline Editing (management of writeable vault items)
Which fields are you missing? All fields should be included if you export in JSON format. The CSV format is lossy (e.g., it excludes Card and Identity items, converts some custom field formats, and omits URI match detection rules and password histories), but to my knowledge, it does preserve all fields (of Login and Secure Note items), except passkeys.
Came to suggest exactly this, glad someone already made the suggestion, sad seing it being suggested since 2021 lol.
On a serious note, this is the only thing i felt missing from Bitwarden. Agree on another post up there, passwords manager should be treated as a secret manager and every entry should warrant their own dedicated edit history.
I think i’ve lost an account too since I’ve been using email alias, I’ve edited the username field to another new email alias but old alias aren’t being edit history recorded. Gone just like that. Technically i can avoid the limitation by also duplicating the email username onto the edit history recorded secret note but I’m too old to always need to manually do that specifically, every time. Please, do us solid by introducing the edit history for all field entry 
2 Likes
I’m also surprised that this basic feature is not implemented yet for every item. Coming from Keepassxc. It would be great to track the item history and restore specific versions.
1 Like
This basic feature (next one after sorting) has really to be implemented. You can loose important data without a proper history.
And even newer password managers like Proton Pass implemented his feature after a few month.
+1
I would like to see this.
I understand that this feature is important for you, perhaps even crucial for your workflow. But by no means is this a “basic feature”.
The basic features of a password manager are secure generation, storage, and retrieval of credentials, perhaps also auto-fill. But not even sync across devices or sharing of passwords are “basic”, otherwise Keepass(XC) would not be that popular.
I suggest for BitWarden to change its strategy – abandon the “Save” button and switch to the modern “Version History” strategy
this is how it looks in MS Office. Take a ready-made solution from large companies.
(I don’t understand the “Show changes” button. BW programmers can come up with their own solution.)
The “Back” button (Ctrl+Z) only works in the current session editing of login .
You don’t have to come up with anything. Use ready-made widespread ideas.
That’s all you need to do 
.
Your post was moved into a related feature request thread.
1 Like
If you compare MS Office and BitWarden, it’s like comparing an entire train and single wagon. Such different scales. And the same comparison in terms of data significance. BW - passwords, Office - texts and money. Where is the value higher?
Which has a higher number of users: BW or MS Office?
However, MSOffice took a risk and removed the Save button. And there are no retrogrades , who say, "We don’t want to change the old Save button to the modern Version History, which speeds up work because a user can make a mistake in a single letter.
A bookkeeper can make a mistake in calculating the budget of an entire organization or a whole country. But this same bookkeeper has been doing their job for the last 10 years. They find errors in the Version History, and everything is fine without the Save button.