Google Password Manager vs Apple Passwords: Which Should You Use?

Google Password Manager and Apple Passwords are both free, built into an operating system you probably already use, and now handle passkeys as well as old-fashioned passwords. The short version: Apple Passwords, the standalone app that shipped with iOS 18, iPadOS 18, and macOS Sequoia, documents a built-in verification-code generator and Wi‑Fi password sharing that Google’s own support pages do not describe for Google Password Manager, while Google’s tool reaches further outside its home ecosystem, with documented support for Windows, ChromeOS, and Linux in addition to Android and Chrome. Neither is a full replacement for a dedicated password manager if you need shared vaults across teams or advanced vault auditing, but for most individuals the right pick comes down to which phone is in your pocket.

What is Google Password Manager?

Google Password Manager is the password and passkey storage built into the Chrome browser and Android. According to Google’s support documentation, when you sign in to Chrome or an Android device, Password Manager can save your passwords and passkeys to your Google Account, and those saved items then work for apps and sites on any device where you are signed in with that same account. You can view and manage everything on Android, inside Chrome, or at passwords.google.com from any browser.

On iPhone and iPad, Google’s documentation describes a narrower path: Password Manager works through the Chrome app, not a standalone Google app. Apple’s iOS Settings let you turn on Chrome’s “AutoFill Passwords and Passkeys” so saved logins fill in other apps, and on iOS 18.2 and later you can instead set Chrome as your default under “Passwords & Codes.”

What is Apple Passwords?

Apple Passwords is a dedicated app, separate from Settings, that launched with iOS 18, iPadOS 18, macOS Sequoia, and visionOS 2. Apple’s own support page describes it as a single place for account passwords and passkeys, Wi‑Fi passwords, and verification codes. Before this app existed, the same data lived inside iCloud Keychain and was managed through Settings; Apple simply gave it a front door.

The app can generate strong new passwords, flag weak or reused ones, and surface credentials that have shown up in known data leaks. It also supports Shared Groups, letting you share selected passwords and passkeys with family members or trusted contacts, and AirDrop sharing for sending a single password or passkey to a nearby device. On Windows, Apple’s support documentation covers access only through iCloud for Windows, which adds an iCloud Passwords extension to Chrome or Edge — narrower than the full native app on Apple’s own platforms.

Passkey support compared

Both companies have built passkeys — the WebAuthn-based, phishing-resistant sign-in method — directly into their password tools, but the details of how they are protected and recovered differ.

Google’s documentation on managing passkeys in Chrome states that passkeys saved to Google Password Manager are stored in your Google Account and backed up and synced to it, so signing in to Chrome or Android with the same account makes them available on another device. Unlocking a saved passkey requires either your device lock screen or a Google Password Manager PIN. Google is explicit that not every storage location behaves the same way: passkeys saved only to Windows Hello are not synced or backed up and cannot be recovered if that PC is lost or reinstalled, the same is true for passkeys kept only in a Chrome profile on a Mac, and passkeys stored on a physical security key are not backed up at all. Google also documents a QR-code flow for using a passkey saved on a phone to sign in on a nearby computer without moving the passkey itself.

Apple’s support documentation on passkeys describes each one as a unique cryptographic key pair per account: the public half sits with the website, the private half stays on the device and is required to sign in, and Apple states the server never receives the private key, which is why passkeys are described as highly phishing-resistant. On Apple devices, Face ID or Touch ID authorizes passkey use, and the passkeys themselves sync across a user’s devices through iCloud Keychain, which Apple’s documentation describes as end-to-end encrypted with keys Apple itself does not hold. Recovery works through iCloud Keychain escrow — Apple’s page says this still requires iCloud credentials, an SMS response, and the device passcode, with a 10-attempt limit — or through an account recovery contact. Apple’s own page also notes passkeys can work with “non-Apple devices within physical proximity,” though it does not spell out the mechanism in the page Pandromeda reviewed.

Two-factor authentication and verification codes

This is one of the clearest documented differences between the two tools. Apple’s support page for the Passwords app explicitly lists “verification codes” as one of the three things the app stores and surfaces alongside passwords and passkeys, describing it as setting up and storing automatic two-factor or multi-factor codes so you do not need a separate authenticator app or SMS messages.

Google’s support pages for Password Manager and for managing passkeys in Chrome do not describe an equivalent built-in time-based one-time-code (TOTP) generator inside Password Manager itself. Google does offer one-time codes elsewhere in its ecosystem — the separate Google Authenticator app generates and, per Google’s help documentation, can sync codes across devices when you sign in with the same Google Account — but that is a distinct product from Password Manager, not a feature documented as living inside it. If built-in authenticator codes matter to you, treat this as a documented gap for Google Password Manager rather than an assumption, and consider whether Google Authenticator or a third-party app fills it.

Autofill and everyday use

Both tools autofill saved credentials, but their reach outside their home browser differs. Google’s documentation describes Chrome’s autofill working on Windows, Mac, Linux, Chromebooks, Android, and iPhone/iPad when Chrome is set as the device’s password/autofill provider; Password Manager settings also let you turn off the “Offer to save passwords and passkeys” prompt, dismiss a site permanently, and review which sites you’ve blocked.

Apple’s documentation describes Password AutoFill working throughout iOS, iPadOS, macOS, and visionOS apps and in Safari, and on Mac it extends to supported third-party browsers through a Passwords extension. Apple’s page also covers sharing a Wi‑Fi password with a nearby device without ever revealing the password text itself — a convenience feature Google’s equivalent pages do not describe.

Cross-platform availability

If you live entirely inside one company’s ecosystem, this section barely matters. If you mix devices, it is the deciding factor.

Google’s own passkey-management documentation for Chrome lists desktop storage support on Windows 10 and later, Mac running macOS 12 or later, Chromebooks on ChromeOS 129 or later, and Linux, plus Android — making Chrome’s Password Manager the more broadly cross-platform of the two by Google’s own account. Apple’s documentation, by contrast, frames full native support around Apple’s own operating systems (iOS 18, iPadOS 18, macOS Sequoia, visionOS 2) and treats Windows as an add-on through iCloud for Windows rather than a first-class platform.

Feature comparison table

Security model and encryption

Apple’s documentation is specific that iCloud Keychain, which carries Apple Passwords data between devices, is end-to-end encrypted with keys Apple itself does not hold, and that an Apple Account using iCloud Keychain must have two-factor authentication turned on. Recovery is deliberately friction-filled: Apple’s page describes escrow-based recovery requiring iCloud credentials, an SMS code, and the device passcode, capped at 10 attempts, specifically to resist brute-force attempts.

Google’s support material for Password Manager and passkeys centers on account-level protection: items are tied to your Google Account sign-in, and a Google Password Manager PIN or your device’s lock screen governs access to saved passkeys. Google’s documentation is also candid about which storage locations are durable and which are not — passkeys left only on a security key, in Windows Hello, or in a Mac-only Chrome profile are explicitly flagged as unrecoverable if that hardware is lost.

Both companies also run ongoing checks rather than one-time scans. Google’s Password Checkup documentation describes continuous background monitoring for exposed credentials, with alerts you can toggle off (though some in-flight alerts may still arrive for up to 48 hours after you disable them), alongside on-demand checks for weak and reused passwords you can run any time from passwords.google.com or the Chrome menu. Apple’s support page describes its own flagging of weak, reused, and leaked passwords as an ongoing background function of the Passwords app rather than something you have to launch manually, which is a small but real difference in how proactive each tool is by default.

Which one should you use?

If every device in your life wears an Apple logo, Apple Passwords is simple to recommend: it is already installed, it documents a built-in verification-code generator so you can retire a separate authenticator app for many accounts, and it syncs through an encryption model Apple describes as end-to-end. If you split time between Windows, Android, ChromeOS, or Linux and just need something free that follows you everywhere, Google Password Manager’s documented reach across those platforms makes it the more practical default, with the caveat that you should pair it with a separate authenticator for TOTP codes since that is not a documented built-in feature.

Either way, understand the ceiling before you commit: both are built for individual or family use, not shared team vaults, granular permission tiers, or detailed audit logs. If that is what you actually need, it’s worth reading Pandromeda’s side-by-side of 1Password and Dashlane’s pricing and features or the three-way breakdown of Bitwarden, 1Password, and Proton Pass before paying for a dedicated manager you may not need.

Bottom line

Google Password Manager and Apple Passwords both now store passwords and passkeys for free, and both publish documentation on breach and weak-password alerts. The meaningful, officially documented differences are that Apple Passwords bundles verification codes and Wi‑Fi password sharing that Google’s own pages don’t describe for Password Manager, while Google documents broader native platform reach across Windows, ChromeOS, and Linux than Apple does outside its own hardware. Pick based on which ecosystem you actually live in, and don’t assume a feature exists just because the other company’s tool has it — check the company’s own support page first.

Written bySana Qureshi

Sana Qureshi runs the security and privacy desk. She reports on actively exploited vulnerabilities, vendor patches and data breaches, and covers the password managers, VPNs and authentication tools readers use to protect themselves. Her alerts cite vendor advisories, CISA and the CVE record directly.

More from Sana QureshiAll Security & Privacy coverage