> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/get-started/setup/restore-existing-wallet/hardware-wallet.md).

# Hardware wallet

Connect a Ledger, Trezor, BitBox, COLDCARD, or Cupcake hardware wallet to Cake Wallet, with supported coins per device and Bluetooth, USB, or QR steps.

{% hint style="info" %}
Hardware wallet support is limited to specific devices and currencies. Check the lists below before you start.
{% endhint %}

## Supported devices

**Connected over Bluetooth or USB**

* **Ledger** — Monero, Bitcoin, Litecoin, Bitcoin Cash, Ethereum, Polygon, Zcash
* **Trezor** — Monero, Bitcoin, Litecoin, Ethereum, Polygon
* **BitBox** — Bitcoin, Ethereum, Polygon (Android over USB; iPhone and iPad over Bluetooth with a BitBox02 Nova)

**Air-gapped, over QR codes** — these devices are never plugged in or paired. Cake Wallet displays a QR code, you scan it with the device, and then scan the signed result back into Cake Wallet.

* **COLDCARD** — Bitcoin, using either the `BCUR` or `BBQR` QR code format
* **Cupcake** — Cake's own air-gapped signing app, for Monero, Bitcoin, Litecoin and Zcash. Add it from `Restore Wallet` → `Cupcake App`; see the [Cupcake documentation](https://docs.cakewallet.com/cupcake)

{% hint style="warning" %}
**SeedSigner**, **Keystone** and **Foundation Passport** aren't supported yet. **BitBox** works on Android, iPhone and iPad only, not on macOS or Linux, and Zcash, including Zcash on Ledger, isn't available on macOS or Linux.
{% endhint %}

{% hint style="info" %}
**Trezor:** Cake Wallet recognizes the Trezor Model One, Model T, Safe 3, Safe 5 and Safe 7. How it talks to your Trezor depends on the coin:

* **Bitcoin and Monero** use Cake Wallet's built-in Trezor connection: select your Trezor in Cake Wallet and approve on the device — no Trezor Suite, bridge, or separate app needed. The Safe 7 connects over Bluetooth or USB; the Model One, Model T, Safe 3 and Safe 5 connect over USB only, and Cake Wallet offers USB on Android only. On iPhone and iPad, that means you need a Safe 7.
* **Litecoin, Ethereum and Polygon** use Trezor Connect. Cake Wallet skips its own device connection step and opens Trezor Connect outside the app, which passes the result back to Cake Wallet.
  {% endhint %}

## Compatibility by platform

| Device   | Android                       | iPhone and iPad              | macOS                                          | Linux         |
| -------- | ----------------------------- | ---------------------------- | ---------------------------------------------- | ------------- |
| Ledger   | Bluetooth or USB              | Bluetooth                    | Bluetooth, all Ledger coins except Zcash       | Not available |
| Trezor   | USB, or Bluetooth on a Safe 7 | Safe 7 over Bluetooth        | Bitcoin and Monero on a Safe 7, over Bluetooth | Not available |
| BitBox   | USB                           | BitBox02 Nova over Bluetooth | Not available                                  | Not available |
| COLDCARD | QR codes                      | QR codes                     | QR codes                                       | Not available |
| Cupcake  | QR codes                      | QR codes                     | Not available                                  | Not available |

Hardware wallets can't be added on Linux, and Zcash isn't available on macOS or Linux at all, so Zcash on a Ledger needs Android, iPhone or iPad.

## Restore wallet from hardware

{% stepper %}
{% step %}

### Step 1

Go to the `Wallets` tab in the bottom navigation bar, then tap `Restore Wallet`.

<div><figure><img src="https://content.gitbook.com/content/XUxrs2r29bTlRr2etoiy/blobs/6yDV3h0HFUctb41segHW/restore%202.png" alt="Wallets tab in the bottom navigation bar"><figcaption></figcaption></figure> <figure><img src="https://content.gitbook.com/content/XUxrs2r29bTlRr2etoiy/blobs/09tJJnkrBFIVtPq2U8Fu/restore%203.png" alt="Restore Wallet button on the Wallets screen"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Step 2

On the `Restore Wallet` screen, tap `Hardware wallet`, then choose the wallet type.

<div><figure><img src="https://content.gitbook.com/content/XUxrs2r29bTlRr2etoiy/blobs/FtBpr9WZaGrzLnti492l/restore%204.png" alt="Hardware wallet option on the Restore Wallet screen"><figcaption></figcaption></figure> <figure><img src="https://content.gitbook.com/content/XUxrs2r29bTlRr2etoiy/blobs/tq8aifOp1dwKB3dFzy4o/restore%205.png" alt="Choosing the wallet type to restore from a hardware wallet"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Step 3

Connect your hardware wallet device.

On Android, Ledger and Trezor devices can connect over Bluetooth or USB, and BitBox connects over USB. **USB connections are available on Android only.** On iOS and macOS, Ledger devices connect over Bluetooth. On iPhone and iPad, a Trezor needs to be a Safe 7 (see the Trezor note above), and a BitBox needs to be a BitBox02 Nova, which connects over Bluetooth.

Air-gapped devices such as COLDCARD and Cupcake are never connected: instead of this step, you scan QR codes back and forth between Cake Wallet and the device.

Make sure the required app is open on your device *before* selecting it: Ledger devices use per-coin apps (for Zcash, version 3.9.2 or later of the Zcash app), while BitBox devices, and Trezor devices for Bitcoin or Monero, need no app.

Once you see your device, select it from the menu and allow access (if applicable).

![Swipe left to right](https://content.gitbook.com/content/XUxrs2r29bTlRr2etoiy/blobs/tNCHuT67JUVx2cZ12kbn/restore%206.png) ![Allow Access](https://content.gitbook.com/content/XUxrs2r29bTlRr2etoiy/blobs/IpL022oRFdfdFudarmP3/restore%207.png)
{% endstep %}

{% step %}

### Step 4

Select your desired account and name your wallet. For Zcash, there's no account to pick: name the wallet and enter its restore height or date so Cake Wallet can start scanning from there.

Then tap `Next`, and you will be in a view mode of your hardware wallet's account, indicated by the icon next to the wallet type.

![Choose account](https://content.gitbook.com/content/XUxrs2r29bTlRr2etoiy/blobs/8XU3Nc3FLKDK5jSi1ZdS/restore%208.png) ![Balance screen](https://content.gitbook.com/content/XUxrs2r29bTlRr2etoiy/blobs/ZM21w58LR4qgO2jWu8sO/restore%209.png)
{% endstep %}
{% endstepper %}

## BitBox: pairing code

When you connect a BitBox, Cake Wallet may show a `Pairing Code` screen. Check that the code matches the one shown on your BitBox, then tap `Continue`. If the codes don't match, close the screen to stop connecting.

## Zcash on Ledger

A Zcash wallet added from a Ledger works a little differently from one created in Cake Wallet:

* **Receive:** you can choose `Shielded`, `Unified` or `Public` addresses. The rotating `Transparent` and the `Legacy Shielded` (Sapling) address types aren't available.
* **Send:** sends always come from your shielded balance, and you approve each one on the Ledger.
* **Shielding:** ZEC received to a `Public` address isn't shielded automatically. Once more than 0.0003 ZEC is waiting, the home screen shows `Unshielded Funds Detected`. Tap it, then `Shield Funds`, and approve on your Ledger to move those funds into your shielded balance.

See [Zcash](https://docs.cakewallet.com/cryptos/zcash) for more about Zcash address types.

## Trezor: passphrase and pairing

When you add a Bitcoin or Monero wallet from a Trezor, Cake Wallet shows an `Almost Ready` screen before it continues:

* Turn on `Passphrase (Optional)` if this wallet has a passphrase. You can then type it in Cake Wallet under `Passphrase`, or turn on `Enter passphrase on device` to type it on the Trezor instead.
* On a Safe 7, the first time you pair you type the `Pairing Code` shown on the device into Cake Wallet. Cake Wallet remembers the pairing, so you aren't asked for the code again, and you may also see an `Auto-connect` toggle.
* Tap `Skip` if you don't need any of these, or `Continue` once you've set them.

## How to tell a wallet is on a hardware wallet

On the home screen, a hardware wallet shows a small device icon before the wallet name: a Ledger, Trezor, BitBox or Cupcake icon, or a QR-device icon for COLDCARD. Wallets created in Cake Wallet have no icon there. Screen readers read the name as "*wallet name*, Hardware wallet".

The `Wallets` list doesn't mark hardware wallets, so switch to a wallet to check it.

## Recovery & Keys on a hardware wallet

Your recovery phrase stays on your hardware wallet; Cake Wallet never receives it. When you open `Settings` → `Recovery & Keys` for a Ledger, Trezor or BitBox wallet, the screen's title ends in `(Ledger)`, `(Trezor)` or `(BitBox)`, and:

* There's no `Recovery Phrase` tab, because the phrase only exists on the device.
* The `Keys` tab shows only keys that let Cake Wallet see your funds, such as the `xPub` for Bitcoin and Litecoin or the view keys for Monero.
* Every send still has to be approved on the device.

To back up a hardware wallet, keep the recovery phrase you wrote down when you set up the device itself.

Tutorial video

[![How to Use Your Ledger With Cake Wallet](https://img.youtube.com/vi/jExAUzETuuo/maxresdefault.jpg)](https://youtu.be/jExAUzETuuo)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cakewallet.com/get-started/setup/restore-existing-wallet/hardware-wallet.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
