Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
snowy
3 years agoSuper Contributor
Native Password AutoFill Extension macOS
So one of the people in my family subscription for 1P relies heavily on iCloud Keychain. The nice piece about using the native autofill extension is entries from both show up together in-line. This h...
chopin1012
2 months agoOccasional Contributor
I've messaged 1Password support several times over the past 2+ years requesting 1Password to support MacOS native autofill as it does in iOS. Frustratingly, support just glosses over the requests for native autofill support and never actually gives a definitive answer on whether we can expect the requested feature or not.
I would really like to have the request for native MacOS autofill addressed. There are several of us who very much want it, and some, myself included, who, at this point, are debating continued support of the app based on future implementation of this. It has, after all, been available to developers for 3+ years.
Many people struggle with the competing native Mac Passkey pop-up, and the longterm 1Password Safari issue likely wouldn't have been an issue while waiting for Apple's fix had 1Password Mac supported native autofill. Even with the supposed fix, if I connect 1Password Mac to 1Password Safari, I still can't unlock 1Password form a username or password field, and, if already unlocked, I can't get the drop down to offer me any autofill suggestions.
I recently switched everything over to Apple Passwords, not because I prefer it to 1Password--I don't. However, the stability and speed of autofill is, in my experience, far better than 1Password. There's never a glitch with Passkeys, and Passwords never fails to surface logins and passwords. I understand 1Password has chosen universal autofill, but there is a decent number of users who want and have been asking for 1Password to support MacOS native autofill. Maybe give users the option if the two can't coexist.
- 1P_Dave2 months ago
Moderator
Thank you for the feedback! I've merged your thread into the existing thread discussing the feature request. I'm sorry that your experience with Safari hasn't been what we would hope for. If you haven't already, please update to macOS 15.6 which includes fixes that should make autofill more reliable when using 1Password for Safari.
If you're still seeing issues after updating then please reply to the last email that my colleague sent you and the team can dig deeper to find the cause of the issue.
I've messaged 1Password support several times over the past 2+ years requesting 1Password to support MacOS native autofill as it does in iOS. Frustratingly, support just glosses over the requests for native autofill support and never actually gives a definitive answer on whether we can expect the requested feature or not.
We hear you on native autofill for macOS, it’s a feature that's been requested by other folks as well and something that’s definitely on our radar. While there’s nothing public to announce just yet, please know that your voice is being heard and your request is valued.
-Dave
PB-50237134
- chopin10122 months agoOccasional Contributor
Thank you for responding. I appreciate it's on the radar. For me, and I think for several others, it's my strongest request.
As to macOS 15.6, I'm running that on my iMac, and 1Password Safari works as expected. My concern and prior comment are that, on my MacBook Pro where I'm running the macOS 26 beta, 1Password Safari is performing there as it did before the fix in 15.6. I'm concerned that when the stable release launches, that we might end up having the same struggles as before. And, one of the reasons I've been pushing so hard for native autofill integration, is that native autofill would likely work properly whether that Safari issue resurfaces or not.
- 1P_Dave2 months ago
Moderator
Thanks for the reply and for the continued feedback. Regarding the Safari issue, I don't believe that I've seen other reports of the issue from folks using macOS 26 beta, would you mind generating a diagnostics report the next time that the issue occurs so that we can investigate further:
Send a diagnostics report (browser extension)
Attach the diagnostics to an email message addressed to support@1password.com
With your email please include:- A link to this thread: https://www.1password.community/discussions/1password/native-password-autofill-extension-macos/88848/replies/160728
- Your forum username: chopin1012
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!-Dave
- snowy2 months agoSuper Contributor
i have been asking for 3 years...and i just keeping asking about it.
https://www.1password.community/discussions/1password/native-password-autofill-extension-macos/88848
and it seems like this question comes up regularly on the community or reddit. Iam not going to lie it is frustrating as what usually seems like end user drive experience from 1password. They have seem to continue to make the choice to ignore or bump the feature further out and not to support it. And they support the native autofill mechanisms on other platforms (Andriod, iOS, and now windows). On top of that the API for iOS and macOS are the same.
This has effected my workflow for me and my wife for years....Please take the time and implement this.
- chopin10122 months agoOccasional Contributor
Also, native autofill would alleviate lots of recurring problems. The long-lived problems with 1Password Safari likely wouldn't have been a problem. I'm also running the current beta for macOS Tahoe, and, similar to the issue with Safari over the past year, when I go to a website and 1Password Safari is locked, clicking the 1Password icon to unlock in the username field results in nothing: no unlocking, no TouchID prompt, and no master password prompt. I have to click the icon in the Safari toolbar, then click the TouchID icon (it should automatically offer that up), and then select autofill. I'm not interested in using universal autofill. With native integration, this would be a non-issue. I know I'm running the beta, but with a likely release in the next 2 months, I worry about another 1Passwords Safari snafu.
- cyt2332 months agoOccasional Contributor
I read a reddit discussion post by 1password team for feedback . There are people asking for the macos native autofill feature and 1password team replied "2025".
I think they just forgot it.
link:
https://www.reddit.com/r/1Password/comments/1gb81qb/comment/luk5x4n/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
- chopin10122 months agoOccasional Contributor
I appreciate your leaving the link for that. I feel a little cynical as, while Matt_G-1P did reference native autofill enthusiasm, his basic statement was only that they have plans to update 1Password for MacOS in the future. There have been comments on other threads referencing this, and they're never responded to them. I'd love to get a response here that is clear.