Ledger Live, the companion app for Ledger hardware wallets

What Ledger Live is and what it is not

Strictly speaking, Ledger Live is a client. It talks to two things: your hardware wallet over USB or Bluetooth, and blockchain data services over the internet. From the device it obtains extended public keys and, when you approve them, signatures. From the network it obtains transaction history, balances, fee estimates, and market prices. Everything you see in Ledger Live is assembled from those two sources, which is why Ledger Live can be reinstalled from scratch on a new machine and rebuild the same portfolio in a few minutes.

It is not a wallet in the sense of a place where coins live. There is no way to create a private key inside Ledger Live, no software-only account, and no cloud custody of funds. If you have no device connected, Ledger Live can show you a cached view of your accounts but cannot authorize a single outgoing transaction. That restriction is deliberate: it means a compromised laptop can lie to you on screen but cannot quietly drain an account, because the final confirmation happens on hardware you hold.

It is also not the only way to use a Ledger device. The same seed can be driven by various third-party wallets that support hardware signing. What Ledger Live adds is a single account list across many chains, a device manager for installing network apps and firmware, an integrated set of partner services, and a portfolio view that ties them together. People who manage assets on several blockchains usually find that consolidation is the main reason to stay in Ledger Live rather than juggling separate interfaces, and it is the reason Ledger Live tends to become the default window onto a multi-chain portfolio.

Finally, Ledger Live is not a marketplace where the app itself is your counterparty. Buying, selling, and swapping inside the app are handled by outside providers whose rates, fees, and identity checks are their own. Ledger Live presents their quotes, hands the resulting transaction to your device for approval, and records the result in your history.

How Ledger Live works under the hood

Accounts from extended public keys

A Ledger device stores one seed, from which an entire tree of keys is derived deterministically. When you add an account in Ledger Live, the app asks the device for the extended public key at a particular derivation path. That public key lets Ledger Live generate every receiving address for the account and watch the chain for activity, without ever being able to produce a signature. This is the standard hierarchical deterministic model used across the industry, described in general terms on the cryptocurrency wallet reference pages.

Because accounts are derived rather than created, adding them is repeatable. Reinstall Ledger Live on another computer, connect the same device, and Ledger Live will scan the same paths and rediscover the same accounts with the same balances. Nothing about that recovery depends on a backup file, an export, or an online profile, only on the device and the seed behind it.

The signing round trip

Sending value follows a fixed sequence. Ledger Live collects the inputs it needs from the network, such as unspent outputs for a Bitcoin transfer or the nonce and gas parameters for an EVM transfer. It builds an unsigned transaction and passes it to the network app running on the device. The device parses the payload, shows the amount, destination, network, and fee on its own screen, and waits. Only after you physically confirm does it return a signature, which Ledger Live then broadcasts. At no point does the unsigned or signed transaction give the computer access to the key that produced it.

This is where clear signing matters. When the device can decode what it is being asked to approve, it shows plain details you can check. When a payload is opaque, typically complex smart contract data, the device can only present raw information, and some apps require you to enable blind signing before proceeding. Treat that setting as a deliberate risk decision rather than a routine toggle, and prefer flows where Ledger Live and the device agree on human-readable details.

One more piece runs quietly in the background. When a device connects, Ledger Live performs a genuine check, an attestation that verifies the secure element holds a legitimate factory signature. It is a defense against tampered or counterfeit hardware bought through unofficial channels, and it is worth paying attention to if Ledger Live ever reports that the check failed.

A tour of the Ledger Live interface

The layout is consistent across desktop and mobile, with the same main destinations arranged differently for screen size. Understanding what each area of Ledger Live is responsible for makes the app much faster to work with, because most confusion comes from looking for a function in the wrong place.

Settings deserve a closer look than most people give them. There you choose the display currency, turn on a password lock that encrypts the local Ledger Live data, control analytics and crash reporting, switch the app language, and reach maintenance tools. Developer mode reveals testnets and less common derivation paths, which is useful when you are recovering into Ledger Live an account created in another wallet.

One maintenance tool is worth knowing before you ever need it. Clearing the cache tells Ledger Live to discard its local copy of transaction history and rebuild it from the network. It resolves a surprising share of display glitches, takes a few minutes on a large portfolio, and cannot affect your funds, because the cache holds nothing but a mirror of public data.

Where Ledger Live runs and how it connects

Ledger Live is distributed as a desktop application for 64-bit Windows, macOS, and Linux, and as a mobile application for iOS and Android. The desktop and mobile builds share the same account engine, so an account added on one behaves identically on the other. What differs is how the device attaches and which advanced tools Ledger Live exposes on each platform.

Desktop connections are made with a USB data cable. Devices with Bluetooth can also pair with the mobile app wirelessly, which is how most people use Ledger Live on a phone. On Android, a USB-C connection works as well; on iOS, Bluetooth is the practical route because the platform does not expose the same USB access to the app.

Device storage is the other practical constraint. Each blockchain you use needs its own small app installed on the hardware, and older models hold far fewer of them than current ones. Ledger Live shows remaining capacity in the device manager and will tell you when an install does not fit, at which point you remove an app you are not using and reinstall it later without any risk to balances.

Receiving, sending, and controlling fees

To receive, you select an account and open the receive flow. Ledger Live displays an address and, critically, asks the device to display the same address on its own screen. Comparing the two is the entire point: malware that swaps an address in the app window cannot change what the hardware shows. Confirm on the device, then copy or scan. For Bitcoin-style chains, Ledger Live hands out a fresh address each time for privacy, while old addresses keep working.

Sending follows the same discipline in reverse. You enter a destination and amount in Ledger Live, choose a fee level, and then read the summary on the device before approving. Check the amount, the network, and at minimum the first and last characters of the destination. On EVM chains, also check the token being sent, since a contract interaction can look similar to a plain transfer at a glance.

Fee handling is chain-specific. For Bitcoin, Ledger Live offers ranked speed options and a custom rate in satoshis per virtual byte, with the estimate updating as network demand changes. For Ethereum and other EVM networks, Ledger Live shows a standard estimate plus an advanced mode where you set the maximum base fee, priority fee, and gas limit. Fees always go to network validators or miners, never to the app.

On desktop, Bitcoin accounts get coin control. Instead of letting the app pick inputs, you select which unspent outputs to spend, which matters if you care about avoiding linkage between coins or want to consolidate dust when fees are low. It is an advanced feature, and Ledger Live keeps it behind an expandable section of the send screen so it stays out of the way of routine transfers.

Occasionally a transaction sits pending because it was broadcast with a fee that the network no longer accepts quickly. On some networks, Ledger Live can rebroadcast a replacement to speed the transfer up or cancel it, which again requires a fresh device confirmation. Where replacement is not possible, the only options are patience or, on chains that eventually drop stale transactions, waiting for the transaction to clear from the mempool.

Buying, selling, and swapping through providers

The buy and sell screens in Ledger Live connect you to outside on-ramp and off-ramp companies. They handle payment processing and identity verification under their own terms, and availability depends on your country and payment method. Ledger Live supplies the destination address from your own account, so purchased coins land directly on keys your device controls rather than sitting in a provider balance.

Swapping works similarly. Ledger Live requests quotes from integrated exchange services, shows the rate and estimated fees, and lets you pick. Some are centralized services that take custody for the duration of the trade, others route through decentralized liquidity. The distinction is worth reading before confirming, because it determines who holds your funds mid-swap and what happens if a quote expires.

Every leg still requires hardware approval. A token swap on an EVM chain may need two device confirmations, one to grant the contract an allowance and one for the swap itself. Ledger Live shows both steps, and it is good practice to approve only the amount you are trading rather than an unlimited allowance when the interface gives you that choice.

Costs in these flows come from three places: the provider's spread, any service fee it charges, and the network fee. Ledger Live displays the expected outcome before you commit, and the completed operation appears in your account history like any other. Desktop users can export operation history from Ledger Live to CSV, which is the usual starting point for bookkeeping or tax software.

Staking and rewards inside Ledger Live

Several proof-of-stake networks let you delegate directly from Ledger Live. On chains such as Cosmos, Solana, Tezos, and Polkadot, delegation is a signed transaction: you choose a validator, approve on the device, and your coins remain in your own account while contributing to network security. Ledger Live then tracks the position and shows accrued rewards, which you claim with another signed transaction.

Ethereum works differently, because solo staking requires a large deposit and infrastructure. Ledger Live routes Ethereum staking through integrated providers, which means you are interacting with smart contracts and accepting the terms and risks of that provider. Read what you are entering: liquid staking tokens, pooled deposits, and validator services all behave differently on the way out.

Two mechanics catch people out. First, unbonding periods: many networks lock withdrawn stake for days before it becomes spendable, and Ledger Live will show the pending status but cannot shorten the wait. Second, validator quality: a validator that misbehaves can be penalized, and delegated funds share that penalty on some chains. Spreading delegations and checking commission rates before confirming is ordinary hygiene here.

NFTs and Web3 connections in Ledger Live

Ledger Live includes an NFT gallery for Ethereum and Polygon accounts, covering the common ERC-721 and ERC-1155 standards. Tokens appear automatically when your account holds them, with images and metadata fetched from third-party sources. You can view details, send an NFT to another address with device confirmation, and hide unwanted items, which is useful because unsolicited spam tokens are common on public chains.

For applications that live outside the app, Ledger Live supports WalletConnect sessions. You scan or paste a connection link, choose which account to expose, and the external application can then request signatures that are relayed to your device. The account is exposed as a read-only address until you approve something; nothing is authorized silently.

This is the area where blind signing risk concentrates. A malicious contract call can request an unlimited token allowance or a transfer disguised as an unrelated action, and the device can only warn you about what it can decode. Prefer applications whose transactions display readable details, revoke allowances you no longer need, and disconnect sessions in Ledger Live when you have finished using them.

Managing device apps and firmware from Ledger Live

Each blockchain needs a small application installed on the hardware wallet so the device can parse and sign that chain's transactions. Ledger Live installs, updates, and removes these from the device manager. Removing one deletes no keys and loses no funds, because addresses are derived from the seed rather than stored in the app; reinstalling restores access immediately, and this is the normal way to free space on devices with limited storage.

Firmware updates are also delivered through Ledger Live. The update is cryptographically signed, the device verifies it before installing, and you confirm the process on the hardware. Keep the device connected until the update finishes, expect to re-enter your PIN afterward, and be prepared to reinstall network apps, which Ledger Live prompts you to do automatically.

A common worry is whether an update can expose the seed. It cannot be read out by the app: firmware runs inside the secure element and the recovery phrase never leaves it. Even so, back up your recovery phrase before starting any update, because the safe recovery path from a device problem always runs through that backup and never through Ledger Live.

What data Ledger Live handles

Your account list, custom names, settings, and cached history live in a local database on the machine running the app. There is no login, no username, and no password stored on a server for basic use of Ledger Live. Turning on the password lock encrypts that local data so someone with access to your unlocked computer cannot casually browse your holdings.

To display balances, however, the app has to ask someone about the chain. By default Ledger Live queries indexing infrastructure operated by Ledger, which means those services can associate your IP address with the extended public keys they are asked about. This is normal for light wallets and is the standard tradeoff for not running a full node, but it is a real privacy consideration and worth stating plainly.

Users who want to remove that dependency for Bitcoin can point the desktop version of Ledger Live at their own full node, so balance and history queries stay inside their own infrastructure. Separately, analytics and crash reporting are switchable in settings, and the Ledger Live client codebase is published publicly, which lets independent developers inspect how the app builds requests and handles data.

Two optional services sit alongside the basics. An encrypted synchronization feature can keep your account list consistent across your own installations of Ledger Live without transmitting keys, and a separately subscribed identity-based recovery service exists for people who want a backup path for their seed. Both are opt-in, both are off unless you enable them, and neither is required to use Ledger Live for everyday transfers.

Using Ledger Live safely

The rule that prevents most losses is short: Ledger Live will never ask for your 24-word recovery phrase, and neither will a firmware update, a support agent, or a legitimate airdrop. Any screen, email, chat message, or phone call that requests those words is an attack, without exception. The phrase belongs on paper or metal in your own custody and should never be typed into a computer or phone.

Install only from official distribution channels and be skeptical of search results and sponsored links, which phishing operators buy routinely. On desktop, the installer is code-signed, and Linux users can verify the AppImage against the published checksum. If an app claiming to be Ledger Live asks for anything unusual during setup, stop and start over from a known-good source.

Then trust the device screen over the app window. Verify receiving addresses on hardware, read the send summary rather than clicking through it, and keep blind signing off unless a specific transaction genuinely requires it. Ledger Live is designed on the assumption that the host computer might be compromised, and that assumption only protects you if you actually read what the device shows.

Ledger Live compared with other ways to hold crypto

The table below sets the app next to two common alternatives: a third-party software wallet that connects to the same hardware, and a purely software hot wallet with keys on the computer or phone. The comparison is about the security model and the day-to-day workflow, not about which brand is best.

Many people run a hybrid setup, and there is nothing wrong with that. Ledger Live handles portfolio tracking, firmware, transfers, and staking, while a specialist wallet handles a particular chain or application, with the same device signing in both. The one task that stays with Ledger Live is device maintenance, since firmware and network apps are installed from there.

How to get started with Ledger Live

Setting up takes about twenty minutes, most of which is writing down and checking the recovery phrase. Do that part unhurried and alone, because it is the one step that cannot be redone later if it goes wrong.

1. Step 01 / Install

   Download Ledger Live from the official source for your operating system and install it. On Linux, add the device access rules so the hardware is detected without root privileges.

2. Step 02 / Set up the device

   Connect the hardware wallet and follow the onboarding in Ledger Live. Choose a PIN on the device, generate a new recovery phrase, write it on the supplied sheet, and confirm it. Never photograph it or store it in a password manager.

3. Step 03 / Verify and install apps

   Let Ledger Live run the genuine check, then open the device manager in Ledger Live and install the network apps for the chains you plan to use.

4. Step 04 / Add accounts

   Add one account per asset. Ledger Live scans the derivation paths, imports any existing balances, and lets you rename accounts so the portfolio stays readable as it grows.

5. Step 05 / Test with a small amount

   Send a small transfer in, confirm it appears in Ledger Live, then send a small amount back out and approve it on the device. Once the round trip works, move the rest.

Two optional finishing touches: enable the password lock in Ledger Live so local data is encrypted, and set the display currency you actually think in, since every fiat figure in the app derives from that setting.

Common problems and how to fix them

Device not detected is the most frequent complaint, and the cause is usually mundane. Many USB cables carry power but no data, so try the cable that came with the device and a different port, ideally directly on the machine rather than through a hub. Close any other application that might be holding the device, such as a browser wallet or a second copy of Ledger Live, then unlock the device and open the relevant network app before retrying.

Bluetooth pairing problems on mobile usually clear by removing the pairing in the phone's system settings, restarting Bluetooth, and pairing again from within Ledger Live. If the phone finds the device but Ledger Live does not, check that location and nearby-device permissions are granted, since some Android versions require them for Bluetooth scanning.

A balance showing as zero after reinstalling almost always means the account has not been added yet, or was added on a different address type. Bitcoin in particular can live on legacy, SegWit, native SegWit, or Taproot paths, and each is a separate account. Re-run the add-account flow in Ledger Live, check each address type, and enable developer mode if you are recovering something created in another wallet with an unusual derivation path.

If history looks stale, prices fail to load, or an account is stuck synchronizing, clear the cache from settings and let Ledger Live rebuild from the network. Should a firmware update be interrupted, the device typically restarts in a recovery state and Ledger Live offers to resume the update; your funds stay recoverable from the phrase regardless of how that repair goes.

Frequently asked questions