How to restore a Ledger from a seed phrase (recovery)

Restoring a Ledger hardware wallet from a recovery phrase (also called a seed phrase) is a routine operation but one that must be handled with care. This guide explains the steps I use in testing and the security trade-offs involved, with links to deeper resources (standards and internal guides) so you can verify every claim.

Why restore from a recovery (seed) phrase?

A recovery phrase is the textual representation of the private key material that controls your cryptocurrency. If your device is lost, damaged, or you buy a replacement, restoring from the recovery phrase allows you to recover access to your crypto holdings (Bitcoin, Ethereum, and other supported chains). The format is defined by the BIP‑39 standard (see the spec: https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki).

In my experience, people underestimate how often they will need a recovery: device failure, travel seizures, or simple hardware upgrades are common triggers. So, practice the process mentally before you need it. Ask yourself: do I know where my backup is? Who else knows it? (Hint: keep it offline.)

Safety checklist before you restore

Verify you are using a genuine device out of secure packaging (see supply-chain checks: /supply-chain).
Do not type the recovery phrase into a phone or computer unless using a fully air-gapped, audited tool. And never photograph it.
Confirm how many words your backup contains (BIP‑39 supports several lengths; common ones are 12/18/24 — see the spec above).
If you use a passphrase (the optional BIP‑39 passphrase sometimes called a “25th word”), make sure you remember it or have a secure record (see /passphrase-25th-word).
Update and verify firmware before you re‑connect to desktop apps (/firmware-updates and /verify-firmware).

Short checklist: offline space, correct word count, no cameras, verified firmware. Simple.

Restore methods: device vs other wallets (quick comparison)

Method	Pros	Cons	Best for
Restore directly on the device	Restores keys inside the device's secure element; never exposes full seed to a host computer	Slower (manual entry); you must be careful entering words correctly	Typical Ledger recovery — highest practical security for most users
Restore to another hardware wallet (BIP‑39-compatible)	Quick if device damaged; retains hardware-level protections on the new device	Must confirm derivation path / address formats; watch for passphrase differences	When device broken or you want a different hardware model
Import into a software wallet (not recommended)	Fast	Exposes seed to the host; increases risk of theft	Emergency-only, and only on air-gapped systems

(Images: Placeholder illustrations of on-device entry and a metal backup plate.)

Step-by-step: Restore directly on the device

This is the method I use first. It keeps the seed inside a secure element and avoids computers during input.

Power on the device and select the "Restore device" option on the screen.
Choose the recovery phrase length that matches your backup (the device will offer choices). If you built the original wallet with 24 words, select 24.
Create a new PIN when prompted. Do not reuse obvious numbers.
Enter your recovery phrase word by word. The on‑device interface will show an indexed field; use the device buttons to select words.
- For small-screen devices this is slower; be patient. For larger-screen models it's faster, but the principle is the same.
After the last word the device will verify the phrase and finalize the restoration.
Connect to the companion app (Ledger Live or another interface as needed) to add accounts and resynchronize balances (/ledger-live and /add-accounts-apps).

In my testing the time required varies by model and typing speed. Expect several minutes. If the device rejects the phrase, double‑check spelling and word order (order matters). If you used a passphrase during original setup, the base 24 words alone will not restore those assets — you must re-enter the passphrase too.

Sources: BIP‑39 (mnemonic/seed format) — https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki and device restore process documented in vendor support materials.

Restore to another hardware wallet or compatible app

If your original device is permanently damaged you can restore the seed to another BIP‑39 compatible hardware wallet or to an air‑gapped software tool. Two important caveats:

Ensure the replacement supports the same derivation scheme for each blockchain (for Bitcoin: legacy vs P2SH‑SegWit vs native SegWit produce different address prefixes). See /derivation-paths.
If you used an optional passphrase, the other device must use that same passphrase to derive the exact same accounts.

If you need to restore to a software wallet, prefer an air‑gapped workstation and a read‑only transfer method (QR, microSD). But be honest: if you can avoid exposing the seed to a general‑purpose computer, do so.

Common pitfalls and troubleshooting

Typo in a single word: causes restore to fail. Re‑enter slowly.
Wrong word order: the phrase is ordered. A single swapped pair will break the keys.
Wrong word list/language: BIP‑39 supports multiple word lists — ensure you’re using the same list as the original backup.
Missing passphrase: funds associated with a passphrase will look "missing" if you restore without it. (Remember passphrase is not stored anywhere.)
Addresses not appearing: confirm derivation path and account index; for Bitcoin a bech32 (bc1) address indicates native SegWit derivation.

If the device reports a system error during restore, check firmware and try the process again after verifying firmware (/firmware-updates, /verify-firmware). If the device is physically damaged see /device-broken for recovery options.

Security notes: passphrase, BIP‑39, and backups

The optional BIP‑39 passphrase increases security by creating effectively a different wallet for each passphrase value. But there’s a trade‑off. If you forget the passphrase, you permanently lose access to funds tied to that passphrase. I’ve seen both outcomes in testing: extra safety for some users, fatal loss for others.

Consider a metal backup plate (see /metal-backup-plates) for long-term storage. Fire and corrosion resistance matter. And store copies in geographically separated, secure locations if the funds are significant.

For high-value holdings, consider moving to a multisig arrangement (/multisig) — single-seed recovery is convenient, but multisig reduces single‑point-of-failure risk.

References: BIP‑39 spec (passphrase section) — https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki; SLIP‑39 (Shamir backup) overview — https://github.com/satoshilabs/slip39

Who this guide is for — and when to seek alternatives

This guide is for users who have a valid recovery phrase and need to restore access to their crypto, whether after device loss, damage, or upgrade. If you are uncomfortable handling the seed yourself, or if the situation involves legal/estate complexity, consider professional help (legal or security experts). But if you follow the safety checklist here, most users can complete restoration safely on their own.

If you hold large amounts of crypto, consider splitting exposure: one portion on an everyday single-sig hardware wallet and another portion secured with multisig and geographically separated backups (/cold-storage-strategies, /multisig-setup).

FAQ

Q: Can I recover my crypto if the device breaks?

A: Yes — if you have the recovery phrase you can restore to a new device or any compatible wallet (BIP‑39/BIP‑44/BIP‑84, depending on chain and address type). See /device-broken and /derivation-paths for guidance. (But make sure you remember any passphrase used.)

Q: What happens if the company that made the device goes bankrupt?

A: The recovery phrase encodes the private keys. As long as you control the recovery phrase (and optionally the passphrase), you can restore your funds using any compatible wallet. That’s why self-custody matters — not vendor continuity. See /company-risk for more discussion.

Q: Is Bluetooth safe for restoring or daily use?

A: Bluetooth can be convenient for mobile use, but it introduces additional attack surface compared with USB. For restores I prefer wired connections or on‑device-only restores to avoid exposing the seed to nearby devices (see /connectivity-usb-bluetooth-nfc).

Conclusion & where to go next

Restoring a Ledger device from a recovery phrase is straightforward when you follow basic safety steps: verify device integrity, keep the phrase offline, confirm word count and passphrase usage, and add accounts only after the device is restored. In my testing, patience at the restore step prevents mistakes later.

Want visuals and model-specific prompts? See the model setup and daily‑use guides: /nano-s-guide, /nano-s-plus-guide, /nano-x-guide and the setup checklist at /setup-initial. If you hit a problem, check /troubleshooting and /forgot-pin for step-by-step recovery paths.

If you found this guide helpful, follow the linked resources above to strengthen your backup and long-term cold storage plans. Good luck — and keep that backup offline.