1Password is a password manager that stores logins, passkeys, secure notes, payment details, documents, and other private records in encrypted vaults. Instead of remembering a different password for every account, the user remembers one account password and approves the device that fills or displays the saved item. Browser and mobile integrations can match a saved login to its site without copying credentials through an ordinary note or spreadsheet.
Vaults separate records
Items live in vaults rather than one undivided list. A personal vault can hold private logins, while a shared vault can expose selected records to family or team members. Moving an item into a shared vault changes who can reach it; adding another copy can leave two records that later diverge.
Collections can group several vaults for viewing without changing their ownership. Tags classify items inside those vaults. These two tools solve different problems, so removing a tag does not remove access, and removing a vault from a collection does not delete its contents.
The browser extension can save a new login and fill the matching website. A convincing look-alike domain should not receive the same item automatically. Checking the shown website before manual filling remains important when a page arrives through an unexpected message.
Two secrets open it
The account password combines with a long Secret Key. The Secret Key is created for the account, stored on devices already linked to it, and printed in the Emergency Kit. A first sign-in on a new device needs both pieces. This design prevents the service alone from decrypting the vault, but it also means an individual user cannot ask support to reveal a lost Secret Key.
The Emergency Kit belongs somewhere separate from the computer and phone used every day. Saving its only copy inside the same locked vault creates a circular recovery problem. A printed copy or another protected offline location remains reachable after a lost device.
Family organizers and business administrators can begin account recovery under their respective account rules. Individual accounts need their own recovery preparation. A recovery code, when configured, also needs protection because possession of it and access to the account email can start a reset.
Passkeys change sign-in
A saved passkey signs in through a cryptographic credential tied to the real service rather than a typed password. 1Password can present the matching passkey on supported sites and synchronize it through the account. Existing password-only sites still need their saved login, and an account can contain both kinds of credential during a transition.
Replacing a site password with a passkey should be tested before deleting the old login. Some services keep a password as a fallback or require it for account changes. The website, not the password manager, decides those recovery rules.
Exports lose encryption
1Password can export data for backup or migration. Its structured 1PUX export preserves more vault information than CSV, while CSV is easier for other programs to read but carries fewer field types. Neither export remains protected by the vault encryption after creation.
Anyone who obtains the export file can read its contents. Creating it in a synchronized desktop folder may upload the unencrypted copy to another service. It should move directly to the intended protected destination and be deleted from the working folder, recycle bin, and temporary transfer location when the migration is confirmed.
Travel removes vaults
Travel Mode keeps only vaults marked safe for travel on signed-in devices. Other vaults disappear from those devices while the mode is active and return after it is turned off. This can reduce what is physically present during a border crossing or other trip.
1Password apps need an Internet connection to receive the change. Turning Travel Mode on immediately before losing connectivity may leave the unwanted vaults on a device that never synchronized. Each device should be opened online and checked before departure. The same step applies after the trip when restoring the removed vaults.
Sharing needs review
A shared item remains accessible according to its vault permissions, even if one recipient no longer needs it. Removing a person from a family or team affects future access but cannot retract a secret already copied. Passwords and recovery codes exposed beyond their intended group should be rotated.
1Password reduces the number of secrets a person must memorize, yet recovery still depends on a few irreplaceable records. Keeping the Emergency Kit current, reviewing shared vault membership, and testing a second trusted device are practical checks that matter before the primary device fails.
