Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
Experiment #4 – New interface in 1Password.com’s vault view
Hi Folks! Today we’re bringing you a beta version of a major update to the vault item view interface on 1Password.com. Our goal is to align the design with the main desktop application as well as improve our ability to introduce new features consistently across all of our platforms. Unlike previous experimental features in labs, you are not required to manually enable this experiment, and it will not appear under the “Labs” tab in the 1Password apps. As this is an updated vault item view of our web interface, you can access it directly via this link. At this time, the new interface provides a read-only version, which means it is limited in functionality compared to the current interface. We wanted to start testing as early as possible to identify any potential issues well in advance of a full rollout. Full functionality that aligns with the current vault item view interface will be gradually introduced over the next couple of months as we continue testing and developing. The primary questions I'm trying to answer are: 1. Do you prefer this new interface over the old one? 2. Do you see value in us rolling out this new interface of the vault item view to all 1Password users? 3. Are you experiencing any performance issues? 4. How often do you use the vault item view in 1Password.com? We are eager to hear what you think about this new web interface. Please share your feedback and thoughts below in the thread! Updates Jun 20 Added Watchtower Added a link to the admin dashboard from the vaults menu Added "What's New" to the help menu, which links to our new release notes page Added vaults in quick find results Improved performance when loading an account with many vaults May 16 Added ability to share items Added item sharing history Recently Deleted now limits deleted items to the last 30 days May 2 Added support for viewing item history Apr 15 Added support for creating and editing items Added categories back to the sidebar Feb 15 Fixed part of the issue firebeyer mentioned with custom item categories. Right now all custom categories will be grouped together under "Others", and we'll be fully supporting active custom categories soon. Group and sort categories in the item list filter menu to match the desktop apps. Feb 6 Began supporting localization for the 12 languages already supported in the rest of the web app and other apps. There are some tasks remaining there. Maintain the last item list sort order throughout the app and across page reload. Show an alert popup when encountering unexpected errors, to hopefully avoid just showing a blank screen like norysang reported. Squashed some minor bugs.
Feature Request: Show Original Contributor of Items in Shared Family Vaults
Summary Please add a built-in way to display who originally created or contributed an item to a shared vault in 1Password Family. Problem In shared family vaults, it is currently not possible to see who an item originally belongs to once it has been shared. This makes it unclear who owns a specific account, even though the item is visible to everyone in the family. As a workaround, we manually add tags with the name of the person who created or contributed the item. This allows sorting and filtering by owner, but it is manual, error-prone, and easy to forget. Proposed Feature Display non-editable metadata such as: “Contributed by: Name” or “Original owner: Name” This information should remain visible in the item details after sharing or moving an item into a shared family vault. Benefit This makes it easy to understand who an account actually belongs to, even when it is shared for convenience. It improves clarity in family vaults, avoids confusion, and removes the need for manual tagging. Reference Apple Passwords already shows this information for shared items using labels like “Contributed by: Name”, which provides clear ownership at a glance.
Support for Imput's Helium Browser
Hiya! I'm an avid 1Password user and I utilize every possible corner of it. BUT there's a certain issue that I'm facing when I'm using it with unsupported browsers. Mainly, Helium Browser (https://github.com/imputnet/helium) which includes unbiased privacy at no compromise to webpage functionality isn't supported. This is an issue because there's no other browser I'd use. The problems that arise are apparent on all platforms, like: Manual addition in the 1Password app on macOS (which, lately, seems to spaz out when using it with the extension) Inability to use with the system app on Windows which inconveniences users by making them log into their vault twice (which, if I guarantee, many have a complex password for and can't bore themselves typing it out multiple times per session) Broken behaviour on Linux, where even with the custom browser config it still can't unlock the vault if it's unlocked on the system. No, I wasn't running the Flatpak version. IMHO 1Password is better than the competition in terms of UX, but seeing my daily driver struggle with that with no way to fix without resorting to this is awful.
The frequency with which 1Password forgets the last-selected collection has suddenly increased
This has bugged me for years, but recently it's got worse. For as long as I can remember, 1Password has intermittently forgotten the last selected collection and silently reverted to all collections. This issue has never been truly fixed. Even when it was supposedly fixed, you could never rely on it 100%. There was always something e.g. a reboot, restarting the app, updating the app, or maybe just not using the app for a while and then using it, that would cause 1Password to silently revert to all collections. For this reason, I'm not going to say this is a regression (because it was never 100% fixed) - but what I will say is that the frequency with which 1Password forgets the last-selected collection and silently reverts to all collections has suddenly increased recently. It doesn't happen every time I open the app, but it is something like an everyday occurrence now - this is on both macOS (1Password 8.12.10) and iOS (1Password 8.12.10). What I don't understand is, why is this so hard? When the user selects a collection, that ought to be sacrosanct. Unless the user selects otherwise, the collection last selected by the user should remain the selected collection until the heat death of the universe, as far as I'm concerned! Why can't it be so? There should be no code paths that alter the user's selected collection.
How to Migrate 1Password Vaults to Bitwarden Folders (With Passkeys!) using iOS 26 CXP
I just finished migrating my credentials from 1Password to a fresh Bitwarden setup, and I wanted to share a workaround for a major pain point regarding vault organization and Passkeys. Those who used 1Password v7 will remember that exporting by vault was standard. In v8, this has been reduced to an "all-at-once" account export. If you want to maintain your organization during a move, this creates a mess. The Challenge: Maintaining Structure If you have multiple vaults (Work, Personal, Shared, etc.) and want them to land in specific Bitwarden Folders, an "all-at-once" export creates a massive, unorganized pile. Plus, standard file exports (CSV/1PUX) usually break Passkeys. The Solution: The "Single-Vault Pipeline" (iOS 26 CXP) By using the newly introduced Credential Exchange Protocol (CXP) on iOS 26, you can move your data app-to-app, vault-by-vault, and keep your Passkeys intact. (Note: I used a 1Password Family account and a free Bitwarden account for this). The Migration Manual: Prep 1Password (Web Browser) Log into 1Password.com on a desktop. Go to Manage Account > People > Select your account > Manage Vaults. The Trick: Deselect all vaults until only one is left visible to your user. Now, your mobile app will only "see" that specific vault. The CXP Transfer (iOS Device) Open the 1Password app on your iPhone/iPad. Navigate to Settings > Advanced > Start Export. Enter your account name (there is a hint at the bottom) and approve. Select Bitwarden as the destination. It will open Bitwarden and securely transfer everything from that one visible vault—including Passkeys and TOTP seeds. Assign to Folders (Bitwarden Desktop) Open the Bitwarden Web Vault on your computer. Click on "No Folder" (this shows all the items you just imported that don't have a folder assignment). Click the "Select All" checkbox at the top. Click the three dots (⋮) above the list > Add to Folder. (Note: You’ll need to create the folder first by pressing the + New button). Rinse and Repeat Go back to the 1Password web interface. Deselect the vault you just finished and select the next one. Repeat the iOS export. Because Bitwarden treats these as new "unassigned" items, you can neatly move the next batch into the correct folder. Why this is the optimal way: Passkeys & 2FA: Unlike file exports, CXP moves the actual cryptographic keys for Passkeys and your TOTP seeds. Shared Protocol: Because it uses a modern exchange protocol, misc info and custom fields transfer much more accurately than a messy CSV. Organization: You don't have to manually sort 1,000 items at once. You do it in controlled, vault-to-folder chunks. Hope this helps someone else stuck in the migration process!
Feature Request: Display Vault Name on Each Item
Hi 1Password Team, I’d love to suggest a small but very helpful UI improvement: showing the vault name as a subtle label on each login item (for example, in the top-right corner of the item view). When managing multiple vaults, it can become unclear which item belongs to which vault—especially when reviewing or moving logins, passwords, or other entries between vaults, collections, or folders. Having the vault name visible at a glance would make organization and bulk management much faster and less error-prone. A lightweight, unobtrusive label would be enough, just something consistently visible without needing extra clicks. Thanks for considering this improvement!
Merging Duplicates
I know that the general response is to manually do this, but doing this with 1000+ objects is impractical to say the least. Some were created because when I migrated to 1Password, some duplicate/corrupt entries already existed in my profiles on Avast, Google, etc, which I did not notice at the time. Unfortunately, some have been created since then by either less tech-savvy family members on their own accounts or how 1Password is asking more often regarding site/app trust & permissions ("Allow fill once") and is thus creating duplicates of its own accord. The fact that merging wasn't already added a while back, considering how many people have asked about it over the years, is interesting to say the least. And yes, I have been attempting to create my own tool for quite some time, but it is difficult to find time to work on it lately, on top of not being successful in general.
