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
172 Replies
I moved to StrongBox it has native autofill support and has ssh agent support - which is the only thing keeping me tethered to 1Password. Last straw was the massive price-hike, if the Safari extension was not horrendously unstable and/or native autofill was implemented, I wouldn't have switched.
Although I prefer 1Password's features and UX, especially the developer tooling, I will be migrating to Passwords.app for personal use due to the lack of native autofill support on MacOS.
I'm an OG 1Password user of over 20+ years. Probably back to version 2 when it was still called "1Passwd". For decades it has been "indispensable" software on the Mac platform ... but it just isn't anymore. It's still more full featured than Apple Passwords, but when it comes to the basics it's now falling short due to the foot dragging with native autofill support on macOS and the ongoing conflicts with the native passkey implementation. Time and again these issues have been reported but not addressed. And look I get it. Since AgileBits took the VC money they are more focused on the Enterprise market and not the loyal Mac users whose support was used to build the company. That would be fine if we had all the functionality we needed as Individual and Family plan users. And normally I would not have minded the recent price increase because I recognize they haven't had one in several years (and because they have to pay for all the new developer features I will never use). But a price increase of that magnitude when this thread is 3+ years old and counting with no indication whatsoever that they are going to deliver this much requested functionality means I'm now officially at the point where my patience has started to wear thin. I finally managed to get my wife onto the Apple platform last year. Now I'm eyeing the newly announced iPhone 17e for my mother who is currently using some random, AT&T store Android. When I pull the trigger on that my entire family will be in the Apple ecosystem and I'll no longer have any need for cross-platform support. The Uplock app fills in the gaps for the various categories that 1Password supports that the Passwords app doesn't for a significantly lower price. And while the Passwords app has a few shortcomings I've encountered while test driving it over the last few months, it's much easier to swallow that from a free app than one you are paying for on an ongoing basis.
So yeah. I just decided tonight that if native autofill support on macOS isn't addressed by the time my subscription renews in May I'll just have to reluctantly move on to the first-party Apple solution.
Trust me, is not just the home user. I’ve been using 1Password V5, and I manage two business accounts and we are also ignored so we are looking for alternatives.
One additional place 1Password's auto fill fails but native succeeds is in the Windows App (formerly Remote Desktop) (https://apps.apple.com/us/app/windows-app/id1295203466). When I remote into Windows and want to fill in a UAC prompt or unlock the desktop, Cmd+\ asks for permission to use the password I select and I approve but nothing happens.
If my password is in Passwords.app, I can go to Edit > AutoFill and it fills as expected. (Maybe it's virtually invoking key presses or something? Or maybe it's doing private API stuff?)
What does this mean?
If you like to have secure and convenient access to the EU login, you either have to choose an "expensive" hardware device, like a yubikey, or turn to other products, which will mostly do, what 1P does, but also support native Autofill - like Apples own Passwords.
Companies will provide their staff with a reasonable priced product, which meets their demand. EU login is going to be used by a broad range of companies as it is becoming mandatory for regulations. On May, 21st, EU regulation 2024/1157 will have to be obeyed and waste shipment across internal EU borders will have to be registered in a central EU system by companies. Guess what: to access the EU system you need an EU login and use 2FA.
To be honest: most private persons use only the plain Password Manager in 1P, enjoying that it supports Passkeys as well. But I see more and more national and EU administrative services forcing a secure Passkey storage. And on macOS this triggers Autofill, the other option being a hardware key. Given that Apple Passwords will do that...who will turn to another product which costs, but won't support this?
I am not sure, but I think I have seen this movement on Microsoft Cloud services as well, where I can't use 1P for Passkey anymore. Have to look this up...
Today's status update highlights one more reason 1Password developers need to prioritize Safari Native Autofill on MacOS:
1Password Browser Extension Code Syntax Rendering Issue
Jan 23, 2026 at 12:04 PM
Resolved - The 1Password browser extension, which works by injecting code into web pages, inadvertently included code from PrismJS, a third party dependency, breaking syntax highlighting on some websites that display code blocks.I do not want an extension injecting unnecessary Javascript into every web page I visit, and certainly not inadequately tested 3rd party Javascript. The next time this happens, the third party code could inject a security vulnerability, and not just a formatting issue. Surely a security focused company should understand why this is an issue. And yes, I know about Universal Autofill, and I don't want to give 1Password accessibility permissions either. Why does a security focused company have so much trouble understanding the https://en.wikipedia.org/wiki/Principle_of_least_privilege?
As a bonus, support for Safari Native Autofill on MacOS will give a far better user experience. I'm not even going to get started on the frustrations created by the UI of the 1Password Safari extension.
I'd like to chime in and put a +1 for supporting the native macOS passwords system. Even with the autofill turned completely off in Safari and in System Settings, the Apple passkey prompt comes up in Safari when requesting a passkey. Sometimes it can't even find the 1Pass passkey, as in this screenshot. It basically makes passkeys unusable for macOS users who prefer safari. Chrome and other browsers work fine.
It seems like you should support this screen for the most consistent macOS/iOS experience possible. I am an affiliate and professional supporter and cheerleader for 1Password and encounter this problem almost daily... still now years after the ability was introduced by Apple.Hi there 1PW team. Please could we have some indication here about whether or not the "2nd attempt of native MacOS autofill" that you alluded to in the last AMA is heading in a positive or negative direction?
All of us in this chat really would love this feature (as many of us have said many many times) so a small progress update / state of play update would be appreciated.
Thanks
Today I discovered that Bitwarden is implementing native auto-fill system integration for macOS. They are using an additional extension written in Swift to achieve system integration and communicate with the Electron client via IPC to exchange data. I think this should be very valuable for your development team as a reference.
+1
+1, I would love it!
- 1P_Dave
Moderator
Thank you for sharing your request!
-Dave
PB-51858364
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".
