# Importing keys from a recovery phrase

## Overview

This guide walks you through importing private keys generated from a recovery phrase into the Transaction Tool. \
A recovery phrase can generate multiple private keys at different indexes. \
By importing keys from your recovery phrase, you can manage all keys derived from it in one place within the Transaction Tool.

***

## Prerequisites

Before you begin, you should have completed the following:

* **Transaction Tool Setup**: Follow the [New User Installation Guide](https://docs.hedera.com/hedera-transaction-tool-v2/general/install-new-users) or [Install: Existing Users](https://docs.hedera.com/hedera-transaction-tool-v2/general/install-existing-users).
* **User Account Configuration:** Complete the [Account Setup](https://docs.hedera.com/hedera-transaction-tool-v2/general/install-new-users/account-setup) process to create user account.
* **Recovery Phrase:**
  * A valid 24-word recovery phrase
  * Knowledge of which key indexes you want to generate from this phrase (starting at index 0, 1, 2, etc.)

***

## Step-by-Step Guide

### Step 1: Navigate to the Key Management Settings

* Select **Settings** from the bottom left corner of the application.

<figure><img src="https://2153012268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIupt2Mk5CkOvzIUMpDrp%2Fuploads%2FUk3SlY3TOfmWM7Oab97y%2Fimage.png?alt=media&#x26;token=5ac0a70e-add2-4667-b3b8-20169a02f4a4" alt="" width="262"><figcaption></figcaption></figure>

* Select the **Keys** tab to access key management options.

<figure><img src="https://2153012268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIupt2Mk5CkOvzIUMpDrp%2Fuploads%2FoXJnVQgl2a6njttmvlkq%2Fimage.png?alt=media&#x26;token=b68902ec-1acc-44d3-bb92-f0f461287c71" alt=""><figcaption></figcaption></figure>

***

### Step 2: Initiate the Recovery Phrase Import Process

* Select **Import** from the top right corner of the Keys interface.

<figure><img src="https://2153012268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIupt2Mk5CkOvzIUMpDrp%2Fuploads%2Frwd5ZC59jvdqgal0FmWc%2Fimage.png?alt=media&#x26;token=630a057a-cf70-4ccb-bb52-80e6b1601464" alt="" width="329"><figcaption></figcaption></figure>

* Select **Recovery Phrase** from the drop-down menu.

***

### Step 3: Enter Your Recovery Phrase

* In the **Recovery Phrase** field, enter your complete 24-word recovery phrase.&#x20;

<figure><img src="https://2153012268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIupt2Mk5CkOvzIUMpDrp%2Fuploads%2F1RPnpLL1M1pE7IxlV8fQ%2Fimage.png?alt=media&#x26;token=70bc789d-3b1d-421b-b610-f4f90ff09d3f" alt=""><figcaption></figcaption></figure>

* In the **Recovery Phrase Nickname** field (optional), enter a descriptive name to identify this recovery phrase. This is useful if you manage multiple recovery phrases within the Transaction Tool.
* Select **Continue** to proceed.

{% hint style="success" %}
**Important:** The Transaction Tool does not store your recovery phrase. It uses the phrase only to generate keys. Always **store your recovery phrase safely**, as you will need it to regenerate your private keys.
{% endhint %}

***

### Step 4: Provide the Key Index

* In the **Key Index** field, enter the index of the private key you want to generate from this recovery phrase.

<figure><img src="https://2153012268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIupt2Mk5CkOvzIUMpDrp%2Fuploads%2Fr7hcw655oFAJpg7Rh8es%2Fimage.png?alt=media&#x26;token=7658821b-f3e3-40ba-9729-ecc3c43edb22" alt=""><figcaption></figcaption></figure>

* Select **Continue** to proceed.

{% hint style="info" %}
**Note:** If you receive an error stating **"Key at index X is already restored,"** this means a key at that index has already been imported from this recovery phrase. Choose a different index or check your existing keys in the keys table.
{% endhint %}

***

### Step 5: Name Your Generated Key (Optional)

* In the **Key Nickname** field (optional), enter a descriptive name for the private key generated at the index specified in Step 4.

<figure><img src="https://2153012268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIupt2Mk5CkOvzIUMpDrp%2Fuploads%2F1AhOgOUmJCDMMnkUzcfP%2Fimage.png?alt=media&#x26;token=32c21383-6998-486a-8299-47e57d444c31" alt=""><figcaption></figcaption></figure>

* Select **Continue** to complete the process.
* The system will validate the recovery phrase and generate the private key at the specified index. Once complete, the new key will appear in the keys table.

***

### Step 6: Verify Imported Keys

* Review the keys table to ensure your imported keys appear correctly.

<table><thead><tr><th width="193.05859375">Field</th><th>Description</th><th>Example</th></tr></thead><tbody><tr><td><strong>Index</strong></td><td>The index at which the private key was generated.</td><td><code>0, 1, 2...</code></td></tr><tr><td><strong>Nickname</strong></td><td>The nickname provided for the key.</td><td>"Main Signing Key"</td></tr><tr><td><strong>Account ID</strong></td><td>If the key is associated with an account on the selected network, the account ID will be displayed here.<br>If the key is not associated with any account, this field remains empty.</td><td><code>0.0.12345</code></td></tr><tr><td><strong>Key Type</strong></td><td>The type of key. Either an ED25519 or ECDSA key type.</td><td>ED25519, ECDSA</td></tr><tr><td><strong>Public Key</strong></td><td>The public key corresponding to the private key.</td><td><code>b691f79aef5b36f5a3c58757971bca9.....</code></td></tr><tr><td><strong>Private Key</strong></td><td>The private key</td><td>Hidden for security reason</td></tr></tbody></table>

* Verify that key information such as index, key type, public key, and nickname are displayed accurately.

***

### Filtering Keys by Recovery Phrase

You can filter your keys to view only those imported from a recovery phrase.

* At the top of the **Keys** table, select **Imported from Recovery Phrase**.
* The table will display only keys generated from recovery phrases.

<figure><img src="https://2153012268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIupt2Mk5CkOvzIUMpDrp%2Fuploads%2FwJbW0PQf6nB05WlEIWtL%2FScreenshot%202025-10-14%20at%207.07.55%E2%80%AFPM.png?alt=media&#x26;token=6a25b1da-d74e-481a-b8ed-36284d47c3f4" alt=""><figcaption></figcaption></figure>

***


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://transactiontool.hedera.com/keys/importing-keys-from-a-recovery-phrase.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.