1Password: Password Manager

You offer an import feature but cannot read the most widely used open password format in existence: KDBX. Instead, I'm expected to push my entire database through CSV or XML. That is indefensible, for two reasons. 1. You lose data without telling anyone. CSV and XML have no concept of file attachments. My vault holds dozens of documents — ID scans, licences, certificates. Your migration path discards all of them. The same goes for passkeys, custom fields, and in part for TOTP secrets. Mentioning this in a subordinate clause in a support article is not disclosure: the import dialog itself warns no one. Most users will discover the loss months later, when they go looking for a document and the original database is long gone. A migration path that silently drops data isn't a migration path — it's a trap. 2. The only route into your product runs through an unencrypted copy of every secret I own. You require me to write my complete credential set — including TOTP secrets, meaning first and second factor together — to disk in plaintext, then upload it through a browser form. On macOS that means, concretely: the file enters the Spotlight index, Time Machine captures it, it persists in the hourly local APFS snapshots macOS retains for days, and if it sits in Desktop or Documents, iCloud syncs it off the machine without being asked. On an SSD it cannot even be reliably deleted afterwards — wear levelling leaves copies in blocks the filesystem can no longer address. You manufacture precisely the condition your own product exists to prevent, hand the cleanup to the user, and mention none of it. Which raises the obvious question your documentation does not answer: is that file processed client-side in the browser, or on your servers? For a company selling zero-knowledge architecture as its core promise, that should not be left to inference. 3. There is a better way, and you know it. KDBX is an openly documented format with mature open-source implementations — KeePassXC, kdbxweb, pykeepass. Competitors such as Keeper have shipped direct .kdbx import for years. And the import belongs in the desktop app in the first place, where the vault key already resides; done there, no decrypted file ever has to exist. This isn't a research problem. It's a prioritisation decision, and you made it. What I expect: - Native .kdbx import in the desktop app, including attachments and TOTP. - Until then, an unmissable warning inside the import dialog stating exactly which data will be dropped — not buried in a support article. - A clear statement in the import flow about where the uploaded file is processed and how long you retain it. I ended the trial after a few hours. I was your customer for years, until version 8 wrote off the licences I had paid for in favour of mandatory subscriptions. That you now can't even make migration into your product safe rather confirms that decision than reverses it.

Ich finde 1Password sehr gut. Ich habe einige Passwordmanager ausprobiert und letztendlich 1Passord gewählt. Es gibt eine Funktion, die ich mir wünsche: eine Einstellung, mit serbisch direkt nach dem Start der App alle Einträge angezeigt bekomme!

für eine passwortverwaltung mit mehreren usern auf verschiedenen systemen ist es immer noch am leichtesten mit 1PW die änderung des inlinepopups hat mich leider zeit gekostet die ursache zu finden. man muss in den systemeinstellungen die autofill-funktion ausschalten. dann ist alles wieder wie vorher. steht in den updatebeschreibungen drin, aber ich habe das zuerst überlesen

Leute, hört auf, so an 1Passwort festzuhalten, als gebe es keine Alternativen! Man muss sich diese gierige Preiserhöhung wirklich nicht bieten lassen. Die interne Passwortverwaltung von Apple Passwörter ist komplett kostenlos und funktioniert mittler problemlos auf Windows. Ich bin über die letzten Jahre peu à peu dorthin gewechselt und bin jetzt einfach nur glücklich. Spart euch das Geld und den Ärger über immer teure Abos. Ein Wort an das ein Passwort Team: Gratulation, eure Preispolitik treibt die Leute direkt zur kostenlose Konkurrenz. Wer glaubt, er könnte seine Kunden durch angesammelten Daten als Geisel halten und beliebig abkassieren, hat sich gewaltig geschnitten. Viel Spaß dabei, zuzusehen, wie euch Nutzerbasis wegbricht.

I decided to renew for the higher price since I use it. Hope such a thing will never happen again. Stupid idea to try and force a renewal by blocking access. --- before 2026-03-17 --- So you are seriously instantly blocking access to my account until I immediately consent to price increase. And you are in the trust and security business right? Stay away from this product they will take your passwords hostage. -- Edit 16/3/2026 - to be clear: This is was not a technical problem. 1Password placed a blocking banner over the app on each device to either immediately accept the price increase or cancel the subscription with no way to bypass the banner. The fact that they try and deceive you into thinking this was some technical error again tells you more about the length they will go to. Very sad.

The in-page autofill widget has started failing on more and more pages since a few weeks. Clicking an entry does nothing. 1Password just keeps getting worse and worse while they raise prices. Unbelievable.