1Password offers a lot more functionality than, say, Apple Passwords.

Apple Passwords will store a user/pass combo for a site. That's it, feature list over.

1Password will let you configure how those things autofill, it provides an `op` CLI that you can use with service account tokens, you can store stuff like photos of your passports and licences, it understands 'Sign in with GitHub', it has per-user access per vault for shared accounts, you can add any number of extra fields to each entry, it integrates directly with Claude, it monitors your passwords against Haveibeenpwned, it'll tell you where you could be using 2FA and aren't … and the list goes on.

Google Password Manager, the one built into Chrome, doesn't even do end-to-end encryption by default. You have to go into the settings and opt in to encrypt your password data before it gets sent to Google. And since it's closed source, you also just have to take Google's word for it. You'd be better off using a standalone password manager that is a) secure by default b) auditable.

Browser password apps are not suited to just store secrets not related to logins.

They are personal, meaning no user management or sharing of secrets.

They do not sync across devices -- or when they do, with restrictions like same browser/same OS only.

They cannot be used for e.g. commit signing or SSH login.

To not be tied to a single machine or OS