Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
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 happens on iOS (or if you use other password managers it secure by each provider but both are offered the same way together).
in terms of migration and allowing those who wish to use both depending on the context. It would be nice to support the native autofill extension, but further it limits exposure or need for safari extension. Should someone not want to use or can't install the extension due to work policy or just rather not use safari extensions
thanks.
1Password Version: 8.x
Extension Version: Not Provided
OS Version: macOS 12.6
Browser:_ Safari
161 Replies
- 1P_Dave
Moderator
Thank you for the request! I've passed it along to our product team.
The 1P extension for Safari is clunky and dysfunctional, while native autofill on iOS/iPadOS works great.
Can you tell me a little more about the issues that you're running into with 1Password for Safari? I'd like to help further or identify if you're running into a known issue.
is there any section where we can upvote feature requests?
All feedback is shared with, and considered by, our product team. We don't currently have a public voting system for feature requests since that could give the wrong impression that features are built only based on what has the most "votes" at a given time. Voting systems are also prone to being gamed. Discussions such as this allow us to better understand the need for specific features.
-Dave
Hello 1P_Dave, thanks for your answer. Got it about the voting system, you raise valid points.
As to the issues with the Safari extension, nothing different from what has been reported by many people on this thread already. Sometimes the extension won't unlock properly, sometimes it will but it won't fill passwords in, sometimes it's out of sync with the main 1P app.
The Chrome extension tends to be far more reliable, although I've run into syncing issues with it too. Worth stressing that I don't encounter the same problems on iOS/iPadOS, only on macOS.
I am pretty sure I have answered once before. Simple.
Personal and work. Work uses one password manager and I personally use 1Password.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.
https://1password.com/blog/autofill-on-big-sur is from WWDC 2020... It looks like there was a working demo of native Autofill back then. I get that the accessibility API mostly works most of the time, but one of 1password's biggest strengths used to be its tight integration with macOS, so to see this go unaddressed for more than half a decade is disappointing.
The reason I found my way to this thread is because I just discovered that the accessibility API doesn't seem to work with iPadOS apps running on macOS. Also cmd-\ often just stops working altogether.
- 1P_Dave
Welcome to the community! Our Group Product Manager Travis recently shed some light on our explorations with macOS AutoFill in our Reddit AMA:
We've been taking a heavier look at MacOS autofill in the second half of this year to see if the limitations we encountered previously have been alleviated or if they're still present. Although not perfect and not where we ideally want it to be, integrating with native MacOS autofill is looking promising. If we're able to have our concerns addressed with the API to ensure 1Password customers can seamlessly use MacOS autofill without fear of falling through the cracks, I don't see a reason to not integrate in the near future.
1Password 8 is more tightly integrated with macOS than any previous version with features like Universal Autofill and 1Password for Safari (a modern web extension using the latest Safari extension technology). The team will continue to explore ways to deepen that integration with features like macOS AutoFill.
-Dave
PB-51721802
- 1P_Dave
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
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.
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.
More reasons for your development to consider speeding up the API development:
https://www.macrumors.com/2025/06/12/ios-26-macos-tahoe-expand-one-time-code-autofill/
My subscription comes to an end in November which is a month or two after these Apple releases their new OS updates. I hope by then this is solved otherwise I am certain I'll back jumping back over to Apple Passwords for good.
It's been 3 years, the autofill API has been enhanced with passkeys even, and 1Password doesn't even bother telling us a simple "yup, we're working on it" :(
is there any progress yet ? I don't want to hear you guys repeat "I have send it to our develop team". I need a definite answer. will you add this feature or not.
Considering I can find 2 years worth of complaints about this on multiple boards including this one, leads me to believe it's not coming and is not a priority. They are focusing on fixing the Safari extension based on the response I got and not disbanding it and working on the native auto fill that would basically make the Safari extension unnecessary.
It's sad because otherwise 1Password is a great manager but considering Apple is giving us an option that's built-in now it's hard to keep dealing with this issue as a Mac and Safari user, my subscription is annual so I will slowly move over to Apple Passwords between now and my subscription expiry in November and not renew any further.
the safari extension is totally a disaster. it never works as well as the chrome extension. I don't think they can make it better for it has already take so much time.
- 1P_Dave
I don't have any news to share to share, we tend to keep new features close to the chest until they're ready for release. This helps us from disappointing folks if a feature is delayed or cancelled. For the time being, the two available filling options for the Mac are:
-DaveThe extension for safari never works as well as it in the chrome. Consider it has been a long time since its first release. I think it also hard to be as good as it in chrome in the future because of some limitation in safari. The native autofill will make 1password experience in safari much better.
That's my opition.
+1
On macOS 15.5 Beta die 1P extension in Safari is not working properly. Native autofill is the way to move forward.
I use hide my email functionality on my iCloud account - native autofill supports generating these. Every time I go to use it 1password conflicts with the form field. Every suggestion is to turn off native autofill - but this is a poor suggestion as then you lose out on this functionality.
Additionally for the second time in a year 1password for Safari is completely broken - passkeys don't work, takes 30 seconds to sync, stops working after first autofill. Really seems like the safari extension is an afterthought.
Are there any updates in this? I.e., native macOS-integration.
The current solution does not work for webauthn-credentials in system native webviews, which makes 1Password a no-go for quite a wide swath of applications.
- 1P_Dave
I don't have any updates to share and I've passed along your comments to the team internally. Thank you for the feedback!
-Dave
Do you have an update on the topic?
In addition, native integration would also be less confusing in scenarious where multiple stores are used at the same time, for example you have private logins in iCloud, often used work-related stuff in 1password and seldom used stuff in secure elements (such as yubikeys).
One list in native macOS style which shows all matching credentials regardless of store would greatly increase usability.
Native Autofill support on macOS is a no brainer! The 1PW Safari extension should be an option ... not a requirement ... particularly since it's so temperamental. It's downright frustrating having to constantly deal with the inline autofill functionality the extension provides suddenly refusing to unlock or stay connected to the app. Apple has put all the plumbing in place and done the heavy lifting. 1PW just has to make the decision to use it for consistency in the Apple ecosystem if for no other reason.
- 1P_Dave
Thank you for the feedback, I've passed your request along to the team internally.
It's downright frustrating having to constantly deal with the inline autofill functionality the extension provides suddenly refusing to unlock or stay connected to the app.
I'm sorry that 1Password for Safari isn't working consistently on your Mac. The next time that you run into one of these issues, so that the team and I can help further, I'd like to ask you to create a diagnostics report from 1Password in your browser:
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/154739
- Your forum username: OAW
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!-Dave
