MetaMask Private Key: How to Export, Import and Keep It Safe

Each account in MetaMask has its own private key. For an Ethereum account, the MetaMask private key is a 64-character hexadecimal string, and anyone who holds it can sign transactions from that account’s address. It is not the MetaMask password, and it does not recreate the Secret Recovery Phrase or the other accounts shown in MetaMask.

What a MetaMask private key controls

A private key gives full control over one address: its ETH, its tokens and NFTs, and any transaction or contract interaction signed from it. As Ethereum’s developer documentation explains, the public address is calculated from the key. Anyone can look up that address and its balance on a block explorer, but only the key can authorize a transaction from it.

Your 0x address is the same on Ethereum and on EVM networks such as Linea, Arbitrum and Base, so one key controls what that address holds on each of them, and nothing beyond it. Since MetaMask introduced multichain accounts, one account can also include a Solana and a Bitcoin address, each with its own key pair.

Private key vs Secret Recovery Phrase

The Secret Recovery Phrase, often called the seed phrase, is the master key to the wallet. MetaMask turns it into a seed under the BIP-39 standard, then derives each Ethereum account’s key from that seed with BIP-32, along a fixed derivation path in the BIP-44 format: m/44'/60'/0'/0. The path tells the wallet where each key sits, with the first account at index 0, the second at index 1, and so on.

Derivation only runs one way. With the phrase, you can regenerate every derived key, in the same order, on any device. With a single private key, you reach only its own account, and you can’t work out the phrase or any other key from it.

So the phrase is the backup that matters most, and a private key is the narrower backup for one account.

How to export your private key from MetaMask

First check the public address of the account whose key you need.

In the browser extension

MetaMask’s current English instructions for the extension use this route:

1. Click the account selector at the top of the screen, then the three-dot menu next to the account you need.
2. Choose Account details, then Private key.
3. Confirm with your MetaMask password.
4. Click and hold Hold to reveal Private Key until the key appears.
5. Write the key down or copy it, then click Done.

Older versions of the extension labeled this option Show private key or Export private key.

In the MetaMask mobile app

1. Use the account selector at the top of the wallet view to switch to the account, then tap the three dots next to it.
2. Tap Private keys.
3. Enter your MetaMask password to confirm.
4. Tap the copy icon next to the network you need.

The app copies the key to your clipboard, and MetaMask warns that a copied key is exposed to clipboard hacks. Paste it only where you intend to use it.

Menus differ between versions, so use the official instructions below if your screen differs. Revealing a key exposes it in readable form. Keep it private and offline, away from screenshots, shared screens and support messages. A connected hardware wallet keeps its keys on the device; MetaMask is not a way to export them.

When to export a private key

Export a key only for a purpose of your own, such as:

• Backing up an account you imported separately, which the Secret Recovery Phrase does not cover.
• Using one account in another wallet app. MetaMask notes that a key can be imported into any compatible wallet software.
• Moving a single account to another MetaMask installation without the whole phrase. For an account derived from your phrase, MetaMask suggests typing the phrase instead where that’s an option.

No legitimate website, app or support agent asks for your private key. MetaMask says no one on its team, Support included, will ever request it, and that anyone else who does is trying to steal your assets. A dapp connects through MetaMask and asks you to approve each request there; it never needs the key itself. If an email asks you to verify or sync your wallet, run the checks in our guide to MetaMask scam emails first.

How to store a MetaMask private key safely

To keep a private key safe, follow the storage rules MetaMask gives for the Secret Recovery Phrase: offline and physical. Write it on paper and keep it somewhere secure, such as a safe. A metal backup plate lasts longer than paper.

Don’t store the key in a text file, a screenshot, a synced notes app, an email draft or an online password manager. MetaMask warns that cloud storage and password managers can be hacked, and malware on a computer or phone can read anything kept there in plain text.

Label each copy with the public address it belongs to. A key always produces the same address, but finding out which one means entering the key into wallet software again, and the label spares you that exposure.

Sixty-four characters are easy to copy wrong by hand, so compare your copy with the screen character by character. Hexadecimal uses only the digits 0–9 and the letters a–f; any other letter is a copying error.

How to import a private key into MetaMask

You can import a key saved from an earlier MetaMask installation, exported from another wallet or kept as a backup. Enter it only in the official MetaMask extension or app.

In the extension:

1. Click the account selector at the top of your wallet.
2. Select Add wallet at the bottom of the list.
3. Choose Import an account.
4. Paste the key on the private-key import page and click Import.

In the mobile app, tap the current account to open the account selector, then tap Add wallet and Import an account. Paste the key, or scan a QR code if the other wallet offers one, and tap Import. Older versions of the extension called this option Import account.

Then compare the resulting public address with the account you expected. MetaMask rejects an Ethereum key unless it is exactly 64 hexadecimal characters, with or without a leading 0x, so a missing, extra or non-hex character makes the import fail, while a wrongly copied hex character imports a different address.

For an encrypted JSON export, open the Select Type menu on the import page, choose JSON File, click Choose file and supply the password used to encrypt that file. This is not necessarily your current MetaMask password. MetaMask documents JSON import for the extension, not the mobile app.

If your MetaMask uses Google, Apple or Telegram sign-in, an imported account becomes linked to that login and syncs to your other devices. MetaMask says you can’t disconnect it afterward, so import into a separate MetaMask installation if you don’t want that link.

After import, check the network and token display if the address is correct but an asset is not shown; see tokens that don’t show. Importing a key restores control of the corresponding account; it does not move funds or reverse transactions.

Why a phrase may not restore an imported account

A Secret Recovery Phrase recreates accounts derived from that phrase. An account imported separately with a private key or JSON file needs its own backup; a hardware wallet must be reconnected. After a restore from the phrase alone, an imported account stays missing until you import it again with its saved key or file. Social sign-in with Google, Apple or Telegram and the original MetaMask password restores imported accounts as well, but not hardware wallets.

What happens if someone gets your private key

Anyone who has the key can sign from that address exactly as you can. They don’t need your password, your device or your MetaMask installation, and a confirmed blockchain transaction can’t be cancelled or undone.

If you think a key has been exposed, act at once. MetaMask’s steps for a compromised account are to create a new wallet with a new Secret Recovery Phrase in another browser profile or on another device, move whatever remains into it, and stop using the old address. If a script seems to empty the old address automatically, MetaMask advises against sending in more ETH or tokens for gas, because a sweeper can take those too.

A malicious token approval is a different problem from an exposed key, and our MetaMask guide explains how to tell the two apart. Crypto Recovers restores access for rightful owners; we don’t take stolen-crypto or scam cases.

If you lost the private key and the Secret Recovery Phrase

If MetaMask still unlocks, nothing is lost yet. Export the key again as described above, and use MetaMask’s built-in option to reveal the Secret Recovery Phrase and back it up.

If it won’t open, do not reset the original installation just to reach an import screen. Preserve its browser data and existing backups first. A saved phrase or encrypted vault may provide a different route, depending on what survives and which password is available. The MetaMask recovery guide explains those cases; a public address alone is not enough.

In a desktop browser, the vault holds the phrase together with the keys of any imported accounts, and it opens only with your MetaMask password. MetaMask documents vault recovery for desktop browsers and says it is not currently possible on Android or iOS. If the password is the missing piece, see forgot MetaMask password. With no phrase, no saved key, no working social sign-in and no vault, nothing remains to work from: no one can rebuild a private key from an address.

If any of those cases turns into a professional recovery, your ETH and tokens never pass to us: Crypto Recovers doesn’t hold client funds. You regain access to your own account, move the assets yourself to a new wallet you’ve created, and pay the agreed fee separately, as the contract sets out. Our MetaMask wallet recovery page explains how a case is assessed.

Official documentation

• How to export a private key in MetaMask Extension and Mobile
• How to connect or import an existing wallet in MetaMask
• How to add missing MetaMask accounts after restoring with Secret Recovery Phrase
• How to secure your Secret Recovery Phrase and password

FAQ: MetaMask private key

Where does MetaMask store the private key?

On your own device, in MetaMask’s encrypted vault. The vault holds your Secret Recovery Phrase, from which MetaMask regenerates the keys of derived accounts, plus the keys of any accounts you imported. Your MetaMask password encrypts it; in Chrome it sits in the browser profile’s Local Extension Settings folder. With Google, Apple or Telegram sign-in, an encrypted backup of the phrase is also kept online and opens only with that login and your password.

Can I recover my private key if I lost it?

Yes, if the account was derived from a Secret Recovery Phrase you still have: restore the wallet, re-add accounts in their original order if needed, and export the key again. An imported account needs its saved key, its JSON file and password, or social sign-in with your MetaMask password. Without those, the vault in the original installation is the last route, and it opens only with your password.

Can I use the same private key in multiple wallets?

Yes. MetaMask notes that an account’s private key can be imported into any compatible wallet software, and the balance is the same in each because it lives on the blockchain. Every extra copy is another place the key can leak, so keep the number of installations that hold it small.

Is it safe to export my private key?

It carries real risk, so export only when you need to. MetaMask warns that exporting shows the key in clear text and that a copied key is exposed to clipboard hacks. Use a device you trust, with no one watching or recording the screen, store the key offline, and never give it to anyone who asks.

Can I export the private key of a hardware wallet account?

No. MetaMask only connects to a hardware wallet; the keys stay on the device, and each transaction is approved there. To restore those accounts elsewhere, use the hardware wallet’s own recovery phrase.