Keeper Review 2026: Powerful Vault Control at a Usability Cost

Most consumer password managers can save and fill credentials. Keeper becomes more interesting when those credentials need to be organized carefully, shared repeatedly, or controlled after another person receives access. Structured records, detailed permissions, shared folders, recovery tools, and temporary sharing give its vault considerably more administrative depth than a simple personal password store.

We put that strength under pressure in this Keeper review by testing the Keeper Unlimited personal plan across core vault and browser tasks. Record creation, search, migration, permission handling, sharing, access removal, password generation, passkeys, and security warnings all completed successfully. A multi-step login required an additional interaction, but Keeper’s strongest results came from managing records and access rather than trying to automate every decision.

That depth is also Keeper’s main usability compromise. People with large vaults or credentials that move between several users can benefit from the extra controls. Someone who mainly wants passwords to save and fill with as little attention as possible may find much of that capability unnecessary.

What Is Keeper?

Keeper is a password manager built around an encrypted vault for storing logins, passkeys, payment information, identities, secure notes, and other sensitive records. Its desktop and mobile apps, browser extensions, and Web Vault keep the same credential collection available across supported devices.

The service is operated by Keeper Security, Inc. Keeper’s consumer password manager is designed around structured records, detailed sharing controls, permission management, and broader vault administration rather than limiting the experience to basic password storage and autofill.

That gives Keeper a more control-focused identity than many consumer password managers. Users can organize records, manage shared access, apply permissions, recover or review changes, and work with newer credential types such as passkeys. The result is a stronger fit for people managing larger or shared vaults than for users who want the simplest possible save-and-fill experience.

Keeper Key Facts

How We Tested Keeper

Keeper’s main advantage is control over records and access, so our methodology put more weight on what happened after information entered the vault, not simply whether a password could be saved. We tested the Keeper Unlimited personal plan with controlled accounts and synthetic credentials on Windows and through browser-based workflows. Other platforms were researched through Keeper’s current documentation rather than presented as directly tested.

Vault testing included structured records, custom fields, editing, synchronization, search, organization, migration, export, and deleted-item handling. A second controlled account was particularly important for Keeper because it let us test sharing, recipient access, permission behavior, synchronization, and later revocation instead of judging the sharing system from its settings alone.

We also introduced a duplicate during migration to see whether Keeper would resolve it automatically. For browser use, we tested credential capture and autofill, including a multi-step login, then followed generated passwords from creation through insertion and saving. Passkey storage and reuse were tested separately, while weak, reused, and exposed synthetic credentials were used to trigger password-health and breach warnings.

Keeper’s encryption, provider-access boundaries, authentication, recovery design, certifications, vulnerability history, and available independent evidence were assessed outside the hands-on interface tests. Those sources are necessary for evaluating security properties that cannot be demonstrated simply by operating the vault.

Usability was judged partly by how much control Keeper made us manage. We considered setup, record handling, sharing, navigation, browser use, and situations where a task succeeded but still required an extra decision or interaction. That distinction was especially relevant to the multi-step login test.

Our conclusions apply to Keeper Unlimited and the controlled Windows/browser workflows used during testing. They should not be treated as evidence for every website, platform, passkey scenario, or business-administration configuration.

Keeper Vault Control Overview

Keeper is strongest when the vault needs to do more than simply store passwords. Its record structure, folders, sharing permissions, recovery tools, and access controls give users considerable room to manage complex collections. In our Keeper Unlimited testing, record editing, search, migration, synchronization, and sharing all worked reliably, with the main friction coming from the amount of control exposed to the user.

Item Creation, Editing and Item Types

Keeper supports structured records for logins, secure notes, payment information, identities, and other sensitive data, while custom fields let users extend individual records when the default layout is not enough.

That flexibility held up well in our controlled workflow. We created records, edited stored information, added custom fields, synchronized the vault, and restored deleted content without losing the data we expected to remain intact.

The advantage becomes clearer as a vault grows. Keeper gives users more ways to shape individual records than a basic username-and-password manager, although that same depth can feel excessive when the only goal is saving a few conventional logins.

Organization, Search and Vault Structure

Keeper uses folders, favorites, search, and shared folders to keep larger collections manageable. Personal records can be arranged without changing their contents, while shared folders provide a separate structure for information that needs to remain available to other Keeper users.

Search performed reliably in our test vault. Every known record was found through the searches we used, and moving records between locations did not alter or remove their stored information.

Record history and deleted-item recovery add another layer of control when something is changed or removed accidentally. These tools make Keeper particularly suited to larger vaults, although users coming from a simpler password manager may need more time to understand where the organizational controls fit together.

Import, Export and Migration

Keeper provides import paths from browsers and other password managers, reducing the need to rebuild a vault manually. In our controlled migration workflow, the essential login information transferred correctly in both directions.

We deliberately introduced a duplicate to see whether the process would resolve it automatically. The transfer still succeeded, but the duplicate required manual review afterward, so migration should not be treated as a completely automated cleanup process.

The result also needs a sensible boundary. Our successful transfer confirms the login data we tested, not every possible attachment, passkey, record history entry, custom field, or sharing configuration that could exist in a larger vault.

Sharing, Permissions and Administration

Keeper’s sharing model is one of the clearest reasons to choose it. Records and shared folders can be given to other Keeper users with permissions that control what recipients are allowed to view, edit, or share rather than treating every shared credential the same way.

We tested this with a second controlled account. Recipient access worked correctly, synchronization behaved as expected, the tested permissions applied properly, and we were able to remove access afterward without disrupting the underlying record.

That makes Keeper more useful for ongoing shared access than simply sending a password outside the vault. The additional permission choices create more setup work, but they also let the owner retain considerably more control over what happens after information is shared.

Keeper Vault Control Test Results

We tested Keeper Unlimited with two controlled accounts, ten synthetic login records, and several non-sensitive vault items. The checks covered item creation and editing, search and organization, import and export, and sharing with later access removal.

Keeper passed all four Vault Management checks. Record editing, organization, sharing, and permission handling were particularly dependable, while the deliberate duplicate created during migration was the main point requiring manual review.

These findings apply to the Keeper Unlimited plan, controlled accounts, synthetic records, and desktop/browser environment used during testing. Different item types, import formats, browsers, sharing configurations, or larger deployments may produce different results.

Standout Vault Control Features

Keeper’s strongest vault controls extend beyond organization itself. Record history, deleted-item recovery, shared-folder permissions, and revocation help preserve control after information has been changed, deleted, or made available to someone else.

One-Time Share

One-Time Share covers situations where permanent sharing would be excessive. Keeper can generate an expiring link to a record for someone who does not need ongoing vault access or a normal Keeper account, with the owner retaining the ability to revoke that access.

That makes it useful for temporary handoffs such as giving a contractor, guest, or family member access for a limited period. Regular shared records remain more appropriate when another Keeper user needs continuing access, while One-Time Share is better suited to short-lived exceptions.

Keeper Functionality Overview

Keeper is capable across the main credential tasks, although it does not always hide the mechanics from the user. KeeperFill handled the browser logins we tested, generated credentials were stored correctly, passkeys could be reused, and account-health tools surfaced the expected warnings. The main interruption came during a multi-step login that needed an additional action before completion.

That fits Keeper’s broader design. Its functionality favors control and explicit interaction over trying to make every process invisible, which works well for users comfortable managing a more involved password manager but feels less effortless than the simplest alternatives.

Autofill and Login Capture

KeeperFill handles login detection, credential filling, and saving new account information during everyday browsing. In our controlled tests, the forms we used filled correctly and the saved credentials remained available for later sign-ins.

The clearest friction appeared on a multi-step login. Keeper still completed the sign-in, but an additional interaction was required before the workflow finished. That is a good example of the difference between a feature working correctly and feeling fully automatic.

Keeper also supports more complex form structures, but our testing covered a controlled set of websites rather than enough cases to claim universal compatibility. Browser behavior can still vary depending on how individual login pages are built.

Password Generator and Credential Creation

Keeper’s password generator works directly inside signup and password-change workflows, with support for configurable random passwords and passphrases. The practical value comes from how well generation connects to insertion and saving rather than from the number of available settings alone.

We tested two account workflows and Keeper inserted the generated password correctly in both cases, then saved it to the intended record. That completed the full creation path without forcing us to copy the credential manually between the generator and vault.

Sites with unusual password requirements can still reject a generated result, so the important fallback is being able to create a replacement quickly and save the new credential correctly. In our tested workflows, that process remained straightforward.

Passkey Support and Modern Login Tools

Keeper can store passkeys in the vault and use them for supported passwordless sign-ins, which allows these credentials to move with the Keeper account rather than remaining tied only to a device’s native credential store.

Our test passkey was stored successfully and reused for sign-in in the browser workflow we examined. That confirms the practical save-and-use path rather than simply verifying that passkey support appears in the interface.

Portability needs a narrower conclusion. We did not establish that Keeper passkeys can be transferred cleanly to another password manager or preserved through every migration and recovery scenario. Keeper’s passkey support is therefore convincing for everyday use, but provider-to-provider portability remains less certain.

Password Health and Breach Monitoring

Keeper separates password quality from exposure monitoring. Security Audit looks for weak, reused, and other problematic credentials already stored in the vault, while BreachWatch is designed to identify credentials associated with known exposure.

Using controlled test credentials, we triggered the expected warnings and confirmed that the findings linked back to the relevant stored items. That makes the alerts useful because the user can identify which record needs attention rather than seeing only a general warning.

Breach monitoring still has limits. Availability can depend on the subscription setup, and no service can guarantee complete or immediate detection of every newly exposed credential. These tools are best treated as an additional warning layer rather than a complete record of breach activity.

Keeper Functionality Test Results

We tested Keeper Unlimited with controlled accounts and non-sensitive credentials across several everyday authentication workflows. The checks covered autofill and login capture, password generation and saving, passkey use, and password-health and breach alerts.

Keeper passed all four Functionality checks. Password generation, passkey use, and credential warnings behaved reliably, while the extra interaction required during the multi-step login was the clearest usability friction we encountered.

These findings apply to the Keeper Unlimited plan, controlled accounts, websites, and browser environment used during testing. They do not establish compatibility with every website or application, complete breach-database coverage, or universal passkey support and portability.

Keeper Security Overview

Keeper has a strong security foundation built around client-side encryption, layered account protection, and structured recovery. Its technical documentation explains the core architecture in useful detail, while MFA, device controls, and emergency access provide additional safeguards around the encrypted vault. The main weakness is independent transparency, since Keeper exposes less public code and fewer broadly accessible audit reports than the most transparent alternatives.

Encryption and Zero-Knowledge Architecture

Keeper encrypts vault information on the user’s device before synchronization. Its documented architecture uses AES-256 encryption with separately generated keys for individual records, while the master password contributes to key derivation rather than being stored as a readable vault key on Keeper’s servers.

Keeper also documents PBKDF2-based key derivation for master-password accounts. The purpose is to increase the computational cost of offline guessing if encrypted account material is obtained, although the protection still depends heavily on the strength and uniqueness of the master password.

Keeper describes this architecture as zero knowledge because protected vault contents are encrypted before reaching its infrastructure and the provider is not intended to hold the keys needed to read normal records.

That claim has a defined boundary. Account registration details, billing information, device data, support interactions, and some service metadata can exist outside the encrypted vault. Zero knowledge therefore describes Keeper’s treatment of protected vault content rather than an absence of all provider-side data.

Account Authentication and Device Trust

Keeper adds several controls beyond the master password, including authenticator-based two-factor authentication, biometric unlocking on compatible devices, security-key and passkey-related authentication in supported environments, and tools for managing trusted devices and active access.

These protections solve different problems. MFA reduces the usefulness of a stolen master password during a new account login, while biometric unlocking can make repeated vault access more convenient on a trusted device without removing the underlying account protections.

Device and session management add another defensive layer. Users can review connected access and remove devices that should no longer remain trusted, which becomes particularly important after losing a computer, changing phones, or sharing a device temporarily.

Feature availability still depends on the platform and browser. Some passkey-based or biometric authentication workflows have narrower compatibility than ordinary master-password access, so users should confirm support on the devices they actually rely on rather than assuming every Keeper client provides identical authentication options.

Recovery Model and Emergency Access Security

Keeper’s recovery system is designed to restore vault access without giving the provider a simple way to reveal a forgotten master password. Its current recovery model uses a 24-word recovery phrase that protects the key material needed to regain access, alongside additional verification steps such as email confirmation and configured two-factor authentication.

That provides a more forgiving recovery path than a design where losing the master password automatically means losing the vault. It still requires users to protect the recovery material carefully, because losing both normal access and the recovery route can have serious consequences.

Emergency Access covers a different situation. Keeper lets users designate trusted contacts and define a waiting period before access becomes available, giving the account owner time to reject an unexpected request.

That makes the feature useful for incapacity, estate planning, or other emergencies without requiring permanent shared access. The trusted contact and waiting period become part of the security model, however, so they should be configured as carefully as any other recovery mechanism.

Audits, Breach History and Provider Trust

Keeper provides more security evidence than architecture claims alone. It publishes technical documentation, operates vulnerability-disclosure and bug-bounty programs, references third-party penetration testing, and maintains certifications covering different parts of its security and organizational environment.

Those signals support confidence, but they should not be interpreted as proof that every consumer client, recovery mechanism, sharing workflow, metadata boundary, and backend component has undergone a fully public independent audit.

Keeper’s consumer applications are also not broadly open source. That does not make the product insecure, but it gives outside researchers less opportunity for continuous public code inspection than an open-source password manager provides.

Keeper has also dealt with documented vulnerabilities in the past, including a serious browser-extension issue disclosed in 2017 and later security disputes involving older desktop and extension behavior. Those historical issues were addressed and do not demonstrate that current Keeper vaults are compromised.

The more useful trust question is how much evidence exists around the current architecture and how security issues are handled when they are discovered. Keeper performs well on documented design and vulnerability management, but its public independent evidence remains less comprehensive than the strongest transparency-focused competitors.

Keeper Usability Overview

Keeper is capable in everyday use, but its depth comes with a steeper learning curve. During our hands-on testing, routine vault and browser tasks were dependable, while the number of record options, sharing permissions, security controls, and occasional extra steps made the experience less immediate than simpler password managers. The usability trade-off is therefore not reliability, but how much the user needs to understand and manage.

Setup and First-Time Use

Keeper’s initial setup is manageable, but new users encounter several important choices early. Account creation, the master password, recovery setup, and browser integration all need attention before the service settles into a normal daily workflow.

Recovery deserves more attention than a typical onboarding prompt because Keeper relies on recovery material that should be stored carefully. Migration can speed up setup for an existing password collection, although our test showed why imported data still deserves review. The essential information transferred correctly, but the deliberate duplicate needed manual attention afterward.

None of those steps made setup unusually difficult. Keeper simply exposes more of the decisions involved in configuring and protecting the vault instead of hiding them behind highly simplified defaults.

App, Vault and Navigation Design

Keeper places a large amount of functionality inside the vault. Records, folders, search, password generation, security information, sharing controls, and record-management options remain accessible without requiring separate tools, which is useful once the structure becomes familiar.

The density becomes more noticeable when moving beyond basic password storage. Structured records, custom fields, shared folders, permissions, recovery tools, and security settings create more controls to understand than a user with a small personal vault may ever need.

Our search and organization tests did not reveal problems locating the records we deliberately created. Every known record was found and could be moved without changing its stored information. That demonstrates reliable navigation through the test vault, but it does not make the interface itself minimal.

Keeper therefore rewards familiarity. Users managing larger or shared collections are more likely to benefit from the available controls, while someone who mainly wants to save and autofill logins may find the interface busier than necessary.

Browser Extension and Daily Login Flow

KeeperFill carries most of the daily browser workload, keeping saved credentials, password generation, login capture, and autofill close to the website being used. Ordinary login workflows in our tests worked without requiring us to return to the full vault.

The clearest friction appeared during the multi-step login test. Keeper completed the sign-in successfully, but an additional interaction was required before the workflow finished.

That distinction helps explain Keeper’s usability score. The feature worked, but successful completion did not always mean the process was completely hands-off. During repeated use, small interventions such as responding to a prompt or completing an extra step can make a capable password manager feel more involved than a simpler alternative.

Desktop, Mobile and Cross-Platform Experience

Keeper provides desktop applications, browser extensions, a Web Vault, and apps for other supported platforms, with synchronization keeping the same underlying account and vault available between them.

Our direct hands-on work for this review focused on Windows and browser-based workflows. Changes to the records we tested remained available through the environment we used, but we did not treat platform behavior outside that scope as first-hand evidence.

Keeper’s documentation also shows that some autofill, passkey, biometric, and authentication capabilities depend on the operating system or browser. Users who rely heavily on a particular platform should therefore confirm that the specific advanced workflows they need are supported there rather than assuming identical behavior everywhere.

Customer Support and Ease of Use

Keeper exposes more record, permission, recovery, and security controls than many personal password managers, so its documentation has more work to do. The help center covers setup, migration, browser integration, recovery, passkeys, and sharing, giving users somewhere to verify how those controls are supposed to behave once the interface becomes more involved.

We contacted Keeper support about recovering a vault after forgetting the master password. The reply explained the recovery process directly and gave us the information needed without sending us through unrelated troubleshooting or several rounds of clarification.

That is a good fit for Keeper. A product with this many controls benefits from support that can narrow an account problem down to the relevant recovery steps instead of adding more complexity.

Keeper Extra Tools and Add-ons

Keeper keeps most of its focus on password management, but it also offers optional services for encrypted file storage and more hands-on setup assistance. BreachWatch fits better with credential monitoring in the Functionality section, while Secure File Storage and Concierge Service are separate add-ons that can increase the total cost depending on what the user actually needs.

Secure File Storage

Keeper Secure File Storage is designed for sensitive files that belong alongside vault records rather than as a replacement for a full cloud-storage platform. It can hold documents, images, videos, and other files, with Keeper stating that files are encrypted locally before upload under the same zero-knowledge model used for vault data.

For personal users, additional storage is available separately, while the Family plan currently includes 10 GB. The strongest use case is keeping items such as identity documents, financial records, or other private files close to the credentials or records they relate to.

Sharing can also use Keeper’s existing access controls and One-Time Share, which keeps file access inside the same permission model as other vault content. The limitation is scope. This is protected document storage, not a substitute for a broader cloud service built around collaboration, productivity, and large-scale file synchronization.

Concierge Service

Concierge Service is a separate add-on for users who want more direct help setting up and using Keeper. Keeper describes it as including one-on-one training, 24/7 support, installation guidance, product assistance, and general cybersecurity guidance.

That can be useful for families, less technical users, or anyone moving a large vault who would rather have guided help than work through documentation alone. Its value is lower for experienced users because Keeper already provides standard support and extensive help resources with its paid plans.

Concierge therefore improves the support experience rather than expanding the password manager itself. It is best treated as a convenience service for users who expect to need ongoing assistance.

Keeper Pricing, Plans and Refunds

Keeper offers a permanent Free tier alongside Keeper Unlimited for individuals and Keeper Family for households. The biggest difference is not the underlying password-management engine. Paid access removes the severe device and record limits of Free and adds synchronization, sharing, recovery, browser access, and other tools needed for normal cross-device use.

That makes the plan decision fairly straightforward. Free is suitable only for very limited use, Unlimited is the practical choice for one person, and Family expands the paid experience to several private vaults with stronger household sharing.

Keeper Free

Keeper Free provides permanent access without a subscription, but its restrictions make it difficult to recommend as a primary password manager. The account is limited to 10 records on one mobile device, with no normal synchronization, browser-extension access, sharing, backup, restore, or export.

Current limits also restrict TOTP storage and file uploads, leaving Free closer to a small local vault than a complete cross-device password manager. That is a major difference from free plans that allow hundreds of credentials to follow the user between desktop and mobile.

For someone managing only a handful of records, Free can still function. Most users with dozens or hundreds of accounts will outgrow it quickly, making it more useful as a fallback tier than as Keeper’s main long-term offering.

Keeper Unlimited

Keeper Unlimited is the personal plan we tested for this review and the most sensible option for one user. It removes the 10-record and single-device restrictions and adds unlimited synchronization, browser and Web Vault access, secure sharing, cloud backup, Emergency Access, and direct customer support.

That upgrade changes Keeper from a restricted mobile vault into the full cross-device password manager. It also unlocks the vault-management and sharing capabilities that form a large part of Keeper’s appeal.

The base subscription is not completely all-inclusive. Services such as BreachWatch and additional Secure File Storage can increase the total cost, so buyers should distinguish the core Unlimited subscription from optional add-ons when comparing prices.

For one person who wants Keeper’s complete password-management experience, Unlimited is the most proportionate choice.

Keeper Family

Keeper Family extends the paid service to five separate private vaults rather than putting several people inside one shared account. Each member keeps their own credentials, while selected records and folders can be shared with the permissions Keeper provides.

That structure fits households particularly well because private credentials remain private by default. Shared logins can then be made available only where needed instead of requiring everyone to use the same master password or common vault.

The plan also includes 10 GB of Secure File Storage, which adds more value for families keeping sensitive documents alongside shared records. One person gains little from the additional member capacity, however, so Unlimited remains the better fit for solo use.

Keeper Billing and Renewal Terms

Keeper subscriptions are generally billed annually in advance and renew automatically unless recurring billing is disabled. Introductory discounts or promotional first-year prices should not be treated as guaranteed long-term pricing because renewal rates can change.

Cancelling auto-renewal prevents the next subscription charge but does not normally convert the remaining paid period into a refund. Users therefore retain access through the current term and should make renewal decisions before the next billing date.

Keeper Money-Back Guarantee and Free Trial

Keeper currently provides a 30-day trial of Keeper Unlimited without requiring a credit card, giving users a practical way to test the full individual plan before paying. If the account is not upgraded when the trial ends, it falls back to the much more restricted Keeper Free tier.

The important distinction is refunds. Keeper’s current terms generally describe subscription fees as nonrefundable, so the service should not be presented as having a conventional 30-day money-back guarantee after purchase.

Purchases through Apple, Google, or another third party may follow that store’s own billing and refund rules. The no-card trial is therefore the safer evaluation route for users who want to test Keeper before committing to an annual subscription.

Keeper Comparison With Alternatives

The main question with Keeper is whether you actually need its level of vault and permission control. Bitwarden is more appealing when open-source transparency, configurability, and value take priority, while Proton Pass suits users who would rather combine password management with stronger privacy features and a lighter organizational model. Keeper earns the extra complexity when records and shared access need closer management.

Compared with Bitwarden, Keeper provides more detailed control over the contents of the vault, while Bitwarden gives users more control over the password manager itself. Keeper’s structured records, folders, sharing permissions, and access controls are better suited to credentials that need active administration. Bitwarden counters with open-source development, a stronger free tier, deeper configuration options, and optional self-hosting.

Against Proton Pass, the difference is advanced vault management versus privacy-focused personal use. Keeper provides substantially more depth through structured records, shared folders, permission controls, revocation, and One-Time Share. Proton Pass keeps the experience lighter while adding open-source applications, email aliases, strong security architecture, and privacy tools that are more relevant to users who do not need Keeper’s administrative depth.

Choose Keeper Unlimited if detailed vault organization, permissions, and controlled sharing are the priorities. Choose Bitwarden Premium if open-source transparency, configurability, and value matter more. Choose Proton Pass Plus if privacy, aliases, and a simpler personal vault are more useful than Keeper’s deeper access controls.

Final Verdict: Keeper Gets Vault Control Right

Keeper stands apart when information inside the vault needs to remain closely controlled after it has been created or shared. That became the clearest theme of our Keeper review, with structured records, custom fields, shared folders, granular permissions, revocation, recovery, and One-Time Share providing considerably more depth than basic save-and-fill tools.

Our Keeper Unlimited testing reinforced that strength. Record management, search, migration, sharing, permission handling, password generation, passkeys, and security warnings all completed successfully, with sharing and access control providing some of the clearest reasons to choose the service.

The same depth creates Keeper’s main drawback. More settings, permission choices, and interaction make it less effortless than simpler alternatives, and our multi-step login also required an additional action. Bitwarden is more compelling for open-source transparency and value, while Proton Pass favors privacy and a lighter vault experience.

Keeper Unlimited is best suited to a single user who needs detailed vault organization and strong control over shared access. People whose needs stop at storing and autofilling ordinary passwords are less likely to benefit from the additional complexity.

Keeper FAQs