What the author actually reports
Her complaints are specific:
- Cross-browser friction. She says she kept having to work out which browser held which password. She also hit trouble signing in on a friend's laptop.
- Flat organization. She describes hundreds of logins in one long list, with no folders or tags. That made it hard to separate personal, shared and private accounts.
- Scattered secrets. She wanted to keep Wi-Fi passwords, software licenses, recovery codes and sensitive notes in one place. Instead they ended up spread across email, notes apps and the browser.
- A quick move. She says that moving to Bitwarden took under half an hour. She then had the same vault on Chrome, Safari, a Mac, a work PC, an iPhone and a Galaxy phone.
These are anecdotes. The piece gives no test method, software versions or dates, so don't read it as proof that every browser manager fails in the same way.
Where the "locked in" framing needs nuance
The article says browser managers tie you to one browser or ecosystem. That is true of some setups and too broad for others.
- Apple's iCloud for Windows documentation says that once iCloud Passwords is set up, you can reach iCloud Keychain passwords in Chrome, Edge or Firefox on Windows. That's a concrete counterexample to "one browser only." Whether it feels smooth in daily use is a separate question.
- Google's help page covers importing and exporting passwords and passkeys, so "passwords only" is too sweeping for Chrome's manager. Google's documented import route is CSV, and its export route is described as passwords. Don't assume a CSV export carries passkeys across.
- Bitwarden's own help says that Chromium-based browsers work with the same import steps. That list includes Chrome, Microsoft Edge, Opera, Brave and Vivaldi. If your passwords live in Edge, the process is the same.
The fairer conclusion is that a browser manager can be enough if your devices and browsers match its ecosystem. It starts to strain when you mix platforms, want shared or organized vaults, or want one place for non-login secrets.
How the Chrome-to-Bitwarden move works
Google's documentation and Bitwarden's help pages agree on the basic flow.
- Export from Chrome on a computer. Open Chrome's menu, then Passwords and autofill, then Google Password Manager, then Settings. Scroll to "Export passwords" and select Download file. Google's page describes this path.
- Save it as CSV. Bitwarden's guidance says to confirm the format is comma-separated values.
- Import into Bitwarden. Bitwarden says data can be imported from the web app, browser extension, desktop app and CLI, and is encrypted locally before it goes to the server. In the web vault, go to Tools, then Import data. Choose the Chrome (csv) format, pick the file and run the import. Bitwarden also offers a direct-from-browser option in its desktop app.
- Check the result. Open a handful of important logins, such as email, banking and work accounts.
- Delete the CSV. Bitwarden advises deleting the source file after a successful import, which protects you if your computer is compromised. Google makes the same point: if you leave the file, anyone using the device can open it and read your passwords.
Pitfalls worth knowing
- Duplicates. Bitwarden's import can't check for duplicates, so importing several files creates duplicate items. Import once, or clean the file first.
- Import errors. If an item exceeds a field's encrypted character limit, Bitwarden won't import any of that item's contents. You'll see an error naming the problem entries.
- Odd CSV files. A Bitwarden community thread shows a user getting a generic error from a Chrome CSV, apparently because of unquoted commas or newlines in a field. The thread is a forum report, not an official diagnosis. It's a reminder to inspect a failing file rather than keep retrying.
- The plaintext window. The CSV holds every password unencrypted. Don't leave it in Downloads, email it to yourself or park it in a casual cloud folder. Work quickly, and empty the Recycle Bin if you want to be thorough.
- Old copies. After migrating, you may still have saved passwords in the browser. Decide whether to turn off the browser's autofill so two managers don't fight over the same login form. Apple notes that its own extension turns off a browser's built-in password saving, so this overlap is a real issue.
Checking Bitwarden's claims
The author says Bitwarden's free tier includes unlimited passwords and devices, passkey storage, password generation, credit cards and notes, and sharing with one other person. She says the authenticator and file attachments are paid. Those are vendor-published plan details that can change, so check the current pricing page before you commit. She also says Bitwarden encrypts data before it leaves your device, so the company can't read it. That's Bitwarden's stated design. Encryption doesn't protect you from a weak master password, a lost master password or an unlocked, compromised device.
One of her use cases needs care. Notes and cards are clearly supported. Wi-Fi passwords, license keys and recovery codes can go in notes or custom fields. I haven't verified a dedicated item type for each, so check how a given manager handles them before you rely on it.
Which should you pick?
- Stay with the browser manager if you use one browser family on a few devices and just want autofill, breach alerts and generated passwords. For that, it's convenient and has less setup.
- Consider a dedicated manager if you switch browsers or operating systems, share credentials, want folders, or want one vault for more than website logins.
- Think about your threat model at work. In a managed Windows environment, an IT policy may dictate which password tools are allowed. Check before moving corporate credentials into a personal vault.
The author's closing advice is sensible: if you're happy in one browser, the built-in tool may serve you fine, and if you often switch browsers or want to store more than logins, a dedicated manager is worth trying. Just treat the export file like the sensitive thing it is, and delete it when you're done.