Ledger Live, the companion app for Ledger hardware wallets

When you plug in a device and open an account, Ledger Live is doing three separate jobs at once: talking to the hardware, talking to blockchain data services, and keeping a local model of your accounts in sync with both. Understanding those three layers makes almost every behavior in the app predictable, including the annoying ones.

The landing screen in Ledger Live is a portfolio dashboard: a total valuation in your chosen fiat currency, a chart across selectable time ranges, an allocation breakdown by asset, and the most recent operations across every account. It is a read-only view, so you can open Ledger Live and check on things without plugging in the hardware wallet at all.

Below that sits the account model. An account in Ledger Live is one derivation branch of one currency, and you can hold several per asset, which is the standard way to keep activity separated: a long-term Bitcoin account, a spending one, a business one. Each account can be renamed, starred, or hidden, and each has its own page with balance, sub-token list where relevant, staking status where relevant, and a full operation history.

Adding an account is a discovery process rather than a creation event. Ledger Live scans the derivation path for the selected currency, shows the accounts that already have history, and offers the next empty one. Nothing is created on-chain until it receives funds, so adding and removing accounts in Ledger Live is a bookkeeping action with no cost and no risk.

Operation history is enriched where the app can do it: token transfers appear against the parent account, NFTs appear in a dedicated gallery with their collections, and each operation links out to a block explorer for independent verification. Desktop builds of Ledger Live can export operation history to CSV, which is the usual starting point for tax or accounting work.

Settings deserve a look early rather than late. Currency and language, the theme, the price data preference, analytics and bug-report toggles, developer mode for testnets and less common derivations, and per-account resync controls all live there. Most of the behaviors people complain about in Ledger Live are settings they have not found yet.

Receiving starts with a request from Ledger Live to the device for a fresh address on the selected account. The app displays it, then asks the device to display the same address so you can compare them. That comparison is not ceremony. A compromised host could show you an attacker's address; the device, which derived the address itself, cannot be made to lie about it. Confirm on the device, then copy from Ledger Live.

Sending inverts the flow. You enter a recipient and an amount in Ledger Live, choose a fee level from the presets or set one manually where the network allows it, and the app assembles an unsigned transaction: inputs and change for UTXO chains, nonce and gas parameters for account-based chains. That unsigned payload goes to the device, the device renders it for review, you approve, and the signature comes back.

Only then does Ledger Live broadcast. Until you approve on the hardware, nothing has been committed and cancelling costs nothing. After broadcast the operation appears as pending in the account history and settles when the network confirms it, and Ledger Live tracks that state change on the next sync.

Fees are where most user error concentrates. Ledger Live estimates them from current network conditions, but the estimate is a suggestion; on congested networks a low setting can leave a transaction pending for a long time. On UTXO chains, sending an amount close to the full balance also interacts with change outputs, so the maximum-send helper in Ledger Live is safer than typing a number that leaves nothing for the fee.

Token transfers add one wrinkle worth knowing: the fee is always paid in the network's native asset. An account holding only tokens and no native coin cannot send anything, and Ledger Live will say so rather than let you build an unpayable transaction. Keep a small native balance in any account you intend to spend from.

Alongside the wallet functions, Ledger Live embeds services operated by third parties. Buying and selling route through regulated on-ramp and off-ramp partners, which handle payment, identity verification, and the fiat side of the trade. Ledger Live provides the destination address from your own device and shows the quote, but the commercial relationship on those trades is with the provider, not with the app.

Swaps work similarly: quotes come from integrated exchange partners, you pick one, and the resulting transaction is signed on your hardware wallet like any other. The important structural point is that funds move from your address to the provider and back to your address. Ledger Live does not take custody in the middle, but the provider does for the duration of the swap, and rates, spreads, and limits are theirs.

Staking is handled per network. On chains with native delegation, Ledger Live exposes it directly from the account page: choose a validator, delegate, watch rewards accrue, and claim or undelegate later with the usual on-device approval. On other networks the staking route runs through an integrated provider. Either way the underlying keys stay on the device, and Ledger Live shows lock-up and unbonding periods where the protocol imposes them.

The Discover section collects third-party applications built to run inside Ledger Live, from dApp front ends to portfolio and lending tools. They render in the app but cannot bypass the signing rule: every state-changing action still produces a transaction that the hardware wallet must display and you must approve. Treat anything you connect to through Ledger Live with the same skepticism you would apply in a browser, because the app is a window onto those services rather than an endorsement of them.

The device management area of Ledger Live, labeled My Ledger, is where the hardware itself is administered. It lists installed coin apps, offers a catalog to install more, reports free storage, shows firmware version, and runs the genuine check on demand. Everything here is device housekeeping rather than fund movement.

Firmware updates are delivered through Ledger Live and are worth taking seriously, since they carry security fixes and support for new features. The device verifies the signature on the firmware before installing it, so an update pushed by a tampered copy of the app would be rejected by the hardware. Keep the device connected and do not unplug mid-update; if an update is interrupted, the device enters a recovery state and Ledger Live can resume it.

App storage is a real constraint on the more compact devices, and the catalog in Ledger Live is deliberately blunt about it. When space runs out, uninstall apps you are not actively using. Your accounts remain listed in Ledger Live and your funds remain on-chain; you simply reinstall the app when you next need to sign for that network.

Two further options sit in this area on supported devices: a PIN change and a passphrase feature that derives an entirely separate set of accounts from the same recovery phrase plus a secret word. Passphrase wallets appear in Ledger Live as their own account set once the device is unlocked with that passphrase. They are powerful and unforgiving, because a forgotten passphrase is unrecoverable even with the 24 words.

Ledger Live ships as a desktop application for Windows, macOS, and Linux, and as a mobile app for iOS and Android. The feature sets are close but not identical, and the practical difference is usually the connection method rather than the interface.

On desktop, devices connect by cable, which works with every model. On mobile, Bluetooth-capable devices pair wirelessly, while a device without Bluetooth cannot be used with an iPhone or iPad at all. Android additionally supports a wired connection with the right cable. Choosing which build to install is therefore partly a hardware question.

You can run Ledger Live on several machines with the same device. Each installation keeps its own local account list unless you enable the optional account synchronization feature, which propagates the list of accounts, not any key material, between your own instances of Ledger Live.

Privacy in a wallet app is mostly a question of who sees your addresses. Because Ledger Live queries hosted indexers to build balances and history, those services observe requests tied to your extended public keys and, with them, the cluster of addresses that belongs to one account. That is the standard trade-off for light wallets, and it is a confidentiality question rather than a custody one; no amount of indexer data lets anyone spend.

Users who want to reduce that exposure have options. Routing traffic through a VPN or Tor moves the network-level metadata, and advanced users can point Ledger Live at their own Bitcoin infrastructure so that balance and history queries never leave their machine. Separating activity into distinct accounts also limits how much one query set reveals.

Locally, Ledger Live stores its account list, labels, cache, and preferences on your disk. Anyone with access to that machine can read your balances, which is a good reason to protect the operating system account itself and to lock Ledger Live with the app password option, which encrypts the local data at rest.

Telemetry is separate from all of the above and is controlled in settings. Analytics and crash reporting can be turned off, and doing so does not disable any wallet functionality. The account synchronization feature is likewise optional; when enabled it moves an encrypted account list between your own Ledger Live installations rather than exposing it to a server in readable form.

One habit matters more than any setting: install Ledger Live only from official distribution channels and verify updates through the app's own updater. Fake builds of Ledger Live circulate through search ads and app-store lookalikes, and their entire purpose is to present a convincing recovery-phrase prompt. The real application never has one.

The comparison worth making is not app against app but architecture against architecture. What differs is where the signing key lives and what has to be compromised for funds to move. On that axis, Ledger Live plus a hardware device sits in a different category from a browser extension or an exchange balance.

It is also perfectly reasonable to combine approaches. A hardware device can be connected to many third-party wallets, in which case that wallet replaces the Ledger Live interface while the device still enforces on-screen confirmation. The table below sets out how the arrangements differ on the points that decide risk.

Most support cases fall into a handful of patterns, and nearly all of them are connectivity or cache issues rather than anything to do with your funds. Before troubleshooting, remember the reassuring part: your assets depend on the recovery phrase and the chain, not on the state of the app.

When the device is not detected, start with the cable. Charge-only cables are the single most common cause, followed by USB hubs and front-panel ports. Then make sure the device is unlocked with the PIN, close any other wallet software that may be holding the connection, and restart Ledger Live. On Linux, device permission rules usually need to be installed once before the connection works at all.

When a balance looks wrong or history stops updating, the cache is the suspect. Use the per-account resync, and if that fails, clear the application cache in the settings and let Ledger Live rebuild from the chain. Compare the account against a block explorer to confirm whether the discrepancy is real or cosmetic; if the explorer agrees with the chain and disagrees with the app, it is a display problem.

When an account seems to be missing entirely, check whether you are on the right device or the right passphrase. A passphrase wallet shows a completely different account set, and reconnecting without it will make those accounts look gone. Also check the hidden-accounts setting and, for older wallets, whether the coin uses a derivation path that Ledger Live only offers in developer mode.

When a transaction stays pending, nothing in Ledger Live can accelerate a broadcast that the network has already received at a low fee; the network decides. Wait, or use the network's own mechanisms where they exist. If an operation shows as failed on chain, the fee is still spent, which is normal protocol behavior rather than a fault of the app.

Good habits with Ledger Live are few and boring, which is what makes them effective. The failures that cost people money are almost never cryptographic; they are procedural, and they repeat.

The rules below are the short version. Read them once, apply them every time, and treat any pressure to skip one, whether from a support chat, an urgent-sounding email, or an airdrop deadline, as the warning sign it is.