Hi! I'm Patrick, an Android developer here at 1Password. I'm happy to announce that we've made some changes to how 1Password interacts with Chrome on Android that should result in a much more reliable autofill experience.What does this update do?We’ve updated how 1Password integrates with Chrome and Brave, aligning with recent changes introduced by the Chromium team at Google. These changes aim to provide a more stable, native autofill experience, and will replace the older "compatibility mode" approach.If you’re using the latest versions of Chrome (v135+) or Brave (v1.79.119+) and 1Password (8.11.4), you’ll now get a more reliable autofill experience once your browser is properly set up to integrate with 1Password.Important: Please follow all the steps in our user guide carefully, even if you have previously enabled autofill on Android, as the necessary settings have changed.Why has autofill on Android been so unreliable lately? Google’s Chromium team rolled out changes over the past few months that are designed to improve users' autofill experience. Overall these were welcome improvements, but they introduced growing pains for third-party password managers:Chrome deprecated the “compatibility mode” approach to autofill that 1Password relied on, replacing it with a new, native autofill integration. (The same kind of integration 1Password already uses in other Android apps.)Additionally, Chrome now requires users to opt-in to a new setting to enable autofill support for third-party password managers, even if autofill was previously working in the browser.All of that is to say that there has been a dramatic change, for the better, to how autofill works under the hood in Chrome. But the new experience rolled out unevenly on the Android side, and it also required some additional changes to 1Password, leaving many users in an in-between state with broken autofill during the transition period.In our attempt to prepare users for these changes, we published a post last week that ended up causing additional confusion. We took this step to prevent users from experiencing a complete loss of autofill functionality following the release of today’s update (8.11.4). In retrospect, we probably should have released that messaging at the same time as the update.What about these browser feature flags?Some users may have previously used browser flags to force the deprecated compatibility mode to work. That approach may have provided some relief, but we advise against it as it will break autofill with 1Password going forward.If you’ve changed any flags, we strongly advise resetting them to their defaults:Open chrome://flags or brave://flags in your browserTap Reset all in the top-right cornerRestart your browser when promptedAutofill might still appear to work with some flags enabled, but we can't guarantee future compatibility. Now that the native integration is fully implemented in both Chrome and 1Password, we strongly encourage users to reset those flags to their default settings to get the most out of this update.Please use this thread to share your experience with this update and to ask any questions you may have about 1Password on Android.

Hi all,We've updated the instructions today (August 7, 2025) based on feedback we've received here and elsewhere to try and take into account folks setting up 1Password autofill on a new device and for folks who have already been using 1Password. We'll keep making updates if you have additional feedback!

Major autofill update on 1Password for Android