Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
Solved
Support for Zen browser
Hi!
There's this new browser called "Zen browser"
It's based on Firefox but the 1password extension doesn't work with the desktop app
1Password Version: Not Provided
Extension Version: N...
Hello everyone!
Thank you all for the continued feedback! For security reasons, the 1Password desktop app will by default only connect to supported browsers such as Firefox, Chrome, Brave, Edge and Arc. If you're using a Mac then you can add Zen Browser as an additional browser to the desktop app:
- Open and unlock the 1Password for Mac desktop app.
- Click on 1Password next to the in the menu bar.
- Click Settings.
- Click Browser.
- Click Add Browser and choose your browser from the Applications folder.
Adding additional browsers is currently only available for the Mac and Linux. We're not regularly adding new supported browsers individually since that isn't a long-term and sustainable solution however I've shared your requests to support Zen Browser with our product team. We hope to bring the custom browsers feature to 1Password on other platforms (like Windows) in the future.
For the time being, you may still be able to use 1Password in Zen Browser on your Windows PC but you'll need to unlock it separately from the desktop app using your account password.-Dave
Then just manually approve Zen because clearly there is a lot of demand for it here. I'm seriously considering moving away from 1password due to the absolute stubbornness in refusing to provide feature parity in a reasonable timeline nor a stopgap while we wait.
1P_Blake
Community Manager
Community Managergshorr I get that this is frustrating, and I’m not here to dismiss that. But I want to be clear: manual browser approvals aren’t coming back. It’s not stubbornness—it’s a conscious shift in how the feature is designed and maintained moving forward.
We’ve been transparent about the direction here, and while we recognize it’s not the answer some folks want, we’re focused on long-term, cross-platform support through the custom browser feature.
I won’t have anything new to share until there’s meaningful progress on the Windows and Linux side, so if this feature is a dealbreaker for you, we respect that, truly—but continuing to push here won’t change the direction we're headed with this.
- 1P_Blake
gshorr I really do appreciate you sharing your thoughts candidly—I mean that. I also want to be clear: nothing we’ve said in this thread has been intended to come across as abrasive. We’ve done our best to be respectful and direct, even when the answers aren’t what folks are hoping for.
The shift away from manual browser approvals was a conscious decision, yes—and it’s one that’s been communicated publicly for quite some time now. We regularly receive requests to add support for individual browsers, and the reality is that manually approving each one just doesn’t scale. It becomes a constant cycle of chasing new, niche, or quickly-evolving browsers, and that’s not sustainable long-term.
The custom browser feature is how we’re working toward a better long-term solution that’s easier to support across platforms—and that’s the direction we’re committed to.
As for timelines, we understand the desire for more clarity, and if we had one to share for Windows and Linux support, we absolutely would. The reality is that work is ongoing, and the timeline isn’t final—so we’re not going to speculate. When there’s meaningful progress to share, this thread (or others like it) is exactly where we’ll do that.
If this feature is a dealbreaker for you, we genuinely respect that. But at this point, we’ve shared everything we can, and continuing to revisit the same points isn’t going to move the conversation—or development—forward.
Thanks again for taking the time to speak up. We’re always listening, even if we don’t always have the answer someone’s hoping for.
And you have zero timeline for us on feature parity?
Why is it a conscious decision to not do manual approvals? Clearly you see the demand for the feature. Clearly you see people are upset at the lack of communication and transparency.
Right now it's "we're not doing this, we won't say why, and we won't give any timeline on a feature that exists for mac but is 2 years late already for windows and linux".
And the fact that this thread is still marked solved is beyond absurd as it clearly is not solved.
The abrasiveness of the replies and the lack of transparency have already prompted me to stop recommending 1password to friends, family, and coworkers. I list a variety of password managers as options.
Today's interaction is prompting me to seriously look at migrating away completely.
