Google Password Manager Duplicate Passwords Explained

A report says Google Password Manager now lets users choose which password or passkey to keep when an imported credential conflicts with one already saved, in a Google Play services update reported Tuesday by heise online.

That detail sits on top of a separate, already-confirmed feature: Android's Credential Transfer API, which Google introduced in September to move passwords and passkeys between password managers without downloading a file. The API works with Google Password Manager, 1Password, Bitwarden Password Manager, and Dashlane on Android 8.0 Oreo or later, according to Google and Ars Technica.

Google says the transfer experience is already available for those four apps. The duplicate-picker claim comes from a single outlet, so the mechanics, the rollout scope, and what happens to a credential a user doesn't select remain open questions.

How to manage duplicate logins in Google Password Manager

Heise online's report describes a new option appearing during import: when a password or passkey being brought in conflicts with an entry Google Password Manager already has saved, the report says users can choose which credential to keep (heise online).

That's the extent of what's been reported. The supplied reporting does not say whether the choice happens one credential at a time or in a batch, whether Google Password Manager duplicate passkeys get shown the same way as duplicate passwords in that prompt, or whether the entry a user doesn't select gets deleted, kept dormant, or flagged for later cleanup.

The Google and Ars Technica materials reviewed for this article do not document this prompt, and the supplied reporting contains no second hands-on test of how the screen looks or behaves. The report establishes the claim, not the feature's full behavior or availability. Anyone curious should check whether the option has shown up on their own device after the Google Play services rollout heise describes, rather than wait for a specific version number that hasn't been reported anywhere.

Google Password Manager has surfaced duplicate entries before, just not this way. A 2022 Chrome update began automatically grouping multiple saved accounts for the same site so they'd be easier to review together (Google). That's historical context, not evidence for how the new conflict picker behaves. Grouping entries for review is a different workflow than being asked to pick a winner between two conflicting logins during an import, which is what heise's report describes.

Existing cleanup tools work differently too. The same 2022 update added Password Checkup to flag weak and reused passwords on Android, on top of its earlier compromised-password warnings, and paired that with an automated password-change feature so flagged logins could be fixed without leaving the app (Google). Those tools clean up credentials already sitting in the saved list. The picker heise describes addresses something narrower: a conflict that surfaces the moment a new credential is imported, not an ongoing audit of what's already stored.

The same Google Play services update bundles in bug fixes tied to security and emergency services, along with changes to Wallet loyalty cards and Google Wallet (heise online). In Google's own release language, the update is meant to improve battery life, device connectivity, performance, privacy, security, stability, and updatability, according to heise's report. None of that is specific to the duplicate-credential picker, but it places the change inside a broader Google Play services push covering several unrelated fixes at once.

Who can import passwords and passkeys to Google Password Manager now

The Credential Transfer API is easier to pin down than the duplicate picker. Google announced it in September as a way to move passwords and passkeys between managers in a few taps, with no file downloads required (Google).

To use it, both the password manager being left and the one being moved to need to already be installed, with credentials synced in the source app (Ars Technica). Starting a transfer triggers an identity check on the device, and Android asks for confirmation inside the destination app before anything moves. Ars Technica reports the process moves both passwords and passkeys without creating any risky text files along the way, and notes the whole thing relies on the Credential Transfer API, which each of the four supported apps has already implemented.

Four managers currently support that API: Google Password Manager, 1Password, Bitwarden Password Manager, and Dashlane (Google; Ars Technica). Google says it expects more providers to add support over time but hasn't given a timeline. Google's announcement confirms only those four participating apps, so support for Apple's Passwords app, Proton Pass, NordPass, or similar tools is unconfirmed, not ruled out.

The feature doesn't require an Android OS update since it arrives through Google Play services, and it works on Android 8.0 Oreo or higher (Ars Technica). Ars Technica separately notes that Google Play services support reaches back further, to Android 7.0 Nougat, though that's a fact about Google Play services generally rather than a stated requirement for this specific transfer feature. The documented minimum for Credential Transfer stays at Android 8.0.

Before trying the transfer tool, the requirements worth checking are narrow:

• Android 8.0 Oreo or later, Google's stated minimum for the Credential Transfer API.
• Both the source and destination apps among the four currently supported managers.
• Credentials already synced in the source app, since the API requires both apps installed with syncing in place.
• No separate OS update needed, since the feature arrives through Google Play services rather than a system update.

What this does not confirm

Nothing in the Google or Ars Technica sourcing addresses the duplicate-credential picker at all. It comes exclusively from heise's report on the Google Play services rollout, which leaves several practical questions open:

• Whether the choice happens one credential at a time or across a batch of conflicting entries during import.
• Whether passkeys are presented in the same conflict screen as passwords, or handled separately.
• What happens to the credential not selected: deleted outright, kept dormant, or flagged for later cleanup.
• Whether the option is tied to a specific Google Play services version, since heise doesn't report one.

Readers should not assume the picker is available or know what happens to an unselected credential until Google documents the feature or independent testing confirms the flow. The same caution applies to assuming the transfer tool itself extends beyond the four named managers. Apple's Passwords app, Proton Pass, and NordPass are absent from Google's announcement, and absence from that list isn't the same as confirmed incompatibility.

What's confirmed, what's still unverified

Android's file-free Credential Transfer API is real, documented, and available now for Google Password Manager, 1Password, Bitwarden Password Manager, and Dashlane on Android 8.0 or higher, with identity verification built into the move (Google; Ars Technica).

The duplicate-credential picker rests on one report of a Google Play services rollout, with no Google documentation of the interface, scope, or outcome for unselected credentials (heise online). Check the transfer tool now if switching between the supported managers; hold off on counting on the conflict picker until more sources confirm how it actually works.