Native Password AutoFill Extension macOS

For companies and persons in the EU using macOS to access EU services 1Password will no longer be an option, for using 2FA with EU login with Passkeys - the most secure and convenient method -  is not possible. The relevant web pages will trigger native Autofill.

Sorry 1P. 

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

+1, I would love it!

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.

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!

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.