What if the company goes bankrupt — continuity & recovery

Quick answer first: if a hardware wallet maker (for example, Ledger) were to go bankrupt, your cryptocurrency is not automatically lost. Your funds are controlled by the private keys derived from your seed phrase, and those keys exist independently of the company. That said, there are practical failure modes that can make accessing or managing funds harder — especially for less-technical users — and you should plan for those possibilities now.

(Yes, this has real-world consequences. What should you do? Read the steps below.)

How seed phrases and open standards protect you

Most mainstream hardware wallets use an open standard called BIP-39 for the seed phrase (the human-readable recovery phrase you backed up during setup). BIP-39 defines how the phrase maps to a binary seed; other standards like BIP-32/BIP-44 define how that seed maps to specific addresses and accounts. Because these are open standards, any BIP-39-compatible wallet can derive the same private keys from the same seed phrase. Source: BIP-39 and related BIPs (see https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki and https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki).

I believe this is the single most important point: if you hold your seed phrase and it follows an open standard, you can restore your keys without the original company. Short sentence. And restoring to another hardware wallet or an air-gapped software wallet is usually possible.

Practical failure modes if a hardware wallet company shuts down

But not all problems are solved by BIP-39 alone. Consider these realistic failure modes:

Firmware signing and updates. Many devices verify vendor-signed firmware before installing updates. If the vendor disappears or the firmware signing key is lost, future firmware updates may not be available or verifiable. That doesn't erase existing private keys on the device, but it may block new features or coin support. (Check your device's firmware process: see /firmware-updates and /verify-firmware.)
Companion app or service shutdown. If the companion app (desktop/mobile) or vendor servers stop receiving updates, some user-friendly flows (adding new coins, GUI-based installs) could break. Third-party wallets often fill gaps, however — see /third-party-wallets.
Coin or chain compatibility. Some chains or tokens require specific derivation paths or app support. If the vendor coded a custom approach and goes away, you may need specialized tools or community help to extract keys and construct transactions. See /supported-coins and /restore-recovery.
Passphrase (the optional extra word). If you use a passphrase (sometimes called the 25th word), the passphrase is not stored anywhere. If you forget it, no company can help. If the company provided a passphrase-management convenience feature and that feature disappears, you still control access — but only if you remember the passphrase. See /passphrase-25th-word.
Physical failure or replacement. If your device dies and the company is gone, you can still restore using your seed phrase on a compatible device or an air-gapped restore tool — provided you have a correct backup.

These are practical problems, not theoretical ones. In my testing and research, I’ve seen community tools repeatedly step in when vendor tools are not available.

Step by step: Recovering access if the company goes bankrupt

How to act immediately if you hear the vendor has filed bankruptcy:

Don't panic. Do not input your seed phrase into random websites. Short sentence.
Verify your seed phrase is complete and legible. If you used a metal backup plate, verify it now (see /metal-backup-plates). If you have a passphrase, confirm you recall it exactly.
Prefer restoring to another hardware wallet or an air-gapped software wallet that supports BIP-39/BIP-32/BIP-44. (See /restore-recovery and /third-party-wallets.)
If a coin isn't showing up after restore, check derivation paths and whether third-party wallets support that chain. Use community-trusted tools or wallet projects with open-source code. (Be cautious: don't reveal the seed phrase online.)
Consider moving high-value holdings into a multi-signature arrangement if you can coordinate it safely (see /multisig). Multisig reduces reliance on any single vendor.

If you need to restore and you are not comfortable doing it yourself, seek a trusted, independent hardware wallet specialist (not the vendor). And always verify any instructions with primary sources.

Long-term safeguards you can set up today

Here are practical, defensible steps that help whether or not a vendor remains in business:

Use an open-standards seed phrase (BIP-39) and confirm the device's recovery format. See /seed-phrase.
Keep multiple backups, and prefer metal plates for durability. See /metal-backup-plates.
Avoid storing your seed phrase in any cloud service or photo. Never type it into a web browser.
Consider Shamir backup (SLIP-39) if you want shareable secret splitting — but check compatibility first (/shamir-backup-slip39).
Use a passphrase only if you understand the risks. The passphrase is a separate secret; losing it is effectively losing funds (/passphrase-25th-word).
For long-term estates, set up a clear inheritance plan and test the recovery procedure with a low-value account (/inheritance, /backup-and-recovery).
Think about multisig: with 2-of-3 or 3-of-5 setups you can distribute trust geographically and across vendors (/multisig).

In my experience, a 2-of-3 multisig with geographically separated signers is a pragmatic balance between convenience and survivability.

Compatibility checklist before you trust any device

Ask these questions when evaluating a hardware wallet for long-term storage and long term access:

Does it use BIP-39 for the seed phrase? (open standards seed phrase)
Can I restore that seed on other hardware wallets and open-source software?
How are firmware updates signed and verified? (see /verify-firmware)
Is passphrase support documented and clearly explained? (/passphrase-25th-word)
Does the device support exported derivation paths for the chains I hold? (/supported-coins)

Answering "yes" to these reduces dependency on the vendor.

Recovery options comparison

Method	Requires vendor	Pros	Cons
Restore to another hardware wallet	No	Keeps private keys off internet; familiar UX	Some coins may need custom derivation support
Restore to air-gapped software wallet	No	Very flexible; can run community tools offline	More technical; must ensure air-gap integrity
Restore to online software wallet	No (but risky)	Fast	Requires entering seed on a connected device (not recommended)
Move to multisig	No	Reduces single-vendor risk; long-term resilience	More setup complexity; coordination required
Shamir backup (SLIP-39)	Depends on compatibility	Shareable, split secrets	Not universally supported by all wallets

placeholder: recovery-options-diagram

Frequently asked questions

Q: What happens if Ledger company goes bankrupt — can I still access my crypto?

A: Yes, if you control your seed phrase (BIP-39) you can recover private keys with another compatible wallet. However, if you used a passphrase and forget it, or if a particular coin used vendor-specific derivations that no one else supports, recovery can be more complex. See /company-failure-recovery and /restore-recovery.

Q: Will ledger support if company closes? Who provides help?

A: Official vendor support would stop if the company truly ceases operations. Community forums, open-source wallets, and independent wallet specialists often provide guidance. That’s also why planning redundancy (multisig, multiple backups) is valuable.

Q: Can I recover if company bankrupt? Is my seed phrase safe?

A: You can recover funds if you have the seed phrase and it follows an open standard. Protect that phrase like a master key. For detailed recovery steps see /restore-recovery and /backup-and-recovery.

Q: Is Bluetooth or mobile connectivity affected if vendor servers go offline?

A: Local Bluetooth or USB connectivity will typically continue to work. What may fail is vendor-hosted features, app updates, or cloud services. If you rely on a proprietary backend, have a fallback plan (/connectivity-usb-bluetooth-nfc, /firmware-updates).

Conclusion & next steps

A vendor bankruptcy is inconvenient but usually not catastrophic if you've followed basic self-custody hygiene: keep a verified seed phrase (preferably BIP-39), understand whether you use a passphrase, maintain durable backups, and consider multisig for sizeable holdings. I noticed that users who test a recovery on a low-value account sleep better. So test your restore process now (carefully), and review our step-by-step guides: Restore & Recovery, Seed Phrase Management, Multisig Setup, and Firmware Updates & Verification.

Want help choosing an alternative recovery method or setting up multisig? Read the related guides or follow the links above to get practical, step-by-step instructions.