Sources we use, in order

  1. The bitwarden/clients source code and its release notes.
  2. The Bitwarden Help Center and the published security audit reports.
  3. Package manager metadata: winget, Homebrew, Snapcraft, Flathub, the Arch User Repository, and distribution wikis.
  4. Competitor vendors' own documentation and pricing pages for comparison articles.
  5. Our own testing.

We do not use other review sites, affiliate round-ups or AI summaries as sources.

Testing

Install guides are executed start to finish on a Windows 11 PC (x64), an Apple Silicon Mac running the current macOS, and Ubuntu LTS. Fedora and Arch instructions are run in fresh virtual machines. Import guides are tested with a throwaway vault containing sample data in each source format. Screenshots are not taken of our own vaults; product images on the site come from the official Bitwarden brand kit.

Release data is automated

Version numbers, tags, file names, sizes and download counts are fetched from the GitHub API by a script before each build and checked again daily. The site currently reflects Bitwarden 2026.8.0, published August 20, 2026. A build fails if a page hard-codes a version string, so a stale number cannot be shipped by accident. The same data is exposed at /releases.json so you can check it yourself.

What "last verified" means

The date on each page is the last time a person re-read that page against the current release and the current vendor documentation, re-ran anything that could have changed, and corrected what had. It is not updated by the automated release refresh. If the date is more than a release or two behind, treat step-by-step UI instructions with some caution and tell us.

Comparisons

Comparison pages state when the competitor is the better choice, and every table row is something you can check on the vendors' sites. Prices are given as approximations with a reminder to confirm, because they change more often than we re-verify. We do not earn a commission from any product mentioned.

Advertising separation

Ads appear only in fixed, labelled slots. Advertisers do not see content before publication and cannot buy placement inside articles, rankings or recommendations. Details are on the advertising disclosure page.

Use of AI tools

Drafting and editing tools, including AI assistants, are used to speed up writing and to lint pages for metadata and broken links. Nothing is published without a person running the commands, checking the facts against the sources above and signing off. The team named on each page is responsible for its accuracy.

Corrections

Report errors through the contact page. Factual mistakes are fixed as soon as they are confirmed, usually within a few days, and the page's verified date is updated.