KeepKey

A hardware wallet for USB use with KeepKey Desktop on Windows, macOS or Linux. Read requests on its OLED screen and approve with the device button.

KeepKey

Approve transactions with

  • Computer: Approve transactions
  • iPhone: Not confirmed
  • Android: Not confirmed

Controls

Physical buttons

Backup

Recovery phrase

Power

USB power

Is it right for you?

Is this the right wallet for you?

A good fit if

You want a USB computer routine with a device screen and confirmation button, and are comfortable entering your PIN through positions in the companion app.

Consider another model if

You need a documented phone-signing routine, or prefer entering your PIN and recovery words directly on a touchscreen.

Worth comparing

  • Trezor Safe 5

    Choose Safe 5 for a colour touchscreen with device PIN and recovery-word entry, using Trezor Suite over USB on a computer or compatible Android phone. It does not sign with an iPhone.

    Compare KeepKey and Safe 5
  • Ledger Flex

    Choose Flex for Ledger Wallet over Bluetooth on an iPhone or Android phone, with touchscreen entry and review. Installing the current iPhone app requires iOS 15.1 or later; on Android, Ledger Wallet requires Android 10 or later.

    Compare KeepKey and Flex

Phones and computers

Check compatibility with your phone or computer.

Check the app and connection for each device. Setup and transaction signing are confirmed separately.

Computer

KeepKey Desktop

USB

  • Windows 10 or later (x86-64)
  • macOS 13 or later (x86-64 or ARM64)

Linux

  • Set up the wallet
  • Approve transactions
More wallets for computers

iPhone

  • Support for wallet setup is unconfirmed
  • Support for signing is unconfirmed
More wallets for iPhone

Android

  • Support for wallet setup is unconfirmed
  • Support for signing is unconfirmed
More wallets for Android

A USB computer routine with the current KeepKey Desktop app

KeepKey works with KeepKey Desktop on a Windows, macOS or Linux computer. Connect it with a USB data cable, which also supplies operating power. The app prepares transactions and shows your accounts; the hardware provides the screen and button for checking and approving requests.

The current app requires Windows 10 or later, 64-bit; macOS 13 or later; or Linux x86_64 with glibc 2.35 or newer. On a Mac, choose the arm64 installer for Apple Silicon or x64 for Intel. Installer files may still say KeepKey Vault: that is the current companion app.

KeepKey’s phone app can show your accounts. Its current instructions leave it unclear how to get a transaction from the phone to the device for approval. Use the computer USB setup described here, or compare Flex below for Bluetooth signing from your phone.

The Classic-finish store offer includes the KeepKey device, a USB cable, two recovery cards and a quick-start guide. The cards give you a place to record your own new recovery words during setup.

Read the digits on KeepKey; click their positions in Desktop

You choose a device PIN during setup. When you enter it, KeepKey’s screen shows digits in a shuffled 3×3 grid. KeepKey Desktop shows nine blank positions. Find each digit of your PIN on the device and click the corresponding position in the app. The layout changes for the next unlock, so use the arrangement currently shown on KeepKey.

The current PIN guide accepts PINs 1–9 digits long and recommends at least four. Incorrect guesses lead to longer waits before another attempt; they do not automatically wipe the device. If you forget the PIN, the app’s forgotten-PIN option intentionally wipes KeepKey and starts recovery. Have the recorded recovery phrase, and the exact passphrase if you used one, available before choosing that route.

KeepKey’s Desktop illustration shows an Enter PIN panel with nine blank position buttons, an Unlock button and a forgotten-PIN option.
KeepKey’s app illustration shows the blank positions you click on the computer; the shuffled number grid is shown on the device.

Approve on KeepKey, then broadcast in Desktop

For an ordinary transfer, choose Send on the asset card in KeepKey Desktop. Enter the recipient address and amount, choose a fee priority and select Build Transaction. Review the destination, amount and network fee in the app. Then read the full recipient address and amount on KeepKey and approve or reject with its button according to the device prompts.

Approval returns the signed transaction to Desktop. Choose Broadcast Transaction to send it to the network; signing on the device is not this final sending action. Cancelling during device review has not broadcast the payment. After broadcast, Desktop shows the transaction ID and tracks its status while the network confirms it.

KeepKey’s manufacturer photograph shows the front of the hardware wallet with a blank OLED screen and a cable connected at its side.
KeepKey’s front and connected cable in the manufacturer photograph. The OLED screen is unlit.

Receive Bitcoin or Ethereum into the right account and network

Bitcoin and Ethereum are supported in the documented KeepKey Desktop computer routine. To receive, choose Receive on the intended asset card. Compare the complete address shown in Desktop with the address on KeepKey before sharing it with the sender.

Bitcoin receiving choices include Legacy, SegWit and Native SegWit accounts. Choose the account type you intend to fund; these use different address paths. When withdrawing from an exchange, select the supported coin or token you want to receive and a withdrawal network matching the receiving account’s network. A name such as USDT alone does not determine that network.

The address QR in Desktop helps the sender copy the receiving details. It is not a QR signing connection. Once the checked address is shared, KeepKey does not need to stay connected while the incoming transfer arrives on the blockchain.

Create a new wallet or restore the recovery phrase you already have

For a new wallet, choose Create New Wallet in Desktop. Expand Seed length to choose 12, 18 or 24 words. KeepKey recommends 12 as the default. The device generates and displays the words for you to write down in order. This is a BIP39 recovery phrase: one ordered word list used to restore the wallet if the device is lost or replaced.

For an existing backup, choose Recover Existing Wallet on a new or wiped KeepKey and select 12, 18 or 24 to match the phrase exactly. KeepKey uses the English BIP39 wordlist. During recovery, the device’s scrambled alphabet tells you which mapped letters to enter in Desktop. Follow the dedicated cipher procedure below; the real words are not entered in an ordinary text field.

Restoring the words and finding the original accounts are separate parts of the task. Use the original assets, networks and supported account/address paths, then compare the receiving addresses with the originals. If you used a hidden-wallet passphrase, you need that exact passphrase too.

For a new wallet (BIP39)
Word count: 12, 18, or 24
To restore a wallet (BIP39)
Word count: 12, 18, or 24

Check the written backup while the wallet still works

Use Verify Now during setup, or the backup check under Settings → Device later. Read from your written record and follow the device-guided check. The result tells you whether that record matches the recovery phrase held by KeepKey; this is a check, not a new-wallet creation or restoration.

If the check does not match, keep a funded device intact while you review the written order and retry the documented check. Do not wipe it to test recovery.

An optional passphrase opens separate hidden accounts

A passphrase is an optional additional recovery password. KeepKey combines it with your recovery words to open a separate wallet with its own addresses and accounts. Enable BIP-39 Passphrase under Desktop’s Settings → Security; the app then asks you to enter it whenever you unlock. Different spelling, capitalization or spaces open a different wallet rather than producing a wrong-password error.

To restore those accounts, retain the original words and exactly the same passphrase. Before funding a hidden wallet, note its receiving address, disconnect and reconnect KeepKey, enter the passphrase again and check that the same address returns. This checks that you can reproduce the hidden wallet; it is separate from checking the written recovery words.

Update the app, bootloader and device firmware separately

KeepKey Desktop is the computer app; firmware is the software on KeepKey. The device’s bootloader provides its update mode. Each has its own version number. For the app, use Settings → Application → App Version → Check for Updates and follow the update or installer prompts for your computer. KeepKey Desktop also handles device updates, replacing the retired KeepKey Client and KeepKey Updater.

Update the device

  1. Before a device update, confirm your written backup with the check described above.
  2. When the current KeepKey Desktop app offers a device update in the portfolio, follow that prompt’s instructions. To enter bootloader mode when asked, unplug KeepKey, hold its button and reconnect while holding it.
  3. If Desktop flags an outdated bootloader, complete its guided bootloader update before proceeding to device firmware.
  4. Read the selected published firmware version in Desktop, choose Install Official Firmware and compare the version displayed on KeepKey with the app’s selection. Confirm on the device only if the versions match, and wait with KeepKey connected until installation finishes.
  5. When Desktop asks you to reconnect afterward, plug KeepKey in normally without holding the button; holding it would return to bootloader mode.

A retired ShapeShift-era app also used the KeepKey Desktop name and can hold the USB connection; quit old software if the current app cannot open the device.

Hardware details

DetailValue
DisplayDisplay typeOLED
Resolution256 × 64 px
Power and chargingOperating powerUSB power
Materials and finishMaterialsBody: Aluminium
Security and softwareSecurity chipNo Secure Element
ProcessorControllersSources disagree

Wallet access

PIN entry
In the wallet’s companion app
Passphrase entry
In the wallet’s companion app
Sources

This page is based on manufacturer documentation.

Documentation checked: · ·

How we compare