Back to Table of Contents

Exporting private keys

Private keys are long strings of letters and numbers that are literally the key to spending your bitcoin. Each wallet has a number of private keys (one for each address). You can back up your private keys for a MultiBit Classic wallet into a text file called a 'private key export file'. You can password protect this text file to prevent other people reading this data.

How to export the private keys in a wallet

  1. In the 'Wallets' side panel choose the wallet you want to export the private keys for.
  2. Select the menu option 'Tools | Export Private Keys'. The 'Export Private Keys' screen appears.
  3. By default, the private keys file is called the same as your wallet file, only with an extension 'key' rather than wallet.

  4. If you want to output the private key file to a different directory or filename click on the 'Export to. . .' button. A file chooser opens and you can select the file to save to.
  5. It is strongly recommended that you password protect your private key export files. To do this, click on the 'Password protect export file' radio button. Enter the password you want to use in the 'Password' field and then repeat the same password in the 'Repeat password' field. If they match you get a little green tick on the right hand side.
  6. To output the private keys to the output file specified, click on the button 'Export private keys'. The private key file is written and a success message appears. If the export of the private key file fails for any reason the error message is given on screen.
  7. After the export file is written, it is then verified by reading the file back in again and checking the keys in the file match the keys in the wallet. A verification message is given if this is successful.

Export file format (no password)

Below is an example of a private key export file containing demonstration private keys. You typically use Notepad or similar when working with this file.

# Anyone who can read this file can spend your bitcoin.
# Format:
#   <Base58 encoded private key>[<whitespace>[<key createdAt>]]
#   The Base58 encoded private keys are the same format as
#   produced by the Satoshi client/ sipa dumpprivkey utility.
#   Key createdAt is in UTC format as specified by ISO 8601
#   e.g: 2011-12-31T16:42:00Z . The century, 'T' and 'Z' are mandatory
Labc123abc123abc123abc123abc123abc123abc123abc123abc 2013-01-01T12:00:00Z
Kdef456def456def456def456def456def456def456def456def 2013-01-01T12:00:00Z
# End of private keys

The key (shown in bold) begins with either "L" or "K". The date is there to allow import software to know when the key was created to avoid looking further back in history than is necessary. Don't change the date to be more recent as doing so will very likely cause a failed import and an incorrect balance.

Export file format (password protected)

Below is an example of a password protected private key export file containing demonstration private keys. You typically use MultiBit Classic or OpenSSL when working with this file.


The content is encrypted (AES256, password-based key derivation) so can only be decrypted by special software and the provision of a password.

The MultiBit Classic wiki provides detailed technical information about the file format.

If you are intending to store exported keys for a very long time and are concerned about code existing to open them far in the future then we recommend the following:

  • Make a copy of the MultiBit Classic source code (fork on GitHub)
  • Decompile a binary of the MultiBit Classic JAR (standard tools exist for this)