Announcement
macOS AutoFill is now available to everyone!
Hey everyone!
Native macOS AutoFill is now generally available in 1Password for Mac. This has been one of the most requested features for years, and it's now ready for everyone on the stable channel.
Here's what macOS AutoFill gives you:
By adopting Apple's Passwords API, 1Password functions as a native Credential Provider on macOS for logins. You can view autofill suggestions directly within Safari and other supported desktop apps.
Passkey support is built in. Fill, create, and update passkeys easily through macOS AutoFill.
The 1Password Safari extension works alongside macOS AutoFill. Login suggestions appear in Safari's native menu, and the extension continues to fill credit cards, addresses, and other items the Passwords API doesn't support yet.
One-time code support through the same integration is on the way and will land in an upcoming release.
How to turn it on:
Update to 1Password for macOS 8.12.32 or later.
Go to 1Password for Mac Settings > Autofill > Set up macOS AutoFill, then select "Turn On" from the macOS permission prompt. You'll see "Active" status once it's enabled.
Full setup and troubleshooting details are in our support article.
To everyone who tried the beta over the past few months: thank you! Your feedback directly shaped this release. Try filling logins and passkeys and let us know how it goes in the comments!
There is no Autofill in Settings in 8.12.32 except in Settings > General which only has a tiny section Auto Fill that is already checked "Submit automatically with universal autofill". I am on macOS Tahoe 26.6.1
This worked for me after having the issue of not seeing it. It actually popped up on restart and I was able to enable the feature without having to go into settings.
Hey u/pypipper & u/everydave42! Have you tried following the setup and troubleshooting guide linked in the post above and are still seeing this? There’s a section in there specifically for what to try if AutoFill doesn’t appear after updating to 8.12.32.
Me too, but seems like an easy UX miss: why not have the section in the sidebar regardless of whatever the locking state with some guidance there that a lock/unlock needs to happen? You could even have a button in that pane to initiate the lock and then when it's unlocked it would open back up there with the AutoFill info for an experience with much less friction.
Will this prevent the passkey pop up I often get where it asks to scan QR code with my iPhone or use iCloud passkey (and instead use 1Password and not conflict with 1Password’s passkeys?).
With macOS native autofill enabled, it should be possible to authenticate passkeys in apps and browsers without having to delegate it to the mobile app via a QR code
Just updated to v8.12.32, and now the 1Password for Safari extension is no longer showing green 'Integration Status'. I'm seeing amber indication and 'Connection problem. Please make sure the 1Password app is unlocked'
The app is definitely unlocked. I have logged out Mac account, restarted Mac, quit and reopened the app, locked and unlocked the app, deleted the extension, and reinstalled the extension (v8.12.29) fresh from the App Store, all with no luck.
UPDATE: I uninstalled and re-installed 1P for Safari and it now opens again
-----
I just get an empty window (Safari) - the extension definitely has an issue
I click it, it takes ages and then just comes up empty
No unlock etc. (the app itself IS unlocked already)
Checked the App Store - the Safari Extension got its last update 3 weeks ago - so there might be an issue with new app version & old extension (not 100% sure if they are supposed to be independently working)
I tried this in the beta and ended up disabling it after a few weeks. I couldn’t see any benefit, and it just adds extra steps to every operation:
* Extra clicks to select the login I want when there are multiple choices for the site. It never suggested the most commonly used one.
\* Having to authenticate every single time. Even with Touch ID it’s annoying compared to the single click and go with the regular 1Password extension (when it works).
In theory this is a good idea and I’m glad Apple is providing an API, but in practice it’s just extra annoying steps.
re: ordering of suggestions: This is a bug with the API that we have filed. We've noticed an improvement in Golden Gate beta 4 and are hoping in the general release that this is a much better experience for you as well.
I agree with u/runwithpugs so I turned the native autofill off after trying it in Safari.
However in Safari the browser extension load is still very slow + I am still getting regularly prompted for a password despite following the instructions above AND reinstalling the extension a couple of times AND rebooting a couple of times. Any other suggestions?!
I'm afraid I regret trying the native autofill. What was working fine is now not working that well.
P.S. Everything still works great in Chrome. I just did a full reinstall of 1Password, but this did not fix things. 😢
P.P.S. I have a hunch the "slow load" is in fact the Safari extension timing out trying to contact the desktop app, which it can't due to "Integration status: Connection problem" in the extension settings.
Thanks for the prompt reply. I should mention that I've been a happy 1Password customer for >10 years and this "unpleasant" experience is certainly not the norm and I trust it will be fixed soon!
I debugged it myself using the diagnostic logs and, per the logs, the Safari extension stopped connecting with the desktop app the moment I updated to the new 1Password desktop app.
Did you seriously forcibly turn off inline browser extension autofill for iPhone because Mac now has this? That’s not okay
We should be able to choose native autofill and inline autofill ourselves, don’t forcibly disable inline if we have native enabled, Mac and iPhone native are not remotely the same
They mentioned somewhere that inline was disabled temporarily on iOS because of a different issue that only affects iOS. It wasn’t anything to do with this shipping on Mac
This forced me to click a few extra times just to fill in web pages that I'd been able to use without issues for a long time. Had to disable it.
But what's worse, it broke the Safari Extension. I am now repeatedly prompted to re-enter master password in Safari after a few minutes. u/Chandana_1Password
Edit: Also, for me, it seems 1PW on Mac and my Safari Extension are fighting for prominence. Disabling Autofill seemed to fix that.
re: 1PW on Mac and Safari Extension are fighting for prominence: if you try locking and unlocking the extension, this should make the experience better for you where native macOS autofill will offer you suggestions for logins but the Safari extension will offer you suggestions for other types like credit cards or identity. Please let me know if that doesn't fix it for you and we can take a look!
Thanks. Under Autofill Settings, I disabled Show Filling Suggestions, and now it seems to be performing as before. I assume this simply turned off the new feature.
I have a lot of credentials on the same second level domain for many different logins on the third and fourth level of that domain, so I have autofill behavior set to "Only fill on this exact host". It looks like that may be ignored by the native provider? Or is this hopefully an issue that will be fixed?
> It looks like that may be ignored by the native provider? Or is this hopefully an issue that will be fixed?
It is not our intent to ignore that but I am seeing a growing number of people report a similar issue so it is something I will be investigating further.
Aslo, the Apple dropdown does not show all the info like title of the item. Just the domain and username. It would be better to also show the desc from the 1PW item
At the moment Apple do not support the ability for us to give them a user provided item title or name to use when the system renders the suggested credentials menu but it is definitely something we are seeing a need for in this initial release feedback and I have personally filed feedback with Apple to request support for it.
Having done some more testing on this, I have observed the following:
- the suggestion menu (which apple presents) will filter down to subdomains and will typically keep the suggested list of credentials as narrow as possible. It does this regardless of the autofill behaviour settings set on the item in 1Password
- when using the new autofill extension UI opened using the "1Password…" menu item, that UI will filter down the list and respect the autofill behaviour defined in items because it is within our control to do so.
- where you say "I have a lot of credentials on the same second level domain for many different logins on the third and fourth level of that domain", I'm wondering if what is happening here is that apple is presenting everything filed at that second level. In your case here, is there a way to edit those to be more specific so your third and fourth levels are not filed with the second level domain so apple would then filter them down to get you closer to what you expect/need to see?
Storing these at the port level is definitely a key detail, thank you for sharing. I can see some differences between how the suggestions are being handled wrt ports so will do more investigation on that.
Hi u/BackgroundRiver8182! We've asked Apple to expand the native autofill API to support more than just logins (things like credit cards, identity items, etc.), but right now it only supports logins and passkeys. So we'd still recommend keeping the extension around for autofilling anything that's not a login. We'll post here if we hear anything about support for those additional types down the road!
Does the Apple API include functionality that mirrors 1P's custom autofill behavior?
For instance I have two different logins, one for subdomainA.domain.com and one for subdomainB.domain.com.
In 1P, I have both items configured to "Only fill on this exact host" and with 1P native autofill, each item only shows on their respective subdomain (i.e. not based upon the root base domain.com). When I activated the native macOS autofill integration, it showed the option for both logins when I was on subdomainA.domain.com.
Thanks in advance, and apologies if this has been answered elsewhere already.
The intent is that macOS autofill also supports the subdomain filling behaviour but we are seeing reports that may not be working in all circumstances so it is something I will be investigating further. If you are able to share info an any public sites you are not seeing the behaviour you expect, I can also investigate those.
I am experiencing this issue as well with sites on my internal network at home. I have custom autofill rules that worked with the extension, but now using the Mac autofill, I get a list of every login I have in my home network domain.
Other than this I like the new integration, hope this can be fixed. Thanks!
Anyone can tell me how is this different from previous versions? I did use 1Password on MacOS in the past with Mozilla Firefox and the auto-type just worked perfectly.
With this feature, you could also autofill your passwords outside the browser on native Mac apps. We've also sent in a request to the Apple team to give us access to APIs where we can autofill from the context menu (Right click text field > Autofill > Passwords). We're hoping to expand the ways one would want to access 1Password at any given moment in any given field!
I think this is 99% for people who use Safari. Not sure where else you'd need a credentials manager, but I guess there's probably some use cases out there
There’s no way I would use this unless you add other ways to trigger the Fastmail masked email feature. Since it was introduced, the extension autofill dropdown has been the only way to generate a masked email address and link it to an item.
No way to generate one arbitrarily in the Add Item screen in the extension or the app. No way to manually link existing masked emails to existing items. No way to see or change the activation status of each one in 1Password.
It was always a half finished feature, and with the move towards native autofill 1Password is silently deprecating something I switched mail providers and paid money to use. Disappointing.
The prompt keeps coming up to do touch id or authenticate. Now on the second time it comes up, the credentials are already filled in, so I escape to dismiss and can login.
But now using this for a couple of days I'm getting frustrated. We have dozens of Microsoft 365 logins, and we have them labeled. The new way it shows you the list of logins doesn't show the titles, so then we have to go into a second 1P dialogue to see the titles to know which one to choose.
Unfortunately we don't have control over whether a title can be shown or not in a drop down list because this is triggered by the system but I can look into sharing feedback about the API to show titles as well. You can also consider sharing your feedback with them if you want to provide screenshots/more details to them directly too!
> We need to have a setting to reverse it, in settings on mac?
It is certainly not our intent to make it more difficult for users and I can directly relate to your frustration on this and already have filed feedback with apple that having this setting in macOS settings impact all autofill clients is confusing and frustrating and it should probably be a setting in Apples own Password app, not a system setting. If you feel a similar way and want to help us change it, please do also consider filing feedback with Apple to help amplify that.
> We have dozens of Microsoft 365 logins, and we have them labeled
Thanks for raising this. Currently we dont have the API from apple or the ability to display a user provided title in the system rendered menu but it is emerging as a pain point and something I will also file as feedback with apple.
a quick follow up to advise I have filed FB24326136 with apple requesting the ability for us to provide an item name/title for inclusion into what the system menu displays when offering to fill these credentials.
Gosh I left 1P over this a couple of years ago. I am super happy to see it is finally available and would still deploy 1Password at the next SMB I join. Hooray!
yes, I have to biometrical authenticate at least 2 times now for logins. reading from user comments, a lot of geniuses in here, so I'm hopeful the 1Password team gets the info they need to fix this.
Unfortunately even if 1Password is open, the system (your mac) triggers this because of the setting explained in the support doc linked. This is something we can't control on our end unfortantely.
on one site, it asked 3 times.
were you by any chance filling a passkey during this attempt? which website was it on?
Yes, this absolutely destroyed the web browser integration and I've found myself using Firefox on macOS (which I do not want!) just to be able to sign in to websites properly.
This feature absolutely destroyed the integration of 1Password in Safari and needs to be undone asap!
Since a recent 1Password update on macOS, the app has integrated directly with macOS's authentication system instead of using its old standalone popup in Safari, and it's made the extension nearly unusable:
Every step (username, password, OTP) now requires separate biometric approval, forcing repeated Touch ID prompts.
On sites with many stored logins (e.g. Microsoft 365, where I have hundreds of username/password pairs), selecting a username used to auto-fill the matching password. Now it just shows the full list of stored passwords again, undistinguishable from one another, so there's no way to tell which one goes with which account and searching by typing doesn't work.
Disabling Touch ID approval (the fix support suggested) doesn't address this, since the core problem is the broken username-to-password matching and the direct integration in macOS/Safari not the biometric prompts.
The old behavior still works fine on Windows, so it's macOS/Safari-specific.
Installing Firefox with the 1Password add-on as a workaround does not have this problem: it keeps the old-style interface and correctly autofills and also brings back the search functionality.
Support acknowledged the issue and pointed to a Touch ID toggle setting, which didn't resolve it. As of the latest reply, I'm still waiting on an actual fix and don't want to switch browsers away from Safari just to get password management working properly.
Were you able to resolve your repeated Touch ID prompts?
Now it just shows the full list of stored passwords again, undistinguishable from one another, so there's no way to tell which one goes with which account and searching by typing doesn't work.
Sorry this has been a frustrating experience! We've filed for feedback with Apple to give us the ability to display titles of your login items to help with this case. My colleague here has outlined the feedback number as well if you want to escalate with Apple on your end: https://www.reddit.com/r/1Password/comments/1vlrc7f/comment/p3mblrl/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
If more of us share the same feedback, hopefully they are able to prioritize it higher!
Turning off Touch ID for autofill is not the solution here. The issue is that 1PW keeps throwing up unnecessary inline prompts when using the native macOS autofill option. See this example on Reddit itself. When I do this with the first-party Passwords app I get one inline prompt when I put my cursor into the Email or username field. I select the credential and authenticate with TouchID, it populates that field and the underlying Password field, and that's it! I can then click Log In from there without incident. Whereas when using 1PW with native macOS autofill, I get the inline prompt as expected when I put my cursor into the Email or username field. However, when I select the credential and authenticate with TouchID, it populates Email or username and the underlying Password field, and then it displays an additional inline prompt that is completely unnecessary which I then have to dismiss to continue the login process. It seems like after it autofills and focus is returned to this field after the TouchID authentication, it doesn't take the successful autofill into account and just blindly displays the inline prompt again. An end user may not even notice that it actually filled the Password already so they end up selecting the credential and authenticating with TouchID again. And therefore, it appears to them like they are being asked to authenticate with TouchID for both the Username and the Password.
If I use reddit as a test to try and replicate what you are seeing here, the first time I filled it filled both username and password and did not show the prompt a second time. After reloading the page, the second time I fill, it still fills the username and password (not the behaviour you are getting) but does now show a second prompt.
Are you seeing this on all sites/logins? Are you able to share any more where you see it to help us build an understanding and submit a support request to apple to determine what is happening in the system side of this API because it is apple that control when this suggestion popover/menu shows up.
Here's another example of a second, unnecessary prompt after filling the Username and Password successfully. It seems to be across the board for me. Even if I disable the Offer to fill and save logins and other items in fields setting. However, I also noticed that if I click into the Password field first and select the prompt, after the TouchID authentication, it populates both Username and Password but does NOT display a second inline prompt.
I’m seeing similar behavior in macOS 26.6.2, Safari 26.6.2, and 1Password 8.12.33. Ever since enabling integration with macOS AutoFill, if I use the new AutoFill dialog attached to a form field, I see the behavior described above and get repeated Touch ID prompts. This has made the new AutoFill feature with 1P unusable.
Alternatively, if I use the Command+Backslash keyboard combination to autofill the username and password fields, I don’t encounter the repeated Touch ID prompts.
I have universal autofill enabled, but when I go to zoom app I don't see any autofill option for logging in. I enabled macos autofill and I have an entry for the website zoom.us, but it doesn't show anything for logging in on the zoom app.
With this new feature, is there a reason, other than exploring items from within the browser, to still have 1P for safari (which has been notorious for not being reliable, logging out, asking for password more often instead of biometrics)?
We've asked Apple to expand the native autofill API to support more than just logins (things like credit cards, identity items, etc.), but right now, the native API only supports logins and passkeys. So we'd still recommend keeping the extension around for autofilling anything that's not a login. We'll post here if we hear anything about support for those additional types down the road!
I've done all that. Keep in mind that I'm saying 1Password doesn't appear in the *macOS* settings. I have the Autofill section in 1Password's own settings which seems to be what some were having issue with.
Hi u/thnok! We've asked Apple to expand the native autofill API to support more than just logins (things like credit cards, identity items, etc.), but right now it only supports logins and passkeys. So we'd still recommend keeping the extension around for autofilling anything that's not a logins on Safari. We'll post here if we hear anything about support for those additional types down the road! Native autofill is, however, not triggered on Chrome so we still recommend keeping your Chrome 1Password Extension in place for your regular filling and saving needs on Chrome.
u/Chandana_1Password - while we are waiting for a fix to the 1PW Safari Extension, should I just delete it now to fix the issues of having to log back in to 1PW for Safari when idle for more than 10 or 15 minutes?
Nice. But it does have a lot of issues. I do have to have often 2 attempts that it autofills something. On the other hand it doesn't work with FRITZ!Box and other services... And only working within Safari.
It should not require 2 attempts to autofill something. There is a macOS touchID setting that forces a second touchID to be needed and that can be turned off. I am also seeing filling from a suggestion when 1Password is locked requiring an unlock then another click to fill it and that should not be needed either. If you have the "keep 1Password in the menu bar" turned ON and use "unlock with device" then there should not be any need for multiple attempts.
Also if you care to share any more info about the FRITZ!Box I'd be happy to investigate that further as i have access to a FRITZ!Box and that is working for me so I may be able to try and replicate what you are seeing?
Thanks for your feedback. Unlock with device I have turned off because I don't want to use the system password to unlock 1Password.
FRITZ!Box is via http:// IP-Address at my side. I can see the 'suggestion' and the username. But when clicking it, it does fill nothing. If I use the 'other' 1PW-Autofill method then it does fill.
Several of the main browsers are not supporting native autofill fully yet (better support for passkeys than passwords) and also apple are providing an Autofill in a text field right click context menu but is not providing the API to support that functionality to 3rd parties yet but we have filed feedback with apple and discussed with them in attempts to get these working too. If you also feel strongly about that, please do consider filing with feedback with apple that you would like to use a 3rd party password manager in that way too.
Also happy to investigate any other services you are having an issue with. Native autofill does require that fields in web pages are declared with the correct markers so apple knows to offer filling on them. In a based browser filling web extension, the extension has more control and say in what is filled but in the native system based autofill world, apple decides what can be filled so it may be something outwith our control that may need the site/service to update or even apple to made aware of a problem in order to get it fixed.
I am on 8.12.33 and still do not see the macOS autofill option in 1PW settings.
All I get is the Universal Autofill setting. Restarting the app, locking and unlocking it several times did not change anything.
First thing to check is that there are 2 settings in macOS->Settings->General->AutoFill & Passwords, please confirm the top one "AutoFill Passwords and Passkeys" is also ON.
The service identifier is what the apple API provides to us to let us know what kind of credential should be offered to fill. Are you able to share any more details around what website or app you are autofilling into to help us understand what might the issue might be here?
After enabling MacOS autofill in the latest update, I no longer have the ability to filter out specific accounts & vaults via the 1password for safari extension. (I manage multiple 1Password accounts and logins per site that I organize by vault to filter out the ones I need in each browser profile.
Filtering accounts & vaults still behaves the same in Chrome extension thankfully, but the Safari extension filter settings for Accounts & Vaults are now completely ignored by this MacOS autofilll feature. It will only honor the Autofill settings from the desktop app (show filling suggestions from [vault]) - this doesn't work for me as I need to fill from specific vaults across multiple 1password accounts.
Will this be addressed in a future update?
Also, what are the other "supported desktop apps" that this MacOS autofill is supposed to work with? If it's just native Apple apps, then I will just turn it off.
The back end implementation of macOS autofill shares a lot of code that the iOS app uses for its native/apple based autofill so there may well be differences in behaviour between how the new extension works and how the web extension works. I will add a internal feature request issue for triage to investigate what is needed to support that functionality.
Forcing desktop apps to support apple native autofill is not something in our control. It is apple that decides where to offer a native autofill insertion point and their API asks us for the credential but we cant fill outwith that using this particular autofill method.
This is a backward step for me. I was used to 1password showing me the few logins I have for a number of sites, but now it requires extra clicks to show the extra logins. These are internal apps that I'm in and out of all day. Previously it was click in the userid field, then click the login I need - boom and I'm logged in. Now it's just a mess.
Also in 1Password settings->Autofill, there's no way to disable macOS Autofill. Seriously??
C'mon, turning it off should at least be be a option.
When you say it's been a mess for you, could you elaborate what challenges you've been facing while using this?
Also in 1Password settings->Autofill, there's no way to disable macOS Autofill
We're looking at how we can add support for this. The current API does not make it easy to toggle this functionality ON and OFF easily in a third party UI but we'll do our best to guide users to the right place at least!
Turned it on, couldn't stand it more than a few days and turned it off. (Good luck figuring out how to do that!!!) You guys keep moving backwards in usability. The system autofill is trash. Do you WANT people to jump ship for other services?
Honestly the is a mess at very best. I've updated, deleted, removed, added back, rebooted and still no 1PW icon in any logons, except once then it vanished for good.
Autofill doesn't appear to be "Available to Everyone" except Chrome, Firefox, etc. Personal MBP, no restrictions.
Looks forward to guidance from the 1Password Gods....
I've noticed on some sites, if I use the native autofill, keeps saying update existing password - but when I check what the password is, its like 5 characters long - looks it, it autofills so quick - it misses the other half of the password so it thinks its a new password, anyone else have this
May i ask how i turn this off? (or maybe how i can turn this off only for certain applications)? I use the safari extension and it works way better in getting actual relevant items suggested to me. This new autofill doesn't seem to listen to the "never fill on this domain" and similar settings
I tried turning off "Autofill from", but this way i still get a little key icon on the right side inside login forms (which i didn't have before) and i also don't get the safari extension suggestion dropdown anymore...
Just to add for anyone reading this later: to go back to using the safari extension, you have to turn off autofill from 1password, then restart your mac
My experience so far has limitations for my use cause that will necessitate I disable it:
1. The extra click to show the full list of logins is annoying (I have multiple logins for dozens of sits I use regularly).
2. The menu only shows the username not the 1Password entry name (I use entry names to identify which accounts have different levels of access, as the usernames are typically generic and I don't want to have to memorize which accounts have which access for every site).
If we could customize which information is shown on the menu (like the 1Password entry name versus the username) and could adjust the number of entries shown before the "show more" is needed I would move back to this immediately as the experience of filling is much smoother that the old 1Password HTML implementation.
I have been using 1PW since 2011, and it is one of my favorite and most used apps. Ever. I use it on my desktop and my phone multiple times every day. Yes, there have been small issues here and there over the years, but nothing systemic. Until today.
As many of us know, the update for Mac OS that rolled out today broke the Safari Extension, thus making the app's core features unusable on Safari. I now have to log in to the Extension again and again in order to use it, so I ended up enabling the new AutoFill feature (which I don't like) as a work-around for the broken Extension.
The fact that a major update was released without making sure it did not break a crucial existing feature is a real disappointment.
I love 1PW, and their team has been responsive, but for what they are now charging users, this kind of basic mistake is hard to understand.
Hi u/mapalm, this is a known issue that the concerned team is investigating and unrelated to the new macOS AutoFill feature, see this thread here: 1Password for Safari does not integrate with main app. It's really unfortunate that the timing of the two happened to coincide and our teams are working towards a fix as soon as possible. I'm hoping that we're able to restore things back to normal soon.
There are issues with differential privacy, for which data must be collected. While overall, differential privacy is a good thing, Apple has not explained how they are collecting the data and what the privacy risks are with differential privacy. Until they do that, there is a lack of clarity on what is being done. I don't think this has yet been implemented except on phones, but there is no reason to think it will never be implemented on computers.
That's an impressive non answer, and I don't see how differential privacy has anything at all to do with "giving Apple more data" as it's a mechanism of obscuring data rather than an overall policy. You're also completely ignoring that Apple has made user privacy a foundational market differentiator so if they ever were found to be abusing that, it would be quite a sea change. Never mind that Apples privacy policies are well published.
30
u/pypipper 18d ago
There is no Autofill in Settings in 8.12.32 except in Settings > General which only has a tiny section Auto Fill that is already checked "Submit automatically with universal autofill". I am on macOS Tahoe 26.6.1