Both hold secrets; they are built for different shapes of secret
A password manager is optimised for many small, frequently-retrieved strings that need to be injected into login forms. A file vault is optimised for fewer, much larger objects that need previewing, organising, exporting and backing up.
The overlap in purpose — protecting things you do not want others to see — hides how different the data models and workflows are.
What a password manager does that a vault should not
Autofill is the defining feature. A manager integrates with the operating system to recognise a login field and supply the right credential, which reduces both typing and phishing exposure by matching on the actual domain.
Modern managers also handle passkeys, credential generation, and breach monitoring. A file vault has no business in that workflow, and using a photo gallery or notes app for credentials gives up all of it.
What a file vault does that a manager should not
Managers usually support attachments, and people reasonably assume that makes them a document store. In practice attachment handling is a secondary feature with size limits, weak preview support, and export behaviour built for occasional use.
A vault designed for media handles original-quality import, playback, thumbnails, albums, search, and a backup format intended for bulk restore. Those are the properties that matter when you are storing hundreds of files rather than a handful.
Use both, with separate recovery plans
- Keep login credentials and passkeys in a manager designed for autofill.
- Keep media and documents in storage designed for file integrity and export.
- Give each its own recovery method, and store them in different places.
- Test both recovery paths before you depend on either.
The circular-dependency mistake
There is one arrangement worth naming because it looks sensible and is not: storing a vault's recovery phrase inside the vault's own backup, or storing a manager's master credential in the vault it protects.
- Storing a vault recovery phrase beside the vault backup it unlocks.
- Keeping the password-manager master credential only inside the file vault.
- Using a photo gallery or notes app as a password manager.
A fictional example
Amara starts with a non-sensitive test: “Keep login credentials in a manager designed for autofill.” Next, Amara follows the second check: “Keep large files in storage designed for file integrity and export.” This fictional scenario demonstrates the decision process; it is not a report of product testing.
Common mistakes
- Storing a vault recovery phrase beside the vault backup
- Using a photo gallery as a password manager
What this workflow does not change
- Storing a vault recovery phrase beside the vault backup
- Using a photo gallery as a password manager
Questions people ask
Should a crypto seed phrase go in either app?
Follow the wallet provider's recovery guidance and prefer an offline plan designed for catastrophic loss.