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 h...
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)
