Using a Hardware Wallet with MetaMask

Symptom	First action	Planning use
MetaMask does not detect the Ledger at all	Plug the device in by USB (not Bluetooth), unlock it and open the Ethereum app	Check the hardware state before changing any software.
Ledger Live is open while connecting	Close the Ledger Live app	Do this first, because it costs nothing.
Connection worked before and now fails	Clear the browser cache	A stale cache can break an existing connection.
Hardware option fails in Chrome or Firefox	Use MetaMask’s Ledger Live-based connection	The older U2F method ended in current browsers.
Expected account is missing from the list	Page through accounts on both derivation paths	The account may sit on the other path.
Device asks for blind signing	Enable it on the device only if the task needs it	Leave it off for ordinary use.
Connection fails after a long gap	Update firmware, browser and the Ethereum app	Run all three updates before a retry.

Fixes follow MetaMask’s hardware wallet connection guide.

To connect Ledger to MetaMask, plug the unlocked device in by USB, open the Ethereum app, close Ledger Live, then add the Ledger from the MetaMask account menu.

Most failed pairings come from the device state rather than from MetaMask itself, so the order below starts with the hardware. Readers still choosing a device can compare the best wallet for ethereum based coins before buying.

What to prepare before connecting

A Ledger pairs with MetaMask through a handful of conditions, and each one is a common point of failure. MetaMask’s support team lists them as a checklist: the latest firmware on the device, an up-to-date browser, an up-to-date Ethereum app, and the Ledger Live app closed.

Cable connection. The device must be plugged in via USB, not Bluetooth. A wireless pairing will not satisfy MetaMask, so use a data-capable cable and a free port.
Unlocked device. Enter the PIN so the Ledger is unlocked and sitting inside the Ethereum app. A device on its home screen or lock screen looks disconnected to the browser.
Current Ethereum app. MetaMask says to update the Ethereum app from Ledger Live, in the Manager section, before retrying a failed connection.
EVM accounts. Only EVM-based Ledger accounts can be connected, so the account you want must belong to that family.

Anyone weighing a Ledger against another brand can read ledger vs trezor, since MetaMask documents both on the same support page. Once the checklist is satisfied, the connection itself takes only a few clicks.

Connecting the Ledger to MetaMask

The connection starts from the account menu inside MetaMask and ends with an account picker. The process is the same whether the wallet is new or already holds software accounts.

Plug in the Ledger by USB, unlock it and open the Ethereum app.
Make sure Ledger Live is closed.
In MetaMask, open the account dropdown menu and choose the option to add a hardware wallet.
Choose Ledger as the hardware wallet type, then click Continue.
Click Connect and approve the request on the device if it prompts you.
Select the account to add from the list MetaMask shows.

MetaMask’s page words the menu entry as “Add account or hardware wallet”, so look for that label if the menu differs slightly from the steps above.

Which browsers and connection methods work

MetaMask states that the U2F API behind its earlier Ledger support ended as of Chrome version 91 and Firefox version 114.0. In its place, MetaMask implemented Ledger Live-based support, which lets people keep connecting a Ledger from the desktop environment.

For that route, MetaMask asks that the Ledger Live app is installed with your Ledger accounts visible. This does not conflict with the closed-app rule above: install and set up Ledger Live first, then close it before pressing Connect in MetaMask.

Illustrative stock photo of stacked USB Type-A ports. MetaMask’s guidance calls for a cable connection, so pick a port on the computer itself.

When MetaMask will not connect to the Ledger

When a Ledger will not connect to MetaMask, work through the cheapest checks first. Each symptom below maps to one change, and the order runs from physical to software.

An outlined graphic, not a real MetaMask screen. It stands in for the moment of choosing one entry from the account list.

Nothing is detected

Start with the device. Confirm the Ledger is on a USB connection, unlocked, and showing the Ethereum app, because MetaMask names all three as requirements. If Ledger Live is running in the background, quit it, since MetaMask lists the Ledger Live app closed as a precondition. This also answers whether Ledger Live must be shut first: yes, for the connection to go through.

An illustrative paper ledger, not a Ledger Live or MetaMask screen. Page through the account list in the same way, on each derivation path.

It worked before and now fails

MetaMask says a Ledger’s connection can be broken by the browser cache. Clear the cache, reload the extension page and repeat the connect steps. This suits the case where nothing on the device has changed but the link has stopped working.

The Ledger Live link will not start

If the symptom appears while you pair through Ledger Live, check that the app is installed and that your accounts are visible inside it. A Ledger Live with no visible accounts leaves MetaMask with nothing to read.

Everything looks right but it still fails

Move to updates. MetaMask recommends the most up-to-date firmware on the device, an up-to-date browser, and an updated Ethereum app installed through Ledger Live’s Manager. Update in that order, reconnect after each change and stop once it works, so you know which change fixed it.

Blind signing on the Ledger

Blind signing is a setting on the Ledger itself, and MetaMask’s guidance is to have it enabled on the device only if what you are doing needs it. That conditional wording matters: it is not a default to switch on during setup.

A practical approach is to leave the setting off for ordinary use and revisit it when the device screen asks for it during an action. Because the setting lives in the Ethereum app on the Ledger, MetaMask cannot change it for you, and a signing request that stalls may simply be waiting on that option.

A generic handheld device with a small display and buttons, shown for illustration only. The real blind signing option appears on the Ledger’s own screen.

Adding and finding more hardware accounts

More accounts come from the same menu: open the account dropdown, add a hardware wallet again, choose Ledger and select another entry from the list. Each account you select appears in MetaMask alongside the others.

If the account you expect is missing, the issue is usually where MetaMask is looking. MetaMask advises viewing multiple pages of accounts on both derivation paths, Ledger Live and Legacy. A derivation path decides which addresses the device generates, so an account created under one path will not appear under the other.

For people who also keep funds in a browser-only wallet, hot wallet vs cold wallet explains how the two storage styles differ, which helps decide which balances belong on the hardware account.

Frequently asked questions

Question	Answer
Can I connect a non-Ethereum-style Ledger account?	No. MetaMask says only EVM-based Ledger accounts can be connected to it.
How do I remove a connected hardware account?	Click the three dots beside the account in MetaMask and select Remove account.
Does a hardware account behave differently from other accounts?	MetaMask says it behaves just like any other MetaMask account, with the device needed to sign.
What can I do once the Ledger is connected?	You can check your ETH or token balance, sign transactions and messages, deploy contracts, and use sites that integrate with MetaMask.