> For the complete documentation index, see [llms.txt](https://doc.crocwallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.crocwallet.com/getting-started/import-wallet.md).

# Import a Wallet

Select **Import Wallet** in the Croc Wallet Extension, then choose the network and import method before entering recovery material.

![All Networks import entry in the installed Croc Wallet](https://773692820-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4GELzY2MfwaDgVIZumqt%2Fuploads%2Fgit-blob-86412a119c519df645c2a0b5313eca9da8f3f707%2F03-import-networks.jpg?alt=media)

**All Networks** uses a 12-word recovery phrase. To import a network-specific key, select **Canton Mainnet**, **EVM Networks**, or **Solana Mainnet** and use a method offered by that selection. A single-network private key does not recreate accounts on every network.

![Canton import options in the installed Croc Wallet](https://773692820-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4GELzY2MfwaDgVIZumqt%2Fuploads%2Fgit-blob-90c0e9166f754a408474d0b4ab4aa39110ec934f%2F03-import-canton.jpg?alt=media)

## Import your wallet

1. Open the Extension and select **Import Wallet**.
2. Select the network. Choose **All Networks** for a supported 12-word multichain recovery phrase.
3. Select **Import with Recovery Phrase** or, where offered, **Import with Private Key**.
4. Select **Continue**.
5. Enter the corresponding recovery phrase or private key only inside the Extension. Follow the word-count options shown for the selected network.
6. Set the required local password, review the recovery acknowledgment, and confirm only when ready.
7. Wait for account restoration and verify the selected account and network before use.

The current import entry screen does not ask for a Canton Party ID. The Canton restore flow can resolve an existing backend binding using the derived public key. Keep an independent record of the complete Party ID to verify the restored account; possessing a secret does not guarantee that every provider's account binding can be restored by this deployment.

Recovery-secret fields are deliberately not pictured in this guide. Never capture or publish a real recovery phrase or private key.

> **Security warning:** A website, support representative, or DApp must never request your recovery phrase or private key. Do not enter either secret outside the Croc Wallet Extension.

## If import does not complete

* **Invalid word count:** make sure the recovery phrase contains all 12 words, separated by spaces and in the original order.
* **Invalid key format:** copy the complete private key without extra spaces or missing characters.
* **Party or key mismatch:** stop and verify that the phrase or key belongs to the Canton party you expect. Never send the secret to another person for checking.

Next: [Home and Assets](/using-the-wallet/home-and-assets.md)


---

# 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://doc.crocwallet.com/getting-started/import-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.
