"Never write your passwords down" was gospel for decades — the sticky note under the keyboard became security's favorite cautionary tale. But the advice aged strangely. In a world of phishing, credential-stuffing, and infostealer malware, the attacks that actually empty accounts arrive over the network, and a piece of paper in your home is invisible to all of them. Paper was never the problem. Plaintext was the problem — and that part is fixable.
What Paper Gets Right
Judged purely as a storage medium for secrets, paper has properties that no digital system can match:
- No remote attack surface: a printed page cannot be phished, breached in bulk, or reached from another continent — an attacker needs to physically stand in your home
- Immune to malware: infostealers can harvest browser-saved passwords and scan disks for "passwords.txt"; they cannot read a drawer
- Survives you forgetting: human memory is the least reliable password store there is — paper doesn't forget, and it never locks you out for too many wrong attempts
- No dependencies: it works during an internet outage, a service shutdown, a dead phone battery, and a decade of technology churn
- Understandable by anyone: in a family emergency, a printed page needs no onboarding — a point that matters more than most security advice admits
Paper also ages better than digital formats do. A file format, an app, or a cloud service from ten years ago may be unreadable today; a printed page from ten years ago reads exactly as it did. That archival quality is why the important half of this approach is keeping the decryption path just as durable — SecurePaper publishes its data format openly and ships a standalone decryptor for precisely that reason, as covered below.
The Obvious Flaw
Of course, the old advice existed for a reason: a plaintext note is readable by absolutely anyone who finds it. The burglar who takes the laptop also takes the notebook next to it. The visitor, the contractor, the coworker at the next desk — physical security in most homes and offices is a drawer that doesn't lock. And unlike a digital breach, a glanced-at notebook leaves no log; you will never know it happened.
So the real question was never "paper or no paper." It is: how do you keep paper's unhackability without its readability? The answer is the same one we use for digital storage — encryption — applied before the ink hits the page.
To Be Clear: Use a Password Manager Day-to-Day
Nothing here argues against password managers. For daily use they are the right tool — they generate strong unique passwords, fill them automatically, and warn you about reuse. If you don't use one, start.
But password managers have a backup story problem of their own:
- The master password is unrecoverable by design: in a properly built zero-knowledge manager, forgetting it means losing the vault — the vendor cannot help you
- Lockouts happen at the worst times: a lost phone can take your authenticator with it, leaving you locked out of the very vault that holds your recovery information
- It is a single point of failure: one credential now stands in front of every account you own
- The vendors themselves reach for paper: nearly every major password manager's own recovery process ends with a recovery kit or emergency sheet you are told to print and store safely — the industry already concedes that the root of trust belongs offline
Encrypted Paper: The Backup Layer
This is exactly the gap SecurePaper's password backup use case fills. You type the handful of root credentials into your browser; they are encrypted locally with AES-256-GCM — the plaintext never leaves your device — and you print the result. What goes on that one page is short:
- Your password manager master password
- Your primary email password (the account that resets everything else)
- Recovery codes for your most critical accounts
How the printed page behaves compared to the plaintext note:
| Scenario | Plaintext note | Encrypted paper |
|---|---|---|
| Someone finds it | Full compromise, possibly unnoticed | They see an unreadable code — nothing exposed |
| Remote attack / malware | Immune | Immune |
| Fire or flood | Lost — extra copies too risky to make | Covered by spare copies, which are safe to distribute |
| You forget the credential | Recovered by reading | Recovered by decrypting with your key or passphrase |
The honest trade-off sits in that last row: encryption moves the risk from the paper to the key. In passphrase mode the key is derived from your passphrase with PBKDF2 at decryption time, and nothing is stored anywhere — powerful, but only as good as your ability to remember (or share) the passphrase. With a generated key, export it as a JSON backup and keep it separate from the printed page. And you are not betting on us: the offline decryptor is a standalone file that decrypts your documents even if SecurePaper disappears. The full data format is published on the security page.
The Threat Model, Honestly
Encrypted paper is not magic, and it is worth being clear about what it does and does not defend against:
- It defends against discovery: the burglar, the visitor, the moving company, the roommate — anyone who encounters the paper without the key learns nothing
- It defends against everything remote: once printed, there is no server to breach and no file to steal
- It does not fix a weak passphrase: in passphrase mode, someone who takes the paper can attempt guesses offline. PBKDF2 key derivation makes each guess expensive, but it cannot rescue "password123" — use a long passphrase, ideally several unrelated words
- It does not protect the moment of use: when you decrypt, the plaintext is briefly on a screen — do that at home, not over an airport's shoulder-height seating
- It shifts risk to key custody: lose the key or forget the passphrase and the backup is gone — which is why the key export and a shared passphrase exist
For a personal backup sheet, that trade is excellent: the threats you actually face — opportunistic discovery and remote compromise — are covered, and the residual risks are ones you control directly.
Putting the Layers Together
A complete personal setup ends up pleasantly simple:
- Daily driver: a password manager with strong, unique passwords for every account
- Backup layer: one encrypted printed page holding the master password, email password, and critical recovery codes — a copy at home, a copy somewhere else
- Emergency layer: a plan for how a trusted person decrypts that page if you can't — our guide to the family emergency envelope covers the patterns
The same logic extends to the other paper-worthy secrets — we've written separately about where to keep 2FA backup codes — and the getting started guide takes you from blank page to printed backup in a few minutes. SecurePaper is free, so the whole backup layer costs you a sheet of paper.
Conclusion
So — is it safe to write passwords on paper? Written in plaintext, no: you are trading remote risk for local risk. Encrypted first, yes: you keep everything paper does well — unhackable, malware-proof, forgetting-proof, dependency-free — and remove the one thing it does badly. Keep the password manager for every day. Keep one encrypted page for the day the password manager isn't enough.
Print Your Backup Layer
The emergency access template has fields for your password manager, master password, and key accounts — encrypted in your browser, free, no account required.