Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
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
125 Replies
I've returned to using 1Password because there are pain points with Apple Passwords I no longer want to deal with, but I'm so frustrated. I'm just going to have to regularly push for native autofill. As predicted, 1Password Safari on macOS Tahoe is doing the same thing it did this past year on macOS 15.
I just opened my Mac, and clicked the 1Password dropdown in a username field. The TouchID dialogue appeared, and I verified my fingerprint. Instead of showing me login/password options, it showed nothing, and clicking the dropdown again did nothing. The 1Password button on the Safari toolbar remained locked. When I clicked it, it said to unlock 1Password, but clicking the unlock button repeatedly did nothing. I had to quit Safari and restart it, and then it restarted with 1Password unlocked. This is so frustrating. It's honestly ridiculous we don't have native autofill, and having it would make this problem a non-issue. Please support native autofill. And, for those who want the extension or universal autofill, fix the system. It feels like blaming Apple for bugs is becoming an excuse for poor performance.
I've just read through this entire thread and there are soooooo many people asking for native autofill using the official API's.
If there are sooo many people asking for this on a regular basis why are the official replies just "thanks for letting us know you want this, i've have passed your feedback to the development team"?
Surely with all these "passes to the dev team", it should be plainly obvious that this is a feature people actually want.
I know you like to keep cards close to your chest but surely in cases like this, can we have a bit of transparency and just let us know if this is in development or not. If not then just come out and tell us so that we know and people can stop hoping for it.
Posts in here go back over 2 years! Come on 1Password, let us know what's happening with this.
At the end of the day, we're the ones paying for your product.
I think this sums it up perfectly! While I'm now using Apple Passwords, I've left a copy of everything in 1Password in case they add native autofill support. I PREFER to use 1Password, but I prefer the native autofill experience and the greater stability/reliability that comes with that.
I've submitted multiple emails, I've posted, and I've also read the repeated requests over the past several years, and the response is always the same. And I'm willing to continue paying, but not if this doesn't get addressed.
It needs to be implemented, I'm at the point where I'm so fed up with this extension that I will be moving to Apple Passwords even if it means I lose out on functionality.
It's broken - you don't need a debug log to see it's broken; it's broken out of the box for everyone.
- Passkeys don't work 100% of the time to intercept Macs native passkey support - both dialogs appear.
- Sometimes passkeys just don't work on certain sites - Azure cloud services, xbox gaming being among them.
- Quite frequently you will click on an item to autofill and nothing will happen.
- The autofill dialog often conflicts with the Mac autofill dialog and YES I could disable Mac autofill, but then I would lose the ability to autofill 2FA codes from iMessage and Mail.
- The extension is is trying and failing to inject scripts into the DOM.
- Randomly the 1Password dialog will take a reaaaallly long time to show anything - just spins.
- 1P_Dave
Moderator
Thank you for the feedback, I'll share your request with our team as well. I wanted to reply to this:
The autofill dialog often conflicts with the Mac autofill dialog and YES I could disable Mac autofill, but then I would lose the ability to autofill 2FA codes from iMessage and Mail.
Turning off macOS AutoFill shouldn't turn off the filling of verification codes from iMessage. I've just tested this and I still see verification codes from iMessage even after the built-in password manager is completely turned off: Turn off the built-in password manager in your browser
Regarding the other issues that you mentioned, it sounds like you may be running into a couple of known issues that our development team is tracking but I would need to see a diagnostics report to confirm whether you're running into a known issue or a different issue with similar symptoms. If you're able to send a diagnostics report in then the team and I can take a look:
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/161618
- Your forum username: dcrdev
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!-Dave
PB-50688478
I'm just going to bullet point reasons I feel native autofill is a necessity:
- no conflicting with Hide My Email
- no conflicting with email autofill (no, I don't want 1Password to handle this)
- no conflicting with passkeys dialogue box
- no requirement to use universal autofill (I don't personally care for it)
- I prefer using touchID for every autofill
- autofilling security codes from 3rd party apps in iOS 26
- when 1Password Safari has issues, or Safari has issues, users still have autofill via the API
- the issue from this previous year would have been non-issues during the wait for a Safari update
- While the 1Password team have acknowledged and are working on issues with macOS 26, there are similar issues with Safari in that, and, if not fixed before the release likely to be next month, we'll be dealing with this all over again.
- User choice is better: make universal autofill and 1Password Safari options, as well as native autofill
- Some people have different use cases and preferences, including using more than one manager or managing certain things in different places (passwords=1Password, Email and Hide My Email=Apple)
- 1P_Dave
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.
- 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.
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.
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.
