@H.B.A Welcome to the forum!
I moved your post into the existing feature request on the same topic.
Hey, thanks Nail!
I was sure I wasn’t the only one who felt that this is an obvious feature to have, the only reason I created this account is to request this feature, but damn! Six whole years and still? Is there a reason why?
1 Like
Bitwarden should provide an email field by default. Every website requiring a login also requires an email address. Sometimes the login is the email address, but often it is not. In those cases an email is still required. It’s a pain to have to set it up manually.
1 Like
Hello @Sophocles and welcome to the community!
That’s not strictly true. A popular exception are banking websites.
@Sophocles Welcome to the forum!
I moved your post into an existing feature request on the same topic.
I stumbled over this shortcome of Bitwarden the first day I gave it a try. After digging through many blog and forum post, my resume is: Many discussions and feature requests in various matters would find a solution in further extending the standard items to cover contemporary demands. But standard items/templates seem to be a holy gral of Bitwarden, which is extremely rigid against changes.
A basic design strategy for a password manager should be to capture and save all information involved in a login procedure, not to loose anything which might be useful to have later. Not offering the email address in the standard login template is a no-go and a design flaw in a modern password manager, it’s simple like that.
It is true that in the first years of online services in the 1990s (I experienced it) the user name or a customer number has some importance, but those days are gone. Since then the email address has established as unique identifyer.
The simple solution would be to add an email field to the standard login item and let it empty if a website does not ask for an email to register, which is extremely rare. For autofill the email or the username is offered, whatever is asked.
While other password managers have dedicated templates for online shops, forums, banks, etc. to meet the different requirements, Bitwarden wants to stay with one universal template for all logins. But isn’t it basic logic, that an universal template must offer the union of all fields, and not the least common multiple? To complement a minimal structure with unstructured custom fields on demand, for information of similar type, as the first email address, is an unfavourable appoach in information management (and relational databases).
The vast majority of login cases are that of millions of online shops, where it is standard to fill just the email address besides the password, while a user name is not involved at all. For this reason the huge majority of the BW global data base entries will have the username field populated with email addresses already, which makes it an universal field in fact. This established base could co-exist with an extended template, without problem, no point against progression.
The next step in a registration progress of an online shop (the majority of all login cases) would be to autofill with an identity item for shopping with a real name and street address for delivery service for physical goods. Any email address of an identity item would not interfere with the login, because it is not asked again in the registration process.
So the feature request from my side is: Please add an email field to the login item template!
Most modern accounts use one of two patterns:
- Email + password
- Email + username + password
In the first case I store my email address in the Username field (because Bitwarden does not provide an Email field by default), which works but is not strictly accurate. In the second case, where both email and username are required, I have to manually create a custom Email field.
Request
Please add a dedicated Email field to all Login items by default, alongside Username and Password, and include a toggle such as “Use email as username.”
Expected behavior
- Login items display Email, Username, and Password by default.
- When “Use email as username” is enabled, Username mirrors Email and stays in sync.
- When disabled, Email and Username are independent fields.
This would make Bitwarden more enjoyable to use, better reflect modern login requirements, and ensure email addresses are consistently stored in fields that accurately reflect what they are.
If this change were introduced in an update, existing Login items could remain unchanged by default, with Email initially empty and the “Use email as username” toggle disabled. Users would then have the option to adopt the new field gradually and revise past items on a case-by-case basis.
Optionally, Bitwarden could also provide user-approved automation, such as detecting when a Username appears to be an email address and offering a one-click action to move it to the Email field and enable the toggle. No automatic or silent changes would be required.
Thanks for considering this improvement 
2 Likes
@VVOLVE Welcome to the forum! I have moved your post into this thread, a feature request on the same topic.
Out of curiosity, could you please provide some examples of common websites that require both username and email to be supplied when logging in? Other than airline websites, which often require last name, frequent flier number, and password.
Hi, thank you!
Bitwarden Community Forums (BCF) prompts you for username + email + password when creating an account (I just created my account to post that request so ironically it’s fresh in mind 
).
You did specify “when logging in” (not when creating an account). If my request stated that all three are sometimes required at login, that was my mistake. I meant during account creation.
Thank you for considering my request! 
Nate
1 Like
For this scenario, you might find an Identity to be more useful.
What’s the status on this?
The requested feature is not on the development roadmap, and cannot be found among the open PRs on Github. By number of votes, this request is currently ranked 31st among the still-open requests.
Status: “Don’t hold your breath.”
Why does Bitwarden still not function like Dave suggested? It’s exactly the UX I want to use. Most sites use email for the username. Some require an email and username. If the both are required, I want to save both in Bitwarden. If only email is saved, fill that automatically. If username is saved, use that instead.
1 Like
I wish to express support for the request for this feature. I also wanted to add to the request: please make sure the Username, Email, and Password slots all benefit from the revision history feature with a separate allocation for each type.
Registration here, on the community.bitwarden site, is touched by this very issue as it includes a separate ‘Username’ field.
1 Like
Yet, like the vast majority of websites, you only need one of the two (either username or email) to actually log in.
It’s not meant to be rude, just thought it was worth mentioning as I ran into it while registering here to vote on this FR.
I would personally prefer to have a history-supported slot for all three parameters by default for any given login and I feel that other users in the FR have laid out reasonable rationales to support their votes. I typically try to capture all information unique to a login, and lately I created logins for enough sites with both email and username fields that I ended up searching the topic and landing here.
In any case, it is a relatively minor QoL tweak in terms of scope/impact and is of course up to the developers to decide whether it would be worth implementing eventually
2 Likes
This would be very useful for LDAP vs SSO logins where you might use the full @ for one login form, while using just for another.