Recommended Free Tools
The safest Zcash backup is wallet-specific. In zcashd, preserve wallet.dat or export every spending key. In Zallet, a usable recovery set can require wallet.db, the age encryption identity, each mnemonic, and account metadata. A seed phrase alone is not guaranteed to restore imported keys or watch-only data.
Shielded addresses encrypt transaction details, while transparent addresses expose more information on-chain. Choose shielded addresses when your counterparty and wallet support them, then protect the device and recovery material separately from theft, loss, and unauthorized access.
As an Amazon Associate I earn from qualifying purchases.
What a Zcash wallet backup actually protects
“Backing up your Zcash private keys is the best way to prevent loss of funds,” according to Zcash’s wallet-backup guidance. A backup preserves the secret material needed to authorize spending. It does not automatically protect you from a stolen recovery phrase, a compromised computer, or a backup that was made before a new key or account was created.
Wallets can contain more than one kind of data:
- Spending keys: the private keys that can authorize transactions.
- Viewing keys: keys that can reveal shielded transaction information without permitting spending.
- Imported keys: standalone keys added to the wallet rather than derived from its mnemonic.
- Watch-only records: addresses or viewing material used to monitor funds.
- Scanning metadata: account indexes, birthday or scan heights, and other information needed to find historical transactions efficiently.
- Transaction history: wallet records that may reveal financial activity even when spending keys are encrypted.
Because each application stores these items differently, “I wrote down my 12 or 24 words” is not a universal backup plan. Before deleting a wallet or changing software, identify the wallet name, version, platform, network, address types, derivation scheme, and any keys imported separately.
#1 Best Overall
Back up a zcashd wallet
The classic zcashd wallet stores its primary data in wallet.dat. Zcash documentation describes a complete wallet copy as the easiest way to preserve wallet data, while also supporting key exports for additional resilience.
Option 1: Create a full wallet copy
- Close any operation that is writing to the wallet and confirm you are working on the intended network.
- Use the wallet RPC command
backupwallet, supplying a destination on a separate storage device or in a protected offline location. - Wait for the command to report success, then verify that the destination file exists and can be read.
- Encrypt the copy before placing it in cloud or third-party storage. An unencrypted wallet file can expose spending capability to anyone who obtains it.
- Record when the backup was made and which wallet, network, and software version it belongs to.
Run another backup whenever you generate a new address. A previous copy may not contain keys created after that backup, so an apparently healthy file can still be incomplete for later deposits.
Option 2: Export keys
z_exportwallet can export wallet keys to a file, and individual-key export is useful when you need to preserve a particular address. Store exported files as highly sensitive secrets: anyone who obtains a spending key may be able to move the associated funds. Key exports are a supplement, not a reason to discard a tested full-wallet backup.
Rank #2
What to verify before relying on a zcashd backup
- The file belongs to the correct network and wallet.
- Recent addresses and transactions are represented; make a new backup after creating addresses.
- Any manually imported keys were exported or otherwise included.
- The backup is encrypted at rest and has more than one durable offline copy.
- You have documented where the file is stored without writing secrets in an easily discoverable note.
Back up a Zallet wallet
Zallet uses a different recovery model. Its documentation states that there is currently no single command that creates a complete backup. A recovery set may include all of the following:
| Artifact | Why it matters | Important handling note |
|---|---|---|
wallet.db |
Contains wallet records, transaction history, viewing keys, imported material, and encrypted spending-key data. | Stop Zallet before copying it; copying while the application runs can produce a torn SQLite copy. |
| Age encryption identity | Needed to decrypt the spending-key material protected by Zallet. | Keep it separate from the database where practical, but ensure both can ultimately be retrieved by the owner. |
| Each mnemonic | Restores accounts derived from that mnemonic. | Write it on durable offline media; never upload an unencrypted phrase. |
| Seed fingerprint and ZIP-32 account index | Identifies the seed and account needed for deterministic recovery. | Preserve the exact values recorded by the wallet. |
| Account name and birthday height | Helps identify the account and tells recovery where to begin scanning the chain. | A wrong or missing birthday height can make a restore appear empty until a broader rescan is performed. |
Safe Zallet copy procedure
- Finish pending operations and quit Zallet completely.
- Confirm the process has stopped before touching
wallet.db. - Copy
wallet.dbto encrypted offline media. - Back up the age encryption identity separately, using a second protected location when feasible.
- Record every mnemonic and its associated fingerprint, ZIP-32 account index, account name, and birthday height.
- Make at least one additional copy in a location exposed to different hazards than the first, such as a separate physical site.
Treat wallet.db as privacy-sensitive. Zallet encrypts spending-key material, but transaction history and viewing keys are stored in cleartext. Possession of the database may therefore reveal financial information even when it does not by itself authorize spending.
Why a mnemonic may not restore everything
A mnemonic recreates accounts derived from that seed under the wallet’s supported derivation scheme. It does not automatically recreate every object a wallet can contain. Zallet explicitly warns that imported spending keys and watch-only material exist only in wallet.db; importing a mnemonic does not recover them.
The same issue appears when moving between applications. Before importing a phrase into a different wallet, confirm:
Free tools Windows power users keep installed
One-click scans. No signup required.
- Which derivation scheme and ZIP-32 account indexes the destination supports.
- Whether the destination supports the same shielded and transparent address types.
- How imported spending keys are exported and restored.
- Whether watch-only viewing keys can be transferred.
- Which birthday or scan height is required to discover old transactions.
If any answer is unknown, keep the original wallet and its complete artifacts until a test restore proves that balances, addresses, history, and spending access are present.
Design a backup that survives common disasters
Use durable offline records
Write recovery phrases and other irreplaceable recovery data on durable offline media rather than leaving the only copy on a phone or computer. A metal seed-phrase plate can improve resistance to fire or water, but it does not replace wallet-specific exports, an age identity, wallet.db, or scan metadata when those are required.
Rank #4
Separate secrets without losing recoverability
For Zallet, keeping the database and age identity in separate locations reduces the chance that one stolen item grants immediate spending access. Separation must be planned: if one component is destroyed and no second copy exists, the split becomes permanent loss. Maintain multiple encrypted copies and document how the legitimate owner can reunite them.
Encrypt before using remote storage
Cloud storage is a transport and availability convenience, not proof of confidentiality. Encrypt wallet databases and exported key files before uploading them. Never upload an unencrypted seed phrase, private key, age identity, or wallet database.
Test recovery, not just file existence
A backup is credible only after a restore test on a separate, offline-capable device or installation. Verify that the test wallet derives the expected accounts, finds historical transactions, displays the expected address types, and can create a transaction without exposing the real wallet’s secrets. Do not send funds during a test unless you deliberately use a small test amount and understand the network and fee implications.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Shielded and transparent addresses: what privacy settings change
Zcash distinguishes transparent, shielding, deshielding, and shielded transactions. Shielded addresses encrypt transaction details inside the shielded pool. Transparent addresses expose more transaction information on the public ledger, including the information normally visible for transparent inputs and outputs.
Holding funds in a shielded address is a central privacy practice; Zcash documentation describes holding some or all funds in a shielded address as one of the most important ways to maintain financial privacy. However, shielding does not erase every surrounding clue. Entering or leaving the shielded pool creates transparent endpoints, and counterparties, exchanges, timing, amounts, and wallet behavior can still reveal context. Do not describe a shielded address as hiding all metadata in every situation.
Choose the address type deliberately
- Use shielded addresses when the recipient, sender, and wallet software support them and you want transaction details encrypted.
- Use transparent addresses when compatibility requires them, understanding that more information is publicly visible.
- For shielding or deshielding, treat the transparent side as an observable endpoint and avoid assuming the transfer is indistinguishable from a fully shielded payment.
Find the privacy control in the wallet you actually use
Defaults and menu names differ by wallet and version. Do not apply a setting path copied from another application. Identify the exact wallet release, then check its send or receive screen for the address type and its privacy or shielded-transaction options. Confirm the destination address before approving a payment; a wallet cannot make a transparent address private after funds have been sent to it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Protect wallet data on the device
Address shielding protects transaction details on the network; it does not automatically encrypt files sitting on a laptop or phone. Some configurations may have wallet encryption disabled. When wallet-level encryption is unavailable or insufficient, use full-disk encryption or encrypt the home directory. Keep the operating system patched, lock the device, and avoid leaving wallet files in shared or temporary folders.
Device encryption and wallet encryption solve different problems. Full-disk or home-directory encryption protects data at rest if the device is lost or powered off. Wallet encryption or an age identity protects spending material within the wallet model. Use both where supported, and keep recovery copies offline so a malware-infected device is not your only source of funds.
Quick Recap
Recovery procedure and failure diagnosis
If you have a zcashd wallet copy
- Install the same or a compatible
zcashdversion on a clean device and select the correct network. - Restore the backed-up wallet file using the application’s documented wallet-replacement or import procedure.
- Allow the wallet to rescan or synchronize as required.
- Check that expected addresses and balances appear, then verify that spending is possible before retiring the old copy.
If you have Zallet artifacts
- Install the matching Zallet release or a release documented as compatible.
- Stop the application before placing the preserved
wallet.dbwhere Zallet expects it. - Supply the age encryption identity and import each mnemonic.
- Recreate accounts with the recorded fingerprint, ZIP-32 index, name, and birthday height.
- Allow scanning to complete and compare history, balances, imported keys, and watch-only records with your documentation.
Common symptoms and likely causes
| Symptom | Likely explanation | Next check |
|---|---|---|
| Mnemonic restores an account but not an address | The address came from an imported spending key or a different derivation path. | Recover the original database or key export and confirm derivation support. |
| Balance appears to be zero | The wallet has not scanned far enough, or the birthday height is wrong. | Use the recorded scan metadata and complete a rescan. |
| Zallet database will not open after copying | The copy may have been made while Zallet was running, creating a torn SQLite file. | Use a copy made after a clean shutdown. |
| History is visible but funds cannot be spent | Viewing data or a watch-only record was restored without spending keys or the age identity. | Locate the missing spending-key artifact; do not assume the mnemonic covers it. |
Rules for support, sharing, and day-to-day use
- Never paste a seed phrase, private key, wallet database, or age encryption identity into a support chat, form, website, or screenshot.
- Legitimate support should not need your spending secrets. Share public addresses, transaction IDs, error text, and software versions instead.
- Keep a written inventory of wallets, networks, address types, and backup dates without recording the secrets in the same easily accessible place.
- Refresh backups after generating new addresses or importing new keys.
- Before a major wallet upgrade or migration, perform a recovery test and retain the original artifacts until the new installation is proven.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
