Trezor passphrase recovery

A lost Trezor passphrase feels hopeless because Trezor, by design, stores it nowhere and cannot reset it. With the correct wallet backup, candidate passphrases can be checked against a known address; success depends on how much the search can be narrowed. The first thing to sort out is which secret you have actually lost, because people routinely confuse three different things.

Passphrase vs PIN vs seed — know which you lost

These get mixed up constantly, and the recovery path is completely different for each:

• The PIN only unlocks the physical Trezor. It is not part of your keys. If you forgot the PIN but have your recovery seed, you don’t need it — you simply restore the seed. On-device PIN attempts are subject to device-specific protections; do not experiment with a locked device without understanding its recovery options.
• The wallet backup may use BIP39 words or a SLIP39 backup/share set, depending on the setup. Identify the format and required shares before assessing recovery. A lost paper backup is a different problem from losing access to a working device.
• The passphrase is an optional string used with the backup to derive a separate hidden wallet. “25th word” is only a nickname; it need not be one word, and it is not the device PIN.

If you have the seed and only the passphrase is missing, you are in the best possible position. The rest of this guide is about that case.

What a Trezor passphrase really is

When you enable a passphrase, Trezor takes your recovery seed and your passphrase together and derives an entirely new set of accounts — the hidden wallet. Change a single character of the passphrase and you get a completely different, valid, empty wallet, with no error message. There is no “wrong passphrase” warning because every passphrase is technically valid; each just opens a different wallet.

The passphrase is case-sensitive and must reproduce the original input. Trezor’s official passphrase guidance describes a limit of 50 characters and why a different passphrase opens another wallet. Device model, firmware and backup standard still matter when investigating an older setup.

The good news: if you still have your recovery seed

With your seed words in hand, a lost passphrase becomes a search rather than a dead end. We take your seed, generate passphrase candidates, derive the hidden wallet’s addresses for each, and compare them to a receiving address you know was yours. The instant the derived address matches, we have the passphrase — but any recovery process involving a wallet backup requires an explicitly agreed method for protecting that sensitive material.

This is why we always ask for a target address from the hidden wallet: it is the anchor that tells us, with certainty, when a candidate is correct.

Why a “correct” passphrase fails — the part most people miss

An empty hidden wallet has several possible explanations: different passphrase characters, the wrong backup, a different account path, incomplete synchronization or funds that have moved. Verify a known address and its history before assuming the remembered passphrase is correct. Input checks include:

• Smart quotes. A phone or macOS auto-correcting a straight ‘ or “ into a curly ’ or ” changes the passphrase completely.
• Wallet-standard handling. BIP39 specifies NFKD normalization, so canonically equivalent Unicode forms should not by themselves produce different BIP39 seeds in a compliant implementation. Check the original backup standard and actual input behavior before attributing an empty wallet to encoding.
• Keyboard layout. A passphrase created on one layout and re-typed on another can swap y/z, or special characters, without you noticing.
• Stray spaces and invisible characters at the start or end, or a capital where you meant lowercase.

Reproducing and sweeping these variations is a core part of what we do — and it is often the whole reason a “lost” passphrase is recovered in minutes rather than never.

How Trezor passphrase recovery works

Recovery is a structured search, not blind guessing. From everything you can tell us — the length, a theme, partial recall, the language and keyboard you used, words or numbers you tend to reuse — we build targeted candidate sets and then expand them with mutations: capitalisation, spacing, common substitutions, and the smart-quote and Unicode variants above. Each candidate is derived across the standard paths (m/44’/0’/0′, m/49′, m/84′ for Bitcoin, and the Ethereum path where relevant) and checked against your target address.

Because the check is a derivation rather than an online guess, it runs fast and entirely offline — there is no device to lock out and nothing leaves our hardware. When a candidate’s derived address matches yours, the passphrase is confirmed and you regain access to the hidden wallet.

What information helps an assessment

• Backup availability and type: whether BIP39 words or a SLIP39 backup/share set survives, and whether the device still works. Do not send the words in the first message.
• A known receiving address: helps identify the intended hidden wallet and check a recovered candidate.
• Non-sensitive passphrase context: approximate length, language, keyboard and whether useful hints remain. Detailed material requires an agreed secure process.

What we can’t do — honestly

A passphrase search requires the correct underlying wallet material, or a separately assessed way to recover it. If the paper backup is missing but the device still works, preserve it and assess available options before resetting anything. If no usable backup, sufficient share set or accessible device remains, recovery may be impossible; a long random passphrase with no useful hints may be infeasible. PIN recovery is separate and depends on the model and firmware.

KeychainX’s recovery team has worked on wallet-access problems since 2017. Its reported 1,000+ clients and about 79% overall success rate cover multiple wallet types, not the odds of recovering a Trezor hidden-wallet passphrase.

Frequently asked questions