Add Account Ledger Live Including Derivation Path Settings
How to Add an Account in Ledger Live App: connect the hardware wallet, enter its PIN, open the companion software, install the matching network package on the device, then create a coin-specific record and verify the receive address on the device screen.
The companion software never holds the seed phrase or private keys; those remain inside the secure element. A coin-specific record is only a public view: it stores an extended public key and a label on the computer or phone, while signing stays on the device. Before creating any record, install the corresponding network package on the hardware wallet and confirm the device displays the same address shown by the companion.
Choose the network from the companion’s list, connect the device with USB or Bluetooth depending on model, and let the software read the public key. Give each entry a distinct label such as “Long-term storage” or “Trading buffer”; duplicate labels make later transaction checks harder. If the device screen asks for confirmation, read the address and network name on the hardware display rather than trusting the computer screen alone.
When the companion shows a new record, verify three items: the network ticker, the derivation path, and the receive address. The ticker must match the asset; the derivation path must match the standard used by that network; the address must match what the hardware screen displays. If any element differs, stop and reconnect the device, because a mismatched public key or stale cache can create a record that never reflects the correct balance.
For multiple assets, repeat the same procedure per network. Each record uses its own public key and address set; one device seed can back many records, but the companion cannot sign without the physical confirmation. Keep the device firmware current through the official companion, and check the manufacturer’s support pages for network-specific notes before large transfers. A hardware-confirmed address is the only reliable destination check for incoming funds.
Check Ledger Live Version and Ledger Device Firmware Before Adding an Account
Verify both builds before touching the coin catalog: open the client’s Settings panel, read the release number under About, then compare it with the figure displayed on the signer under Settings → General.
A mismatch between those two builds is the usual cause of a new asset entry failing to appear, because the coin list the dashboard renders is generated from the pair in use. When the desktop or mobile software lags behind, that list can hide token programs the secure device already handles.
Refresh the firmware only from inside the official companion suite. Keep the physical signer attached by cable or paired over Bluetooth, confirm the install prompt on the device’s own screen, and never cut power mid-write. If an unexpected message appears or the progress bar freezes, stop and consult the official support pages instead of retrying through third-party utilities, which can leave the secure element in a broken state. Once the write completes, the signer restarts and requests the PIN again; re-enter it, let the client re-sync, and only then create a balance entry.
Reverse the order when the situation demands it: refresh the desktop or mobile client if the hardware signer already carries newer code.
Never install token software from outside the manager tab.
To confirm the pairing works, open the manager, install the required asset program, then set up the coin record. The client will ask the signer to export a public address, which must match the string shown on the device display and be approved by a physical button press there – that confirmation is the only proof the address belongs to your keys.
Skipping the comparison produces recognisable symptoms: an empty asset catalog, a program that installs but never populates a portfolio slot, or a connect loop that keeps restarting. Each of those points to mismatched builds rather than a faulty cable. Release notes published on the official site state which pair is tested together.
Recheck both builds after every major refresh cycle, and again whenever a program refuses to install – the listing the companion software shows depends on that pair staying current.
Connect and Unlock Your Ledger Hardware Wallet in Ledger Live
Plug the hardware device into a computer with the supplied cable, launch the desktop or mobile companion, and enter the PIN directly on the device screen.
USB remains the most predictable route because it carries power and data without pairing; Bluetooth suits phones and tablets, yet it requires the device to be charged and paired through the companion’s settings.
When the companion asks for the device, choose the correct model, confirm the connection on the hardware screen if prompted, then type the PIN using the device buttons or touchscreen; the software never sees that code, and the private keys stay on the secure element. If the device is locked, the companion displays a connect prompt; if it is already open, it displays the dashboard. Never enter the recovery phrase into the computer, phone, or any website.
For Bluetooth on a phone, enable location permissions if the operating system demands them for scanning, keep the device within a few feet, and confirm the pairing code matches on both screens.
After connection, the companion checks firmware status; if an update is required, install it via the desktop suite with the cable attached, then reconnect. A table below maps common connection states to checks. If the device cannot be detected, swap the cable, try another USB port, restart the companion, and verify that no other wallet software is running.
| Connection route | Preparation | On-device confirmation | Quick check |
|---|---|---|---|
| USB cable | Attach the supplied cable to a powered computer port. | Enter the PIN on the hardware screen. | Try another port or cable. |
| Bluetooth pairing | Charge the device and enable Bluetooth on the phone. | Compare the pairing code on both screens. | Keep the phone within a few feet. |
Install the Correct Coin App on Your Ledger Device for the New Account
Install the blockchain-specific plugin that matches the asset you plan to manage before creating a new tracked holding in the companion suite.
Each chain demands separate signing logic.
Link the secure device, enter your PIN, open the companion suite, and go to the plugin management area. The software reads the secure element, lists available plugins, and installs one after you confirm the action on the device screen. Keep the link active until the progress bar completes; breaking the connection mid-install can leave the plugin incomplete.
A plugin is chain-specific, not always asset-specific. Some families use one plugin for many tokens, while others require a separate binary for each network. This matters because a token can show up in the companion suite before the corresponding plugin is present on the device; in that state, balance display may work, but signing will fail.
Storage on the secure element is limited, so install only plugins you actively use and remove unused ones from the same management area. Removal does not delete keys, recovery phrase, or tracked holdings; it frees space for another chain’s plugin. Reinstalling later restores signing capability as long as the same seed controls the addresses.
During installation, the device screen shows the plugin name and asks for confirmation. Verify that the name matches the network selected in the companion suite. Approve only if it matches; reject unexpected prompts. The suite fetches the plugin from the official distribution channel, so sideloading files from other sources breaks the trust path and can expose signed transactions to tampering.
If the plugin fails to install, check three things: the device has accepted your PIN, the cable or Bluetooth link is stable, and no other wallet software is holding the connection. Then restart the companion suite and retry. A plugin built for a different firmware branch may be rejected; update the device firmware through the official suite before repeating the attempt. Never enter your recovery phrase into any software, web page, or chat to fix an installation issue.
Once the correct plugin is installed and confirmed on the device screen, create the new tracked holding in the companion suite. The software derives the first receiving address from your seed, and the device displays that address for independent verification. Compare the address on the device with the one shown in the suite before using it. This step binds the tracked holding to a key held only by the secure element and ensures every outgoing transaction for that chain can be reviewed and approved physically on the device.
Open the Accounts Tab and Select Add Account in Ledger Live
Click the portfolio icon in the left rail, then press the plus control above the asset list; that is the fastest route to register a fresh asset record inside the companion software. If the rail is hidden on a narrow window, use the menu button first, then choose the portfolio label from the drawer.
The plus control appears only after the hardware wallet is connected and unlocked; when it is missing, reconnect the unit with the original cable, restart the companion program, and approve the connection prompt on the device screen. The software requests extended public keys from the secure element, so a locked or unresponsive unit cannot create a new entry.
Label every profile entry with a clear, unique tag.
After pressing the plus symbol, choose the coin or token family from the search field; the companion tool proposes a derivation path and a label. Confirm the creation on the hardware wallet’s screen with the physical buttons. The derived public address is then stored in the local database, while the private material remains inside the chip. To verify the result, open the newly created entry, choose receive, and compare the displayed address with the one shown on the device; a match proves the correct key pair is in use.
If several entries are needed, repeat the plus action for each asset; the software keeps separate derivation paths and balances, so mixing networks inside one record is impossible. Remove unused records only after checking that no funds remain, and keep the recovery phrase offline. For supported assets and derivation rules, consult the manufacturer’s official support pages.
Choose the Cryptocurrency and Network for the Account You Want to Add
Match the network to the chain the sender will use, and install the corresponding coin module on the hardware signer first. Both conditions carry weight: without the on-device module the companion software cannot derive a receiving string for that chain, and a chain mismatch routes tokens to a destination your setup never scans.
Every record in the desktop or mobile client is bound to a single chain the moment it is created. A ticker alone does not define that chain, because one symbol often circulates on several of them, and the client presents each as a distinct option in the same selection field. Picking Ethereum mainnet for a token whose issuer also releases it on a sidechain or rollup yields a perfectly well-formed receiving string that belongs to the wrong network, and value sent there stays outside the standard interface, since the keys behind it control a record the client refuses to display. The device derives the public receiving string from the seed kept inside its secure element and renders it on its own screen; compare that string with the one handed to the sender before anything leaves their custody. Derivation paths differ per chain, so one seed produces entirely unrelated strings across networks – which is exactly why the chain chosen during creation cannot be edited afterwards for that existing record.
Run through these checks before approving anything:
- Read the chain named on the sender’s withdrawal form and mirror it precisely in the selection field.
- Install the device module for that chain beforehand; onboard storage is finite, so delete unused modules when an installation refuses to fit.
- Create a distinct record for each chain where the same ticker is held; balances stay per chain and are never merged into one figure.
- Verify the first and last characters of the receiving string against the hardware screen reading, not against a screenshot or clipboard copy.
Never route a token over a chain that differs from the one named in its record.
The catalog of supported tickers and chains lives on the vendor’s official pages and in its support documentation, so confirm availability there rather than assuming the field will offer a given network. If a chain is absent, nothing inside the client will conjure a working record for it; wrapped variants and third-party bridges carry their own chain choice no matter what the original token is called, and they hand custody of the underlying asset to someone else. For a hardware signer, the safe pattern stays constant: correct module on the device, correct chain in the selection field, and a receiving string confirmed on the screen.
Name the New Account and Confirm the Derivation Path Settings
Use a label that combines asset, network, and purpose, such as “BTC Native SegWit – Long-Term” or “ETH Main – Swaps,” and leave the default derivation path unchanged unless you are restoring from another wallet that used a custom path.
A vague name like “Crypto” becomes useless after three entries.
The derivation path is a numeric string that tells the hardware signer which branch of the seed tree to use. Bitcoin native SegWit typically follows m/84’/0’/0’/0/0, nested SegWit uses m/49’/0’/0’/0/0, legacy uses m/44’/0’/0’/0/0, and Ethereum uses m/44’/60’/0’/0/0. The companion software shows this path before creation; confirm it on the device screen. If you change the path, the same recovery phrase produces a different set of addresses, so a restore with the wrong path will show zero balances.
Tap confirm only after the signer displays the expected address.
For multiple entries, use a suffix that marks origin or use case, such as “BTC Native SegWit – KYC Exchange” or “ETH Main – DeFi,” but never include your name, email, or seed words. Renaming a label later is harmless; changing the derivation path after creation requires a new entry with the correct path. When you restore a recovery phrase, select the same coin and path to see the same funds. The companion software stores public keys and labels, while the signer keeps the private keys isolated.
A wrong path does not destroy coins; it hides them under a different branch. Recreate the entry with the original path, then verify the first receiving address against the signer’s screen. If you used a BIP39 passphrase, the same recovery phrase plus the same passphrase plus the same path is required to recover that branch. Advanced mode exposes change and address index fields; leave them at default unless a migration guide from another wallet specifies otherwise.
Most people need one native SegWit Bitcoin entry and one Ethereum entry; custom paths belong to users who move between multiple software wallets or run separate passphrase setups.
Q&A:
I added an Ethereum account but the balance is zero. What should I check?
Check the network and account type first. In Ledger Live, an Ethereum account shows ETH and ERC-20 tokens for that address. If you expected funds from another wallet, confirm that wallet used the same recovery phrase and the same address. Also check whether the account is hidden or whether you added a new empty account at a different index. Connect your Ledger device, unlock it, open the Ethereum app, and let Ledger Live sync. If the address still does not match, do not send funds to it. Compare the receive address in Ledger Live with the address used before.
Can I add two Bitcoin accounts in Ledger Live?
Yes. You can add several accounts for the same coin. Each one has its own addresses and account index. Pick Add account, choose Bitcoin, connect and unlock your device, open the Bitcoin app, then follow the prompts. Give each account a clear name, such as Bitcoin 1 and Bitcoin 2.
Does my Ledger device have to be connected while I add an account?
For a hardware-backed account, yes. Ledger Live asks your device to derive the account address and confirm that the address belongs to your wallet. Connect the device by USB or Bluetooth, unlock it with your PIN, and open the app for the coin you want. After the account is added, you can view its balance without the device. Sending crypto still requires the device so you can confirm the transaction on its screen.
Ledger Live says no accounts found or the coin app is not installed. How do I fix that?
If the coin app is missing, open My Ledger in Ledger Live. Connect and unlock your device, then install the app for that coin. Return to Accounts and try Add account again. If Ledger Live finds no accounts, confirm that your device firmware and Ledger Live are up to date. Try a different USB cable or port, and avoid USB hubs. For some coins, Ledger Live scans for accounts with activity. An empty new account may not appear as an existing account. If you restored your wallet and expected old funds, check that the recovery phrase is the same one used before. You may need to add accounts at the correct index. If you are unsure, stop and check your backup before moving funds.
Is it safe to rename or delete an account in Ledger Live?
Renaming is safe. The name is only a label inside Ledger Live, so it does not change your keys or the blockchain. Deleting an account removes it from the app view. Your funds remain on the blockchain. You can add the account again later with the same device and recovery phrase. If you delete it, write down the account name and index so you can find it again.
I connected my Ledger Nano X and opened Ledger Live, but I can’t find where to add a new Ethereum account. What should I click, and why does the account sometimes not show up after I add it?
In Ledger Live, go to the Accounts tab on the left sidebar. Click the Add account button near the top. Choose Ethereum from the list, then click Continue. Ledger Live will ask you to connect and open your Ledger device. Enter your PIN on the device, then open the Ethereum app on the device screen. After that, Ledger Live scans for accounts. If you already have an Ethereum account, it may show it; if you want another one, select the option to add a new account, give it a name, and confirm. If the new account does not appear, close Ledger Live, disconnect the device, reconnect it, and repeat. Also check that the Ethereum app on your Ledger is up to date through My Ledger, and that your device firmware is current. A common reason is that the Ethereum app was not open on the device when Ledger Live tried to scan. Another fix is Settings > Help > Clear cache, then reopen Ledger Live. That forces a fresh sync from the network, so your account list should update. If you use a passphrase, make sure the same passphrase is active, because accounts differ between passphrase sessions. If you still cannot see it, try a different USB cable or port, and avoid USB hubs. For Bluetooth on Nano X, pair the device again in Ledger Live settings.
