Export a wallet

Privy enables your users to export the private key for their embedded wallet. This allows them to use their embedded wallet address with another wallet client, such as MetaMask or Phantom.

Availability

Key export is only available in certain environments depending on how the wallet was created.

Show environments where key export is available.

The environments where key export is available depends on the environment where the wallet was created.

Wallets created client-side

Wallets created client-side (e.g. through Privy’s React, React Native, Swift, etc. SDKs) can only be exported via the exportWallet method in the React SDK.

Due to the sensitive nature of key export, it is only available in web environments where the operation can be secured with strict browser security guarantees.

If you’d like to enable key export with one of Privy’s other client-side SDKs, we encourage setting up a minimal web page with Privy’s React SDK and export wallet functionality that you can direct users to.

By default, to use wallets, users authenticate to the Privy API directly from their client using their access token. This means that users can send transactions or export their keys using their access token with the Privy API, even if an application does not implement Privy’s exportWallet method. This design ensures users always retain self-sovereign access to their wallet keys.To prevent users from unilaterally exporting keys, applications can set up a 2-of-2 key quorum as the wallet owner, consisting of the user and an authorization key controlled by the application’s server. This requires authorization from both parties to export the wallet.

Wallets created server-side

Wallets created server-side can only be exported via Privy’s server-side SDKs or REST API. This ensures that wallets are securely exported in an encrypted interaction between your app’s and Privy’s infrastructure.

Supported chains

Key export is available for all wallets on Tier 2 and Tier 3 chains.

Usage

Private key formats

The format of the exported private key varies depending on the chain type of the wallet:

Chain	Format	Example
Ethereum	Hex	`0x...`
Solana	Base58	`5K...`
Spark	Mnemonic	`word1 word2 word3 ...`
NEAR	ed25519: prefixed	`ed25519:...`
Sui	suiprivkey bech32	`suiprivkey...`
Bitcoin	WIF	`KwDi...`
All others	Hex	`0x...`

Embedded wallets

Using wallets

Custodial wallets

External wallets

Global wallets

Availability

Wallets created client-side

Wallets created server-side

Supported chains

Usage

Private key formats

Embedded wallets

Using wallets

Custodial wallets

External wallets

Global wallets

​Availability

​Wallets created client-side

​Wallets created server-side

​Supported chains

​Usage

​Private key formats

Availability

Wallets created client-side

Wallets created server-side

Supported chains

Usage

Private key formats