If you are searching for how to create multiple wallets on ledger, start by clarifying terms. An account in Ledger Live is an entry derived from the same seed phrase using a specific derivation path. A wallet in the colloquial sense can mean a completely separate seed phrase (and therefore a separate recovery). An address is an on-chain identifier you receive funds to. Short sentence. I believe mixing up these terms causes most user confusion.
In my testing, I found that Ledger Live treats accounts as virtual containers. You can add many accounts for a single coin without generating additional seed phrases. But creating a new wallet on the device typically means initializing it with a new seed phrase, which removes previous keys unless you back them up first.
(If you want a primer on recovery and seed phrases, see seed-phrase-basics.)
How many wallets can you have on Ledger? The answer depends on what you mean by wallet. If you mean separate seed phrases: you can initialize the device with a new seed, but that replaces the current seed on-device — you must back up the old seed first. If you mean accounts within Ledger Live: you can create many accounts per currency. That is effectively unlimited for practical purposes, because accounts are an index in the derivation tree rather than another private key stored on the device.
The caveat: installing multiple coin apps on the device consumes device storage. So you may need to manage apps using the steps in install-apps-manage-space. And note that different address types (legacy, segwit, native segwit) are separate accounts in Ledger Live.
How to create multiple accounts on Ledger? Here is a practical how-to.
If you want separate accounts for spending and long-term storage, create two accounts and label them (Savings, Spending). I did this to separate my long-term BTC from day-to-day funds. It keeps UTXOs tidy and makes fee estimation easier.
Table: quick feature comparison
| Action | Uses same seed phrase | Requires device reset | Easy in Ledger Live | Best for |
|---|---|---|---|---|
| Create additional account | Yes | No | Yes | Separate balances without new backup |
| Create new wallet (new seed) | No | Yes (initializes new seed) | No (done on device) | Full separation, different recovery |
| Add existing wallet (recover) | No (uses recovered seed) | Yes (device is restored) | No (done on device) | Move keys from another device or restore |
Create new wallet Ledger workflow (high-level): initialize the device, choose Create new wallet, write down the recovery phrase, confirm the phrase on-device. Then add accounts in Ledger Live.
Add existing wallet to ledger (recovering a seed): choose Restore on the device, enter the recovery phrase (12 or 24 words depending on the original), then reconnect to Ledger Live to sync accounts. Avoid entering your seed phrase anywhere other than the hardware wallet itself. See restore-recover-failure for troubleshooting.
For Bitcoin and UTXO chains, each account can generate many addresses. Use a fresh receive address for each incoming payment to improve privacy. But that creates multiple UTXOs, which can increase fees when consolidating later. Trade-offs exist.
For account-based chains like Ethereum, a single account usually maps to a single address. Create additional Ethereum accounts in Ledger Live when you want distinct on-chain identities (one for DeFi, one for collectibles). I noticed gas estimations are simpler when accounts are separated by purpose.
For more on address reuse and UTXO management, see privacy-addresses-utxo.
If you need more than separate accounts, multisig is an option. Multisig requires multiple signing keys across devices or signers, and can dramatically reduce single point of failure risk. But it adds operational complexity. Which should you choose? For large holdings or inheritance planning, I recommend exploring multisig-setup-ledger (and take your time during setup).
Advanced users may also use different derivation paths or a passphrase (25th word) to create hidden accounts. But passphrase use carries risks; if you lose the passphrase you lose funds. See passphrase-usage-risks.
Common mistakes I see:
Firmware updates matter. Keep device firmware current and verify updates through Ledger Live and the device prompts. If you need a refresher, read firmware-update-verify. And never type your recovery phrase into a PC or browser; only enter it when restoring on the hardware wallet itself.
Bluetooth vs USB? Bluetooth convenience has trade-offs for threat models. For many people USB is fine. See connections-usb-bluetooth-nfc for details.
Best for:
Not the best fit for:
Q: Can I recover my crypto if the device breaks?
A: Yes. If you have the recovery phrase, you can restore to another compatible hardware wallet or a recovery tool (prefer hardware). See restore-recover-failure.
Q: What happens if the company goes bankrupt?
A: Your funds are non-custodial. The keys are yours via the seed phrase. Company status does not unlock or lock your funds. Still, software support may change; keep local backups and export transaction history if needed. See company-bankruptcy-and-business-risk.
Q: Is Bluetooth safe for a hardware wallet?
A: For many users, Bluetooth is acceptable but comes with a higher remote attack surface compared with USB. Consider your threat model and read connections-usb-bluetooth-nfc.
Q: How many wallets can you have on Ledger?
A: You can add many accounts in Ledger Live without new seed phrases. Creating multiple wallets with separate seeds requires initializing new seeds and separate backups.
Managing multiple accounts and addresses gives you flexibility: separate budgets, better privacy, and cleaner bookkeeping. But remember this: accounts are convenient, while separate wallets (separate seed phrases) give full separation. I recommend testing an account-first approach: create extra accounts, label them, and watch how your workflow changes. What Ive found is that the extra accounts reduce mistakes when sending funds.
For step-by-step setup guides, check getting-started-setup and ledger-live-download-install. If you plan multisig or advanced derivation paths, the links above will help you plan safely.
And if you run into trouble, consult troubleshooting-common-errors or the device-specific walkthroughs like walkthrough-nanos-step-by-step.
Want more depth on backups and inheritance? See backup-recovery-best-practices.