Does restoring a seed phrase recover wallet labels and notes?
A seed restores compatible keys and history, not every label or note. Learn how BIP329 exports wallet metadata and why labels need a private backup.

Usually, no. Restoring a seed phrase can reproduce compatible keys and let a wallet rescan for the addresses and transactions those keys control. It does not automatically recreate every label, contact name, category, note, coin-control choice or wallet-file setting from the original application. Those records are wallet metadata. Back them up separately from the seed, then verify that the receiving wallet can import the format you kept.
This distinction matters when a restored wallet appears to have the right balance but looks unfamiliar. A seed is recovery material for key derivation. A label such as monthly savings or practice donation is an application record attached to a transaction, address, public key or output. The label may describe the history without being part of the mnemonic, and it is not written into the Bitcoin blockchain by restoring the wallet. A rescan can rediscover on-chain history; it cannot infer the private note you wrote beside that history.
What the seed recovers
Keys, not your wallet's filing system
A compatible wallet uses the seed together with its own format, network, account type, derivation path and script rules. With the right settings, it can derive public addresses, find transactions and calculate balances. If those settings differ, the wallet may show an empty or incomplete view even when the seed is correct. A seed phrase can lead to different wallet addresses when the path, account, network or script convention changes.
The mnemonic does not contain a universal database of address names. It also does not guarantee recovery of imported single keys, watch-only branches, multisig policy, contact books or application preferences. A wallet-file password or device PIN protects an interface or file; changing it does not add label data to the seed. Keep the original wallet's metadata export until the restored view has been checked.
Rescan is not metadata recovery
After restoring, a wallet may need to derive accounts and scan for activity. That operation can locate activity recorded on-chain, but it does not know whether you called a transaction rent, client A or do not spend. A restored wallet may therefore show the correct outputs with blank descriptions. Do not treat blank labels as evidence that the seed failed, and do not send funds merely to test a label mapping.
The same limit applies to an address book. The seed may help the wallet rediscover an address that belongs to the account, but a saved contact name and the reason you trusted it are local records. Export them from the original wallet before deleting or migrating its file.
What BIP329 adds
A portable label format, not a replacement seed
BIP329 proposes a wallet-label export format. Its current status is Draft and its type is Informational; it does not guarantee that every wallet will accept the file. The format uses UTF-8 JSON Lines: one JSON object per line. Each record requires a type and a ref; label and origin are optional, and spendable is an optional output-only field.
The record can identify a transaction, address, public key, input, output, extended public key or another type defined by the proposal. This lets a compatible importer match a label to a record it already knows. It does not make a seed phrase more complete, and it cannot invent a missing wallet policy. An importer may ignore types it does not store or fail to match a record when its wallet scope differs.
The optional origin is also narrower than a recovery backup. BIP329 describes it as an abbreviated output descriptor with key-origin information, excluding actual keys, child path elements and a checksum. It can help distinguish records from different accounts, but it is not a full descriptor or a substitute for the wallet configuration required to derive addresses.
The format is not encrypted
BIP329 recommends encryption in transit over untrusted networks and says encryption at rest should be considered. The JSON Lines format itself does not encrypt labels. A file can contain transaction relationships, addresses, extended public keys, paths, amounts or arbitrary text depending on the exporter. Even without private keys, that information can reveal finances, counterparties or personal routines. Treat an export as sensitive, store it privately and remove unencrypted temporary copies when they are no longer needed.
What an implementation may actually import
Support is wallet-specific. For example, the current Sparrow WalletLabels implementation exports labels as newline-delimited JSON, with additional metadata where available. Its importer also handles BIP329 data and Electrum history CSV for the currently selected wallet. That is evidence about this implementation, not a promise that another wallet has the same menu, mapping or supported record types.
Sparrow's implementation can change an output's local status between frozen and available, and may ignore a record when its origin does not match. That local freeze does not prevent spending from other software with the keys. A successful file import therefore does not prove that every label was applied, that a frozen output is an on-chain property or that all metadata from the old application has been reconstructed. Read the target wallet's current documentation or inspect its supported import format, then review the result record by record.
A safer label-backup workflow
- Inventory without secrets. Note the wallet application and version, network, account or script type, derivation path and whether the wallet has imported keys or multisig policy. Never store mnemonics, private keys or passwords in labels. When sharing records, consider what addresses and their annotations reveal.
- Export from the original wallet. Use its documented label or wallet-data export. If it offers BIP329, confirm whether the export is plain text and where it is saved. Keep the original wallet file until the migration is complete.
- Protect the metadata file. Store it offline or in a controlled encrypted location. The file is not harmless merely because it lacks private keys; labels can identify people, purchases and balances. Do not email it unprotected or upload it to a support form.
- Restore the seed privately. Use the target wallet's official recovery process with the correct format, network, account and path. A controlled offline backup check is more useful than a web-based seed checker.
- Import and compare. Import the label file only after selecting the intended wallet. Rehearse first with fictional labels in a separate practice wallet; that does not verify your real backup. Then review the real records, notes and output status. Check that the expected public history is present independently of the labels.
- Retain a recovery map. Keep the format, path, network and metadata-export instructions with the backup plan, but separate secrets from descriptive records. Do not destroy the old wallet file or its metadata until every account and balance has been checked.
Where SeedAddress fits
SeedAddress deterministically generates a BIP39 mnemonic in the browser from the selected coordinates, input password, word list and word count. Locations and public addresses are not secret entropy. The method adds no random entropy; a 24-word result does not guarantee 256 random bits. SeedAddress does not generate wallet keys or addresses and does not create, import or recover label metadata.
If you use SeedAddress for study, preserve the exact deterministic inputs and an independent offline backup, and use only fictional labels such as practice wallet. Do not enter a real mnemonic, password, private key or wallet file into SeedAddress or any web checker. A practice-wallet exercise can teach the recovery steps; it does not verify the backup protecting real funds. Follow the original wallet's recovery and metadata-export procedures.