Additional item types (pre-defined)

@walib65081 - all set :slight_smile:

1 Like

Hi Community Bitwarden!

I hope to help you in some way.

  1. This idea above talks about standardizing defined types. My idea is this: all predefined types somehow need to be standardized to avoid empty data and/or null data Because “fields may be required” - if they are models
  2. I believe this may help in this topic.

I’ve just moved my company from LastPass to Bitwarden, and this is the one thing that I miss, but I’m happy to see it on the roadmap for Q1 2022!

I was going to try to copy all of the SSH and database credentials the dev team has stored into “login” items (as the LastPass export turned them all into “secure notes”) but I’m holding off until I see what the update provides. I also had some custom items types defined in LastPass for things like “keystores” (Android app signing certificates).

As a fellow developer I’m sorry to ask this question, but is the update on track?

i disagree with this.
Find a Way to another universal entry.
For exemple :
Title (name)
information x 4 filed with a copy option

Managing Entry in Lasspass (LP) is in my taste full of bloat of MANY MANY Entry I never used and don’t plan to. And something I now love of Bitwarden is the simplicity.
Maybe those can be enable in the account.

I created multiple “template” in LP

You could simply have one with :
Title (name)


but as a suggestion for a model :
“document” I had a time where I created multiple document with password but could find a model that really fit (7z, verascrypt, cryptomator,ect) so it could be something like :

Tile (name)
Note :


Looks like this thread has been here for a while. I haven’t read ALL 189 posts, but from the jest of it, a lot of people would like more types added, me included. I am coming from an app that has all sorts of types, and I’m now finding out that I have to squeeze most of them into the Secure Note and customize the fields to fit. Taking some work, but I will make it work.

I’ve cast my vote to add additional types.




Hi @rosede, you’ll be happy to know that ‘additional item types’ is included in the 2022 roadmap.


This is great to hear. Thanks for bring it to my attention.


1 Like

Hi Community! HI @Kruger2147 ! How are you guys?

Great idea… this is great. ^^ awesome… So… I have this idea.

ui/ux 1

ui/ux 2


  • Here have some item types

ui/ux 3


  • Item types are associated with item type by association. Example: Login inside => Type: “Common type item”

ui/ux 4


  1. I read all the comments and got this inspiration, I made this ui to represent everyone’s opinion here
  2. I’m happy if I can represent everyone’s idea here with this beautiful graphical interface ;D
  3. I hope to help

This looks awesome! I hope these options are added to Bitwarden in the near future :smiley:

1 Like

Update from the product team: additional item types are in early development, beginning with a significant refactor of how item types are stored in the database while keeping the product backwards-compatible. This will also enable faster creation of new item types. Making progress!


Could you tell us what item types are being added? :face_with_peeking_eye:

If this is still in early development, how could they possibly confirm this, @Korat?

1 Like

sorry I was just curious :frowning:

WEB SITE LINKS SAVING. Nowdays we visit so many websites to read and forgot too. Usually Passwords are related to websites. Not all websites have password request. Saving websites links are very useful. Please consider adding this too.


I’d really love to use additional items.

I’ve always wished to have a Software Licence Key Item
(Developer, Software, Version Number, Key, Activation Date, Expiring Date etc.)
and a contact item to use Bitwarden as address book.
Less fields than the identidy item but importable from *.contact *.vcf *. files or via scanning a QR code.

In Addition to that my insurance company sent me an digital insurance card today to add to a digital wallet via QR code (my insurance company recommendet the app “PassWallet” from Google Play Store.
My first thought was: It would be nice to considure Bitwarden as this digital wallet.
This cards have to be importable via scanning QR code.

I’ve uploaded a screenshot of this PassWallet entry in Google Play, here is the link:

1 Like

Hi all!

  1. I find this idea, proposal interesting.
  2. I hope to help the Bitwarden company and community in some way
  3. As this post talks about adding new types defined in Bitwarden, I added the type here… bookmark - here : Bookmarks type
  4. One thing that’s interesting is that this type of item set as a bookmark - could help this topic: Bitwarden Bookmark Sync too - which can increase bitwarden’s customer base - most people have a lot of information about the sites they need to access and this mixes with the sites they need to monitor daily with login and password - Having a password manager like Bitwarden is a great way to make the user’s life easier - but giving the user the chance to manage their information based on urls does greatly improve the user’s life too.
  1. There is even another type of item to be added - As in the case of a bookmark which is a url item type.
  2. It would be interesting to have the item type as url - to remember the website we are going to access or the which is website most common that we need to access
  3. Usually these sites we don’t have a record - but… serve as a reminder - part of the password manager is to manage passwords, but also to manage type the of information too
  4. There are no new item types defined at the moment, but I hope it helps in some way

I have the same question about year later…
These types are available only on Premise or something?

I tried to found more types, but without results. I have premium account…

1 Like

Hey @iAmMember additional item types are on the roadmap, stay tuned! :+1:

Hey @bw-admin thanks for ansawer!
Looking forward! Additional item types are for me now the most needful option in Bitwarden :smiley: so i will waiting impatient for it :smiley:

1 Like

I paid for a year of a Bitwarden family account to bake it off against my 1Password. Let me preface, I strongly, strongly dislike 1Password: Their customer service is unfriendly and arrogant. The pricing is borderline predatory, and how they’ve treated customers who purchased perpetual licenses is abhorrent.

After coming across this thread, and seeing a request that is…

– Four years old, to design, implement and deploy new database models plus the necessary front-end refactor work is confusing. Looking at Bitwarden’s GitHub release cadence, there are consistent patch releases, and semi-regular dot releases. I understand as a small company that scope is hard to manage, but with an open source community that is eager to contribute, why not encourage the community to contribute to larger changes like this? I have a blanket assumption in my head the average BW user is more technically adept than most, understands OSS, and would probably be happy to contribute on larger workstreams like this request, if some direction was given from BW on the help it needs/wants to get these requests over the finish line.

– Indicative of a pattern that plainly ignores community feedback (Feature Requests - Bitwarden Community Forums). As an outsider, it feels like a lack of customer empathy and lack of resourcing to working on the core product could be an issue. (The GitHub releases page shows many enterprise and saas related functionality being implemented for the server repo).

…I’m going to very sadly stick with 1Password when it comes time to renew my BW or 1P accounts. I love Open Source software. Personally, OSS is what pays my salary, so I feel uncomfortable making this pointed criticism towards this product that is well-intentioned, but just doesn’t deliver on basic needs. I’d pay 2x the cost of my 1P subscription to move to an OSS product that has a decent saas offering. If I can’t use the product as myself, and others want to use this product, then I’m going to move away, and stop patiently waiting and hoping with fingers crossed that the folks who decide the roadmap will eventually organize work towards what customers are asking for.