---
title: How to test a seed phrase backup before you fund the wallet
url: https://bitcoinseedbook.com/test-a-seed-backup/
description: Restore your seed phrase backup on a wiped signer, compare the fingerprint and first address on its screen, include the passphrase, then re-test every year.
published: 2026-06-25
updated: 2026-06-25
section: E. Physical storage
tags: Cold Storage, BIP39, Passphrase
---

# How to test a seed phrase backup before you fund the wallet

A backup you have never restored from is a guess. You wrote the words once, maybe in a hurry, maybe with
a pen that skipped. The only way to know the copy works is to rebuild the wallet from it and see the same
wallet come back. Do that before any coins arrive, while a mistake costs nothing.

## What you compare

You need something that identifies the wallet without spending from it. Two things do the job, and your
signer can show both on its own screen.

- **The master fingerprint.** BIP-32 identifies a key by the Hash160 of its public key and calls the first
  32 bits of that the key fingerprint. Written out, it is eight hex characters. The fingerprint of the
  master key changes if a single word or a single passphrase character changes.
- **The first receive address.** The first address of the first account, for the same address type. If
  the restored wallet shows the same first address, it holds the same keys.

The xpub works too, but it is a long string and easy to misread. The fingerprint is short enough to compare
by eye, character by character.

Compare on the signer's screen. Never type your words, your passphrase or your xpub into a website to
"check" them, and never photograph the screen ([why](https://bitcoinseedbook.com/camera-screen-and-clipboard-leaks/)). Once the seed has been on a
networked computer, treat it as exposed.

## The test, step by step

You need your signer (a hardware wallet, or an air-gapped signer that keeps nothing between sessions), the
backup exactly as you stored it, and a pen.

1. Create the wallet on the signer. Write the words on your backup and, if you use one, set the passphrase.
2. Write down the fingerprint the signer shows for the passphrase wallet. Then open the receive screen and
   write down the first address. Keep this record with the passphrase copy, not with the words.
3. Wipe the signer, or use a second one that has never held this seed. A signer that keeps nothing
   between sessions starts empty every time you power it on.
4. Put the original record out of sight. Take out the backup from where you will actually keep it, not
   the draft on your desk.
5. Restore from that backup: enter the words, then the passphrase, the way someone else would have to.
6. Read the fingerprint on the screen. Compare it with your record, all eight characters.
7. Open the receive screen and compare the first address.
8. If both match, the backup works. If either differs, stop. Don't fund this wallet. Read the section on
   failures below.

Wiping a signer that holds an unfunded seed is safe: the worst outcome is that you start over with a new
seed. Don't wipe a signer that guards funds unless your backup has already passed this test.

## Include the passphrase

The passphrase is where a restore most often goes wrong, because nothing checks it. BIP-39 builds the seed with PBKDF2 and uses the text
`mnemonic` plus your passphrase as the salt. It also says every passphrase generates a valid seed, and only
the correct one opens the wallet you wanted.

So a typo doesn't produce an error. A capital letter you didn't intend, or a trailing space, opens a
different wallet with nothing in it. The words were fine and the backup still failed. A test of the
words alone leaves out the passphrase, and the passphrase has no checksum to catch a typo.

Type the passphrase from your written copy during the test, not from memory. If you only remember it, the
test tells you about your memory today, not about the copy your heirs will find. More on choosing and
storing it in [the 25th word](https://bitcoinseedbook.com/bip39-passphrase-25th-word/).

## Decode the cipher from the stored copy

If you store the seed as this site's cipher numbers, the decode is part of the backup and has to be part
of the test.

1. Take the numbers from the stored copy, the one in its hiding place.
2. Look up your cipher on [the cipher page](https://bitcoinseedbook.com/cyphers/) from a clean device, or from your offline copy of
   the tables.
3. Decode each number to a word on paper. Don't rely on what you remember the words to be.
4. Check each decoded word against the [BIP-39 English list](https://bitcoinseedbook.com/en-bip39/). A word that isn't on the list
   is a decoding or copying error.
5. Enter the decoded words on the signer and carry on from step 5 above.

A decoded phrase looks like any other, for example:

> pizza educate fat kiss domain venue … (this phrase is public: never use it for real funds)

The signer will warn you if the checksum fails, as BIP-39 requires of wallet software. For a 12-word
phrase the checksum is 4 bits, so a single wrong word still gets past it about one time in 16. The
fingerprint comparison catches what the checksum misses.

**Hiding is not encrypting.** The ciphers are public and a seed phrase carries its own checksum, so a
list someone recognises as a seed can be tried against every cipher in minutes. Add a BIP-39
passphrase to the wallet and keep it somewhere else.

## A dry run with a small amount

The restore test proves the keys. A dry run proves the whole path, from receiving to spending.

1. Send a small amount to the first receive address. Make it enough to cover a fee several times over.
2. Wipe the signer and restore from the backup again, passphrase and cipher included.
3. Spend the small amount to another address in the same wallet, signing on the restored signer.
4. Confirm the spend arrived.

Only then send the real amount.

## Built-in backup checks

Some hardware wallets have a backup check built in. Trezor calls it Check backup. You start it from
Trezor Suite and enter your words on the device. Trezor's guide for the Safe 5 says the device compares
the backup you enter with the one in its storage, doesn't keep what you entered, and shows on its own
screen whether the backup is okay. Trezor recommends running it before you wipe the device and before
every firmware update.

It is a good habit, with two limits:

- It checks the words. Trezor doesn't store your passphrase, so the check can't tell you whether the
  passphrase you wrote down is the one you used. Check the passphrase separately by opening the hidden
  wallet from your written copy and comparing its fingerprint or first address.
- It compares against the device's own copy. It doesn't prove that a different signer, years from now,
  restores the same wallet. A full restore on a wiped device does.

## Test again every year

Paper fades and ink runs. A stamped plate can carry a wrong letter you never noticed, and your own
handwriting can be hard to read five years on. Re-test once a year, and again whenever something changes:

- after you move house, or move a backup to a new hiding place;
- after you re-copy the backup onto [metal](https://bitcoinseedbook.com/metal-seed-backups/) or [new paper](https://bitcoinseedbook.com/paper-seed-backups-that-last/);
- after you [split it across places](https://bitcoinseedbook.com/split-a-seed-across-places/) or change who holds a part;
- after you change the passphrase or the cipher;
- before you put a backup back under a [tamper-evident seal](https://bitcoinseedbook.com/tamper-evident-seed-backup/), so the seal
  covers a copy you know is good.

The yearly test with a funded wallet is the same restore, on a second signer or a stateless one, without
wiping the signer you use every day. Compare the fingerprint and first address. You don't need to spend.

## If the test fails

Don't try to patch the old backup into shape. Until something happens to it, your original signer still
holds the keys, so you have time to do this properly.

1. Find the cause if you can: a misread word, a decoding slip, a passphrase character. Correct the written
   copy and test it again from the top.
2. If you can't make the backup restore the same fingerprint, treat the old seed as unrecoverable.
3. Create a new seed on the signer, back it up, and run the full test on the new backup until it passes.
4. Move the funds from the old wallet to the new one with the original signer, which still works.
5. Destroy the failed backup once the funds have moved.

Trezor's own guide gives the same advice for a failed Check backup: move the funds to a new wallet right
away, because without a valid backup, losing the device means losing the funds.

*We will never ask for a seed word or a passphrase. Never type one into this site or any tool it links to.*

## Sources


- [BIP-39](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki): the salt is "mnemonic" + passphrase; "every passphrase generates a valid seed", only the correct one opens the intended wallet; software must warn when the checksum is invalid; a 12-word phrase carries 128 bits of entropy and a 4-bit checksum.
- [BIP-32](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki): an extended key's identifier is the Hash160 of its public key, and "the first 32 bits of the identifier are called the key fingerprint".
- [Trezor: Check wallet backup on Trezor Safe 5](https://trezor.io/guides/backups-recovery/general-standards/check-backup-on-trezor-safe-5): the device compares the entered backup with its stored one and doesn't remember it; result shown on the device screen; test before wiping and before every firmware update; on failure, move funds to a new wallet immediately.
- [Trezor: Passphrase and hidden wallets issues](https://trezor.io/learn/a/passphrase-hidden-wallets-issues): passphrases are not stored on the Trezor; every character counts and passphrases are case sensitive.
