> For the complete documentation index, see [llms.txt](https://docs.vultisig.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vultisig.com/security-and-technology/emergency-recovery.md).

# Emergency recovery in Vultisig

Emergency recovery for Vultisig vaults with the Vault Share Decoder. Reconstruct private keys from a threshold of vault shares (DKLS and GG20) if Vultisig software becomes unavailable. Last-resort fun

{% hint style="danger" %}
**Last Resort Only**

Emergency recovery permanently converts a TSS vault to a single-signature wallet. Use it only if Vultisig software is completely unavailable.
{% endhint %}

***

## What is emergency recovery?

Think of your vault as a safe that only opens when several keys turn at once. Each device holds one key, called a vault share. No single key opens the safe, and no master key exists anywhere. There is nothing for an attacker to steal.

Emergency recovery combines the shares into that master key: one private key you can import into another wallet. The **Vault Share Decoder** does this if Vultisig software ever becomes unavailable.

***

## Recommended: Vault Share Decoder

The **Vault Share Decoder** is the recommended way to recover a vault. It is a community tool with a simple web interface: upload your shares, and it shows the private key and address for each chain. No installation required.

* **Website**: <https://share-decoder.vultisig.com>
* **Repository**: [GitHub](https://github.com/vultisig/community-tools/tree/main/recovery-tools/vultisig-share-decoder)

It supports both vault types: **DKLS** (current vaults) and **GG20** (older vaults), and detects which one you have.

{% hint style="info" %}
Shares are decoded in your browser and never leave your device. If you prefer to work offline, you can also run the decoder on your own machine (see [Run the decoder locally](#run-the-decoder-locally)).
{% endhint %}

***

## What you need

* **A threshold of vault shares**, for example 2 shares for a 2-of-3 vault. Each share is the `.vult` (or older `.bak`) backup file from a different device.
* **The backup password for each share**, if the backups are encrypted. Each backup may have its own password.
* **Your vault's addresses**, noted from the Vultisig app while it still works. Use them to confirm the recovered keys are correct.

***

## Recover with the website

1. Open [share-decoder.vultisig.com](https://share-decoder.vultisig.com).
2. Upload a threshold of vault shares and enter the password for any encrypted share.
3. Run the recovery and note the private keys and addresses for each chain.
4. **Check that every recovered address matches the address in your Vultisig app.** If an address does not match, the recovery is wrong. Do not send funds to it. Retry with the correct shares.

{% hint style="warning" %}
With fewer shares than the threshold, older (GG20) vaults can still show keys and addresses without an error. They are wrong. Always upload a full threshold of shares and compare the addresses.
{% endhint %}

***

## Run the decoder locally

Optional, for offline use or for developers. The local version has the same interface as the website. Build from source. Requires [Go 1.25+](https://go.dev/doc/install) with CGo.

```sh
git clone https://github.com/vultisig/community-tools.git
cd community-tools/recovery-tools/vultisig-share-decoder
```

**Web interface:**

```sh
make webserver
./dist/webserver
```

Then open <http://localhost:5000>. Start the server from the `vultisig-share-decoder` folder.

**Command line:**

```sh
make cli
./dist/cli recover --files share1.vult --files share2.vult --password <password1> --password <password2>
```

Omit `--password` for unencrypted shares. Add `--format json` for machine-readable output.

***

## Supported chains

* **UTXO:** Bitcoin, Bitcoin Cash, Dash, Dogecoin, Litecoin
* **Cosmos/BFT:** THORChain, MayaChain, Cosmos Hub, Kujira, dYdX, Terra Classic, Terra
* **EVM:** Ethereum
* **Tron:** TRX
* **XRP Ledger:** XRP
* **EdDSA:** Solana, Sui, TON

Tokens are recovered with their chain's key. For example, ERC-20 tokens use the Ethereum key. Other EVM chains, such as Arbitrum, Base, BNB Chain and Polygon, also use the Ethereum key and address. Osmosis, Noble and Akash use the Cosmos Hub key.

{% hint style="warning" %}
Chains not listed above, such as Cardano, Polkadot, Bittensor, and Zcash, are not yet supported by the decoder.
{% endhint %}

The [repository README](https://github.com/vultisig/community-tools/tree/main/recovery-tools/vultisig-share-decoder#importing-results) explains how to import each key type into another wallet.

{% hint style="danger" %}
**Warning:** Until you run recovery, the full private key has never existed. Recovery is one-way. Once the key exists, the vault is no longer a TSS vault but a single-signature wallet.

Move funds to a new vault after recovery. Never use a single-signature wallet for significant value again.
{% endhint %}

***

## Legacy recovery tools

The older recovery tools in [mobile-tss-lib](https://github.com/vultisig/mobile-tss-lib) only read GG20 vaults and cover fewer chains. Use the Vault Share Decoder instead.

***

## Related

* [Backup & Recovery](https://docs.vultisig.com/getting-started/backup-recovery.md): standard backup procedures
* [TSS Actions](https://docs.vultisig.com/security-and-technology/tss-actions.md): how threshold signatures work


---

# 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://docs.vultisig.com/security-and-technology/emergency-recovery.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.
