It’s Cybersecurity Awareness Month! Join our interactive training session, or learn about security and AI from 1Password experts.
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
152 Replies
Another +1. 1Password’s own autofill is not quite as convenient as the native autofill (the unlock flow is not as seamless), but worse is that the two cannot coexist. This means that when creating a new account, you don't get the option to use the iCloud Hide My Email feature in the email field.
For now I've disabled the 1Password Safari extension’s autofill dropdown and rely on a keyboard shortcut to trigger autofill. But this is a much worse experience than if 1Password just let me use the native autofill dropdown, like every other macOS password manager does!
I think for me the investment in the safari extensions is throwing good money after bad. I have lost enough time and frustration with it. It is not worth it. I do try it still, but within 1 day if I hit a friction point or bug. And it happens everytime. I turn it off and I go another month. But it doesn’t address the inconsistency between iOS and macOS and autofill which frankly is just weird.
all the good will is gone with the extension. Even if gets better it doesn’t work when you need to use 2 password managers which works on iOS because 1Password supports native autofill.
universal autofill. I use it I like it. No passkeys though. And it doesn’t work for password prompts in iterm2 or terminal. So that stinks.and passkeys well once my wife starts using them that will mean if 1Password doesn’t support them through the native auto fill. I’ll end up having to move to something else which is just disappointing.
I think that is just Safari being Safari.
I switched to Chrome on macOS cause I got fed up with how slow and glitchy browser extensions are in Safari. The glitch extends to all other extensions as well, like the CardPointers extension that I use to enable credit card offers.
But on the other hand, I find myself having to autofill on iOS and it actually works (even if there is so much typing to begin with). It is more tedious compared to Universal Autofill, but if the feature isn't perfectly tuned, or it doesn't work how users expect it to work, what's the point anyways?
I'm just surprised why something so basic isn't implemented but a feature that probably relies on a local model is preferred because of "AI priorities".
From time to time, I would use the macOS autofill feature, just like how I would use it on iOS and I wonder why it's not available on macOS.
I do have the browser extensions installed, but the problem is some websites disable copy and paste passwords and I find it tedious to manually type passwords in so I resort to the right click autofill menu.
Can this feature be made available, would certainly help with accessibility more, thanks!
- 1P_Dave
Moderator
Thanks for reaching out! I've merged your post into the existing thread for the feature request.
Support for macOS AutoFill isn't currently available since our team has historically focused on our two existing filling methods:
- 1Password in the browser: Get to know 1Password in your browser
- Universal Autofill: Use Universal Autofill in apps and browsers on your Mac
That being said, our team is exploring support for macOS AutoFill but I don't have any news to share at the moment.
the problem is some websites disable copy and paste passwords and I find it tedious to manually type passwords in so I resort to the right click autofill menu.1Password doesn't use copy and paste to fill passwords, can you tell me which website filling doesn't work on and which browser you're using? I look forward to hearing from you.
-Dave
PB-50869185
I'm aware that 1Password doesn't use copy and paste to fill passwords. That's why the autofill works when needed.
Yesterday I wanted to sign up to the BLS International website, and normally, what I'd do is create a login first. I don't like having the extension create the login for me (long story short, I'm very particular). Anyways, when the site asks me to create a password, I usually just copy and paste it in, but it doesn't allow me, because the form disables copy and paste!
So in this situation, especially on the iOS devices, I use the iOS autofill to bypass that restriction, but autofill isn't supported on macOS, so I end up having to create a new generated password and the copy and paste it back into the login item.
This feature is useful because 1Password wants to take over the entire experience with Universal Autofill and sometimes it can't and does things in the wrong way. This at least helps me retain control in exactly what I want to paste in, just like how it works in iOS.
This is a feature has been requested for 3 years. and the answer is always "I will send it to the develop team."
There is no further text.
- 1P_Dave
I understand how frustrating it is to wait so long for a feature, and I truly appreciate your patience. Our team takes seriously all features requests but not all features can be implemented right away due to various factors that include limited development resources, bug fixes, and our existing product roadmap.
My colleagues and I on the support team will continue to make sure that everyone's feedback and requests are being heard by the appropriate teams internally.
-Dave
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.
- 1P_Dave
I’m really sorry to hear you continue to run into trouble with autofill, I know how valuable it would be to have autofill working the way you’d like. Your feedback is important and helps guide our future improvements, so we truly appreciate you sharing your perspective.
That said, posting a similar message repeatedly in this thread won’t move things forward and can make it harder for us to track and respond effectively.
For the filling issues you’re experiencing right now, the best next step is to keep working with our support team over email. They’ll be able to dig in with you directly and provide more tailored help. I see that our team sent you a new email a few hours ago, please continue the conversation there.
-Dave
Can we provide an iPadOS version on the macOS app store ? People who need a native Integrate can install that version.
As an aside, I have a photo and recorded video of the issue, and will be submitting a ticket, but I've submitted so many tickets for these issues with fixes either taking months and then recurring or never getting fixed. I love the responsiveness of customer service, but, honestly, this needs to be permanently fixed in a way that doesn't always require months-long waits or updates from Apple. Apple provides a fix--native autofill.
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.
- 1P_Dave
Thank you so much for your patience while waiting for a response. I understand how valuable macOS AutoFill support would be for you. While I don’t have any new information to announce at the moment, this is something that our team is exploring. As soon as there’s official news, we’ll be sure to share it.
-Dave
Well that doesn't help at all! Either let us know it's being worked on, or if it's NOT then tell us the reason why and we'll be understanding of that reason.
What's going on? Just give us some information.
1P_Dave Can I get a response to my post please? We don't want anymore "Passing on your requests to the dev team" nonsense.
A clear answer indicating if native autofill is coming or not, and if not, then at least tell us why. There may be a good clear sensible reason, and if so then I guess we'll all be understanding.
Please don't leave us like this. It's not a great look.
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
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.
