Add Tokens to Ledger Live via Accounts, Coin Apps and Receiving
How to Add Tokens to Ledger Live Wallet Guide begins with a direct check: install the asset-specific app on the hardware signer, connect and unlock the device, open the companion application, select Accounts, choose the relevant network, then confirm the new account on the device screen. A coin or digital asset appears only when the device firmware, the asset app, and the companion software all recognize the same standard and account type. If the asset lacks a compatible device app or account scheme, the interface cannot display it, though an external address may still receive it.
The mechanism is account derivation, not a text import. The protected chip generates and stores the seed; the companion program derives addresses from that seed and prepares unsigned transactions. The hardware signer displays the destination, amount, network, and fee data; the user approves or rejects physically. For smart-contract assets, the parent network account must exist first, and the asset contract must be recognized by the device app. Verification happens by comparing the address and contract details on the signer screen against an independent source before approving any receive or send action.
Keep the 24-word recovery phrase offline and enter it only on the device itself. No website, chat, email, phone call, or remote helper needs it; anyone requesting it is hostile. Download the companion software only from the manufacturer’s official domain, and confirm the domain character by character. Supported networks, account rules, and setup details change, so use the official support pages for the compatibility matrix rather than third-party posts.
Check Which Tokens Ledger Live Supports Before Adding
Verify asset availability inside the companion application’s catalog before creating any account.
Each supported cryptocurrency requires a dedicated app installed on the hardware signer; the companion application lists only networks for which such an app exists. If the catalog lacks a coin, the secure element cannot derive addresses or approve transfers for it, and third-party workarounds do not change that limitation.
Use the official vendor’s supported assets page as the primary source, then cross-check the in-app catalog. The application’s list is updated with firmware and device app changes, so an asset absent from an older release may appear after an update. For EVM-compatible networks, confirm whether support comes through a separate device app or a shared account type; do not assume that because one chain works, every fork or layer-two network will also work.
Creating an account for an unsupported asset can produce a watch-only entry with no signing path, or a third-party service may custody the funds instead of the hardware signer. Both outcomes defeat self-custody. Check that the asset’s network matches the app you installed; sending a coin on the wrong chain can result in permanent loss.
Some assets need a specific account model: UTXO chains use separate account types from account-based networks, and certain staking or smart-contract operations require an accompanying app on the device. The companion application may display a balance without offering send, receive, or staking controls if the required device app is missing. Verify every action you need–viewing, receiving, sending, staking, or interacting with contracts–before moving value into that account.
If the asset is absent from both the official catalog and the hardware signer’s app directory, do not create an account.
Update Ledger Live and Ledger Device Firmware for New Token Support
Download the newest companion application release, then connect the hardware signer and apply any available firmware refresh before expecting a newly listed cryptocurrency to appear.
Why both components matter: the application handles account derivation and balance display, while the device’s embedded software contains the cryptographic rules for each asset’s signing scheme. A mismatch between the two leaves the asset visible but unsignable.
Perform the application upgrade first via the official desktop or mobile client. Then attach the secure element device, enter your PIN, and allow the firmware update to write over USB or Bluetooth. Do not disconnect the cable or close the client during this write phase. After the device restarts, reopen the client and use its asset management area to reinstall any coin-specific programs. For a new cryptocurrency to become usable, the embedded software must include the correct elliptic curve and transaction parser, and the client must know how to query that asset’s blockchain. Updating only one side yields a broken state.
Skipping either refresh produces a partially compatible setup.
After both upgrades, verify the firmware revision on the device screen by navigating to its settings menu. In the companion client, open the About section to read the software build identifier. Then attempt to create a fresh account for the target asset. Successful account creation proves that the device recognizes the asset’s derivation path and that the client can fetch its balance. If creation fails, reapply the firmware update using a different USB cable or port. Never use third-party flashing utilities; they can corrupt the secure element’s memory. Also check that your operating system has the latest drivers for USB or Bluetooth communication.
Understand that firmware and application updates are released independently. A new asset may be supported by the client’s interface before the device’s embedded software can sign for it. Conversely, the device might gain signing capability for an asset that the client does not yet list. Cross-check both official release notes. The manufacturer publishes separate change logs for the desktop client, the mobile client, and the device firmware. Read all three. If you use both desktop and mobile versions of the companion software, update both. The mobile client may receive updates through an app store, while the desktop client requires a manual download from the manufacturer’s website. A device paired with an outdated mobile client will fail to broadcast transactions even if the firmware is current. Also note that the device’s secure element cannot be downgraded after a firmware upgrade. Therefore, installing a firmware refresh for a beta asset can prevent returning to a prior revision. Only apply firmware updates from the official source. For any discrepancy, consult the manufacturer’s support documentation.
| Aspect | Companion software update | Device firmware update |
|---|---|---|
| Primary role | Enables account discovery and interface for new assets | Provides cryptographic signing rules for new asset protocols |
| Typical trigger | Manual check in the application’s settings | Prompt upon connecting the device to the application |
| Verification method | Read the build identifier in the About section | View the firmware revision on the device screen during startup |
| Consequence of neglect | New asset may not appear in the account list | Device cannot sign transactions for the unrecognized asset |
| Update medium | Download from the manufacturer’s official website | Delivered over USB or Bluetooth from the companion application |
Install the Correct Coin App for the Token’s Blockchain
Install the blockchain application matching the asset’s native network before you attempt any transfer or balance check.
Each blockchain requires its own dedicated program on the hardware device. For an ERC-20 unit, you need the Ethereum app; for a BEP-20 unit, the BNB Smart Chain app.
Open the companion software, connect your physical unit, and navigate to the app manager. Locate the exact network name, then install that program. After installation, create an account for that network so the asset can appear in your portfolio view.
Installing an unrelated app will leave your balance invisible. Many networks share a single program across all compatible digital units–the Ethereum app handles both ETH and its derivative assets. Always verify the network name through official support pages. Never install a program from an untrusted source.
Once installed, the device screen displays the program name when opened. The companion software only shows assets for which the matching program and an account exist. If an asset does not appear, confirm the program is present and the account is created. Removing a program does not erase your keys or funds–they remain on the distributed ledger. Reinstalling the program restores access. For any discrepancy, consult the official documentation; never share your recovery phrase.
Add an Account for a Supported Token in Ledger Live
Create the account through the desktop or mobile companion only after the asset’s network app is installed on the hardware signer and the device screen shows the derived address you expect.
Install the network app first; the companion cannot manage an asset whose network app is absent from the secure element. Open the account manager area, choose the correct asset and network, then let the software scan the device for existing addresses. If the scan finds a balance-bearing address, register it instead of creating a fresh one, because the derivation path determines which public address is used.
Name the account with a clear label that identifies the network and purpose, such as savings or daily use; the label is local metadata and does not change keys or addresses.
Match the address on the signer display with the address shown in the app before naming the account.
Confirm synchronization only after the app shows a balance and transaction history consistent with the address on the signer. A fresh account may remain empty until the network broadcasts incoming activity; do not send funds to an address copied from chat, email, or a web page.
For assets that require a memo or destination tag, the account itself stays the same, but every incoming transfer must include the correct tag or memo from the sending side; the signer screen will not repair a missing tag. Verify the network’s requirements in the official support documentation before sharing the address with a sender.
If the asset does not appear in the account manager, update the companion software and the device firmware through official channels, then reinstall the relevant network app; unsupported assets cannot be forced into the interface. Never enter the 24-word recovery phrase into a computer, browser, chat, or pop-up, and treat any request for that phrase as fraud. Check the public address on the signer every time you open the account; a mismatch between the device display and the companion view indicates a compromised host or a wrong derivation path.
For large balances, test with a small transfer first, verify receipt on the signer, then move the remainder; keep the desktop or mobile release current and use only the official download page.
Receive Tokens to a Ledger Live Account Address
Generate a fresh receive address in the companion program, then verify every character on the hardware signer’s display before sharing it with the sender. Copy only after that check passes. This single habit blocks clipboard malware and address-swapping attacks that target desktop and mobile users.
Open the account tied to the asset you expect, choose the receive action, and let the app request a public address from the device. The signer derives that address from its protected keys; the private half never leaves the secure chip. The screen shows the same string that appears in the app, plus a QR code for scanning. If the asset uses a network identifier, select the correct one before generating the address. Check the official support pages for current network-specific labels and any memo requirement.
Verify the address on the hardware signer
Compare the full address, not just the first and last four characters. Scroll through the entire string on the signer’s screen using its physical buttons. If a single digit or letter differs, cancel the request and generate a new address. Then recheck. This step matters most when you paste an address into a chat, email, or exchange withdrawal form.
Network and memo requirements
Match the network chosen by the sender to the network of your account. A transfer broadcast on a different chain can become unrecoverable, because the receiving address may not exist on that chain or the funds may land in an unspendable state. For assets that use destination tags, memos, or payment IDs, include the exact value shown in the app. Omitting it can delay or lose the deposit. Ask the sender to confirm the network and memo before they broadcast. If you are unsure, send a small test amount first, then wait for confirmation before sending the remainder.
Treat the receive address as public data. It is safe to share with anyone who needs to pay you. Never disclose the 24-word recovery phrase, the private key, or a signed transaction. No legitimate service needs those items to route an incoming transfer. Anyone who asks for them is attempting theft.
After the sender broadcasts, the companion app displays the transfer as pending and later as confirmed once it syncs with the network. Receiving does not require the signer to be connected or powered on. The device only needs to be available when you generate or verify the address. Some chains require several confirmations before the balance becomes spendable; the app reflects that status automatically. A public block explorer can provide an independent view of the same transaction.
If the expected asset does not appear, confirm that the correct network app is installed on the signer and that the account is synced. Reopen the companion program and reconnect the device. Check that the address shown in the app still matches the one on the signer’s display. When a mismatch persists, stop and contact the manufacturer’s official support channel. Avoid lookalike domains and never enter your recovery phrase into a browser pop-up. For current fixes, consult the official support site rather than third-party videos or chat groups.
Add ERC-20 Tokens That Do Not Appear Automatically
Input the contract address into the custom asset field of the Ethereum account within the companion application. This action forces the software to query the blockchain for that specific ERC-20 standard.
Not every ERC-20 unit appears by default because the companion program relies on a curated registry. Developers or liquidity providers must submit their contract address for inclusion. Assets outside that list remain invisible until you supply the missing hexadecimal string. The hardware signer itself holds no asset directory; it only signs for the Ethereum address.
Open the accounts view, select the Ethereum account, then choose the option to manage assets. Locate the field labeled for custom contract addresses. Paste the 42-character hexadecimal string. Confirm the operation. The companion application will retrieve the symbol and decimal places from the blockchain. A new sub-account appears under the same Ethereum address. The private keys remain on the secure element; the application only reads public data. No transaction confirmation on the physical device is required because this changes only the display, not the blockchain state. If you later receive that ERC-20 unit, it will be visible in the sub-account. Always verify the contract address against a trusted block explorer before pasting. A single wrong character creates a fake asset that mimics a real one.
Never trust a contract address from a social media message or email. Obtain it only from the official project website or a verified block explorer.
Qualitative differences between automatic and manual asset display
| Attribute | Automatic display | Manual inclusion |
|---|---|---|
| Source of contract list | Curated by the software vendor | Supplied by the user |
| Risk of wrong contract | Minimal | Depends on user verification |
| Physical device confirmation | Not required | Not required |
| Sub-account creation | Automatic for listed units | User-triggered |
After the sub-account exists, sending that ERC-20 unit to your Ethereum address makes the balance visible in the companion application. The physical device screen will show the transaction details during any transfer, as it does for any other Ethereum operation. Removing a manually included asset from the display does not delete the underlying data; it only hides the sub-account. Repeating the contract address restores visibility. Keep a record of each custom address in a secure offline note.
Q&A:
I have an Ethereum account in Ledger Live. How do I add an ERC-20 token so I can see its balance?
Open Ledger Live and go to Accounts. Select your Ethereum account. Look for the Add token button on desktop or the + icon on mobile. Type the token name or ticker. Pick the correct token from the list and confirm. Ledger Live will create a token entry under that Ethereum account. You do not need a new address. The token balance appears after the app syncs with the network. Make sure the Ethereum app is installed on your Ledger device and the device is connected if Ledger Live asks for verification.
My token is not in the search list. Can I add a custom token by pasting its contract address?
Ledger Live does not let you add any token by contract address. It only shows tokens from its supported list. If your token is missing, use a wallet that supports custom tokens, such as MetaMask, and connect your Ledger device to it. That way you can still manage the token with the same hardware wallet. You can also check if Ledger Live supports the token on another network, because some tokens exist on several chains.
Do I need to create a separate Ledger Live account for every token I want to track?
No. For tokens on the same network, you use the same account as the native coin. For example, all ERC-20 tokens on Ethereum share your Ethereum account address. You add each token as a sub-entry under that account. You only need separate accounts for different networks or different native coins. This keeps your setup simple and avoids extra addresses.
Will adding a token to Ledger Live cost a fee or move my coins?
No. Adding a token only changes what Ledger Live displays. It does not send a transaction to the blockchain. Your tokens stay at the same address. No gas fee is charged. You will only pay a network fee when you send the token or move it. If you see a fee prompt while adding, stop and check that you are not on a swap or send screen.
I added a token but the balance shows zero. What should I check first?
First confirm you added the token to the correct network account. An ERC-20 token on Ethereum will not show under a Polygon or BNB Chain account. Next, check the receiving address in a block explorer. Make sure the tokens were sent to the same address as your native coin account. Also verify the token contract matches the one you added. If the token is supported but still shows zero, update Ledger Live and refresh the account. If it remains zero, the tokens may be on a different address or network.
I hold USDC on Ethereum and want to see it in Ledger Live. Do I need a separate USDC account, or can I just send it to my Ethereum address?
Add an Ethereum account in Ledger Live first. Then use Accounts > Add account, search for USDC, and add the USDC token account. The receiving address for that token account is the same as your Ethereum account address. You can send USDC to that address from an exchange or another wallet. Make sure the sender uses the Ethereum network (ERC-20), not another chain. You will also need a small amount of ETH in the Ethereum account to pay network fees when you move USDC later. If you only see ETH and no USDC after adding the token account, check that Ledger Live is updated and that the USDC contract is the one supported by Ledger Live.
My token does not appear in Ledger Live’s Add account list. It is on BNB Chain and I also have some on Polygon. How can I manage it with my Ledger device?
Ledger Live shows tokens only for networks and assets it supports. If your token is on BNB Chain or Polygon and the list does not show it, you can use a wallet that works with those networks and your Ledger device. For EVM networks, MetaMask is a common choice. Install MetaMask, connect your Ledger, select the BNB Chain or Polygon network, then add the token with its contract address. Always copy the contract address from the official project page or a trusted explorer. A wrong address can create a fake token entry and may lead to loss if you trade it. Keep your Ledger device firmware and the Ledger Live app up to date. If the token later becomes supported in Ledger Live, you can add it there as a token account under the matching parent network.
