(The listed release number is for the Bitwarden Server, other version numbers released in this cycle also include Web 2026.4.0 and Mobile 2026.4.0.)
Password Manager
Preview image attachments on Android: You can now preview image attachments from within the Password Manager Android app, without having to download the file to your device. Previewing image attachments will be available on iOS in a future release.
Admin Console
Send controls Enterprise policy: Two Enterprise policies, Send Options and Remove Send, were merged into the newly titled Send controls policy. If either policy was previously turned on, the chosen options will transfer and remain unchanged.
Updated Enterprise Policies page: On the Policies page, the Enterprise Policies are now organized into three categories: Data Controls, Authentication, and Vault Management. You can also review at a glance which policies are turned on or off.
To keep everything in one place, new versions within this Release cycle will be added to this first post. (and I only report the Release Notes here as they can be found in the official Bitwarden Release Notes and in the released versions in the Bitwarden GitHub repositories – I’m not a Bitwarden employee)
Some new features may be behind a feature flag, so it can take a few days for those features to get “activated” by Bitwarden. (in rare cases, new features can also temporarily be disabled again via those feature flags when there are unforeseen issues)
Features marked with a Star icon are part of a progressive rollout.
Some Bitwarden apps/clients are distributed by “stores” (like Apple’s App Store, Microsoft Store, Google Play Store, Mozilla’s Extension store…) so the availability of new versions via those channels also depends on the approval processes of these “stores” and thereof the respective roll-out can take some time.
For those who self-host their Bitwarden server: some new features of a given release cycle might only arrive / get activated in one of the next release cycles on self-hosting environments.
A “major version”, as described in this document, is indicated by the second number in the version format used for Bitwarden clients and servers (e.g. 2025.6 .0 or 2025.7 .1).
@mutilator Just a normal major release indicated by the second number in the version as pointed out by @DenBesten.
I teased this upcoming change to the Github release notes here:
Previously the commits weren’t categorized and it was harder for consumers to see what was updated and if the bug they reported/experienced was fixed within a specific release. This aims for a nicer experience and to give more transparency. There’s some more things I have planned around this, stay tuned.
This was still a slightly manual effort, but I hope to have this more automated with the next client release.
Kudos to @Nail1684 for providing these updates here !
Yes, I love the improvements in the Android release notes already. I liked Android’s notes before for being more detailed than other clients’ release notes, but honestly, if I needed to search for something, I had the LLM handle it because they were long and unreadable (and because of synonyms and such). Now they’re more readable.
@mu88 If you’re talking about the “feature flags” mentioned – my understanding is: via feature flags, Bitwarden can control a roll-out of a given feature on the cloud accounts.
As Bitwarden can’t control the feature flags on self-hosted installations, only when the feature flags get removed from the code, those features also arrive for self-hosted environments.
Thanks for your input! Maybe let’s discuss it with a concrete example: some weeks ago, the new archive items was released and announced in the release notes. Some screenshots clearly show that this feature can be used on bitwarden.com. So I pulled the Bitwarden Lite Docker image and was surprised that I was not able to archive items. So I’ve contacted the Bitwarden support and got the following response:
The Archive feature has not been released yet, and we apologise for any confusion this may have caused. It will first become available on Cloud, and will then be rolled out to self-hosted environments at a later stage.
According to what you wrote before, my assumption is now the following: there’s an feature flag for this particular feature. This feature flag has been enabled in the cloud, but is not enabled in Bitwarden Lite.
Is that understanding correct? And if yes, are you aware of a list of available feature flags so that I could play around with it on my own?
Some new features may be behind a feature flag, so it can take a few days for those features to get “activated” by Bitwarden. (in rare cases, new features can also temporarily be disabled again via those feature flags when there are unforeseen issues)
Star icon are part of a progressive rollout.
!
