Testing your backup: how to know your recovery phrase actually works

Most people write down their recovery phrase once, put it somewhere safe and never look at it again. That's the right instinct for security. It's also how backups quietly fail: a misspelled word, a skipped line, two words swapped, ink that faded, or a sheet stored in the one place that flooded.

You won't find out until you need it — unless you test it. Here's how to check your backup works without putting it at risk.

How backups fail

• Transcription errors. A word misread, misspelled or written in the wrong order. Recovery phrases have a checksum, so many typos are caught on restore — but you discover the problem only when you try.
• Missing pieces. A passphrase you added and forgot, a second phrase for another device, or the knowledge of which wallet the phrase belongs to.
• Physical damage. Water, fire, fading ink, a laminated sheet that peeled.
• Lost location. You remember making a backup, but not exactly where you put it.
• Single copy in the wrong place. One backup in the same house as the devices it protects.

Recovery 101 covers what a complete backup needs to include. Testing is how you confirm you actually have it.

Three ways to test, from lightest to most thorough

1. Check the words against the app. Many wallets offer a backup check: you re-enter or select your words, and the app confirms they match the phrase it holds — without showing the phrase on screen or sending it anywhere. It's quick and safe, and it catches transcription errors.

2. Restore on a test device. On a spare phone or a clean browser profile, restore the wallet from your written backup and confirm it shows the same addresses and balances. Then delete it again. This tests the full restore process — the words, any passphrase and your understanding of the steps.

3. Practise with small amounts first. If you're nervous about restoring a wallet that holds real funds, rehearse the whole process — create, back up, wipe, restore — with a fresh wallet holding a small amount, or on a testnet. Once you've done it once, the real thing is far less stressful.

Doing it safely

Testing should never create new risks:

• Never type your phrase into a website or any app you didn't deliberately choose for the restore.
• Use an offline or trusted device for a full restore test, and remove the wallet afterwards.
• Don't photograph the phrase to make testing easier.
• Don't test in public or within view of cameras.
• Put the backup back exactly where it belongs and check the storage itself while you're there.

How often

• Right after creating it — the most important test, before any real funds arrive.
• After any change: a new passphrase, a new storage location, a recopied backup.
• Once a year or so as routine, together with a check that the physical backup is still intact and readable.

Testing your backups in SSP

SSP has two recovery phrases — one for SSP Wallet, one for SSP Key — and your vault needs both keys. That makes testing both backups doubly important: a perfect SSP Wallet backup doesn't help if the SSP Key backup is wrong.

SSP builds the check in:

• SSP Key has a backup check under Settings, "Verify seed backup". After you confirm with your biometrics or password, it asks you to pick your seed words from among decoys, and confirms they match — without displaying the phrase. It also shows a periodic "Backup checkup" reminder on the home screen.
• SSP Wallet shows a backup-health card under your balance until your seed phrase has been verified and SSP Key is paired, so you can see at a glance whether anything still needs securing.

For a full restore test, you can restore either app from its phrase on a separate device. Keep the two phrases stored apart: the point of two keys is that one compromised location isn't enough to take your funds — seed phrase best practices covers how to store them.

The honest summary

A backup you've never tested is a hope, not a plan. Errors creep in when words are written down, paper degrades and memories fade — and you only discover it at the worst possible moment.

Check your words against the app when you create them, do a full restore test on a spare device at least once, and repeat the check every year or after any change. With SSP, do it for both phrases.