A seed phrase backup should be created as a controlled security procedure, not as a hurried note made after a wallet is already funded. The first setup determines whether the wallet can be recovered after device loss and whether someone else can steal it from a photograph, cloud copy, discarded draft or exposed storage location. This guide walks through a complete offline backup ceremony: preparing the environment, recording the words in order, verifying the copy, separating duplicates, testing the recovery plan and removing temporary traces.

Last reviewed: October 19, 2026. Wallet interfaces, backup formats and recovery procedures can change. Follow the current instructions shown by the official wallet or hardware device. This independent guide is educational and is not financial, legal or professional security advice.

Quick answer: generate the recovery phrase only through a verified wallet, record every word and position offline, confirm the copy using the wallet’s built-in process, store protected copies in separate locations and test the recovery method before meaningful funds depend on it. Never type the phrase into a website, chat, cloud note or unverified application. If anyone may have seen or captured it, treat the wallet as compromised and migrate assets to keys generated through a fresh trusted setup.

1. What a seed phrase backup actually protects

A recovery phrase is not a reminder for an account password. In compatible deterministic wallets, it is the human-readable input from which the wallet can recreate a hierarchy of private keys and addresses. A correct backup can restore control when the original phone or hardware wallet is lost, damaged, reset or replaced. An incorrect or incomplete backup may look reassuring for years and fail only during an emergency.

The same property that enables recovery creates the main risk: someone who obtains the words can often restore the wallet elsewhere without possessing the original device or knowing its unlock PIN. The backup is therefore both a recovery tool and a transferable form of control.

2. Recovery phrase, private key, PIN and app password are different

Item Purpose What happens if it is exposed or lost
Recovery phrase Recreates a wallet’s key hierarchy Exposure can compromise the wallet; loss can prevent recovery
Private key Controls a particular blockchain account Exposure compromises that account
Device PIN Unlocks a particular hardware device Does not normally restore the wallet on another device
App password or biometrics Restricts local access to an application Does not neutralize an exposed recovery phrase
BIP39 passphrase Changes the wallet derived from a compatible mnemonic Every different entry can lead to a different valid wallet

Record which recovery format and optional components your setup uses. Do not assume that remembering the app name is enough to reconstruct the wallet years later.

3. Complete the backup before depositing meaningful value

The safest moment to establish recovery is before the wallet receives assets. If the backup fails during verification, little or nothing needs to be moved. Funding first creates pressure to accept an uncertain copy and makes troubleshooting more dangerous.

  1. Install or initialize the verified wallet.
  2. Generate recovery material through its official setup.
  3. Record and verify the material offline.
  4. Plan the storage locations.
  5. Test with a small receive transaction.
  6. Only then consider transferring a larger balance.

4. Choose the wallet and backup format before the ceremony

Different wallets may use BIP39, SLIP39, wallet-specific mnemonics, encrypted backup files, descriptors or multisignature configurations. A sequence of 12 or 24 words is common, but it is not universal. Never convert one format into another with a random online tool.

Read the manufacturer’s official recovery documentation first. Determine the word count, whether an optional passphrase is supported, whether accounts use unusual derivation paths and whether the backup needs an additional configuration file. This article focuses on human-readable recovery phrases but does not imply that every wallet uses the same method.

5. Verify the application, device and setup path

Download wallet software through the developer’s official website or a verified app-store listing reached independently. Avoid sponsored search results, links in direct messages and “support” pages that ask for recovery words. For a hardware wallet, follow its authenticity checks and initialize it yourself rather than accepting a phrase supplied on a card.

Stop immediately if: packaging contains a preprinted recovery phrase, a seller supplies the words, a website asks to generate them, or the device instructs you to type its newly generated phrase into an ordinary web form. A legitimate recovery workflow should be confirmed against the manufacturer’s current official instructions.

6. Prepare a private offline workspace

Select a place where another person cannot observe the screen or paper. Remove unnecessary cameras, smart displays and voice assistants from view. Close blinds if the workspace is visible from outside. Do not perform the procedure during a video call or in a shared office, café, hotel lobby or airport.

Prepare the approved recording medium, a reliable pen or pencil, and numbered spaces for the exact word count. If a metal medium will be used later, first follow the wallet’s normal confirmation flow with a temporary offline sheet, then transfer carefully without exposing the words to a connected engraving service.

7. Reduce connected-device exposure

A hardware wallet should generate and display its phrase on the trusted device screen. Do not retype those words into a computer merely for convenience. A software wallet necessarily operates on its host device, so reduce risk by updating the operating system, removing suspicious applications and avoiding screen-sharing or remote-access software during setup.

  • Do not photograph the words.
  • Do not use a screenshot.
  • Do not paste them through a clipboard manager.
  • Do not dictate them to a voice assistant.
  • Do not print them using a networked or commercial printer.
  • Do not scan them to “make a safe copy.”

8. Let the wallet generate the words

BIP39 describes encoding computer-generated entropy as a mnemonic sentence. It is not an invitation to choose memorable words, quote a song or rearrange a phrase found online. Human-created sentences are predictable and may not contain a valid checksum.

Use the entropy generation method provided by the verified wallet or hardware device. Advanced manual entropy procedures require expertise and are outside the scope of a first backup. Adding improvised dice rolls or substituting preferred words can make a standard recovery procedure invalid.

9. Confirm the exact word count and language

Before writing, count the numbered spaces. BIP39 permits several mnemonic lengths, while individual wallets commonly use 12 or 24 words. SLIP39 shares may use a different length. The number alone does not identify the format, so note the wallet and format separately without placing secret words in that metadata record.

Preserve the original language and spelling. Do not translate words. BIP39 implementations are most consistently interoperable with the English list, but the correct action is to preserve exactly what the wallet generated and follow its supported recovery procedure.

10. Record one word in each numbered position

Write slowly and keep every word aligned with its number. The order is part of the secret; an unordered collection is not a usable backup. Use clear lowercase block letters and leave enough space to correct a transcription before final storage.

Read each word directly from the trusted source, write it once and compare it immediately. Avoid memorizing groups and then writing from memory. If interrupted, stop and restart the comparison from the first word rather than assuming where the interruption occurred.

11. Resolve similar or unclear words immediately

Mnemonic wordlists are designed to reduce ambiguity, but handwriting can still turn one word into another. Pay particular attention to letters such as a, o, u, m, n, c and e. If the wallet permits reviewing the phrase during setup, correct unclear writing before completing the ceremony.

Do not use an online “seed checker.” A checksum can detect some transcription errors, but submitting the entire phrase to a website exposes the wallet. Use the device-native verification workflow or a deliberately controlled recovery test described by the wallet provider.

12. Perform a first word-by-word comparison

After writing all words, compare the sheet against the source from position 1 to the final position. Then perform a second pass in reverse order. The reverse pass prevents the reader from skimming a familiar sentence and overlooking a duplicated, omitted or shifted word.

Check Question
Count Does the copy contain the expected number of words?
Order Does each word match its numbered position?
Spelling Is every word clearly readable?
Duplicates Is a repeated word genuine rather than an accidental copy?
Format Is the wallet type and backup standard known separately?

13. Use the wallet’s built-in confirmation

Many wallets ask the user to select or re-enter particular words during initial setup. This step confirms that a copy was made, but it may sample only part of the phrase. Complete it carefully and never allow browser autofill or a password manager to capture the input.

A successful confirmation proves that the selected words were entered correctly at that moment. It does not prove the sheet will remain available after a fire, theft, relocation or years of deterioration. Storage and recovery testing remain separate responsibilities.

14. Understand what checksum validation does not prove

A valid BIP39 checksum can show that a word sequence has a structurally valid relationship, but it does not prove that the phrase belongs to the intended wallet. A different valid phrase can derive a completely different wallet. An optional passphrase can also produce a different valid set of addresses without showing an error.

The strongest practical confirmation combines correct transcription with a wallet-native backup check and comparison of a known public receiving address after a controlled restore. The separate One Crypto Library verification guide covers this process in greater depth.

15. Decide whether a second copy reduces or increases risk

One copy creates a single point of failure. Two copies can survive loss of one location, but they create two places from which the wallet might be stolen. The right decision depends on realistic fire, flood, burglary, access-control and relocation risks.

For many individual users, two well-protected copies in independent physical locations are more resilient than one. “Independent” means that one incident should not reach both. Two envelopes inside the same safe do not provide geographic redundancy.

16. Create the duplicate without digital copying

If a second copy is appropriate, transcribe it directly while the verified source or confirmed first copy is securely available. Compare every numbered position. Do not use a phone photograph as an intermediate copy, and do not send the phrase to a printer.

After both copies are verified, expose only one at a time during handling. This reduces the chance that a visitor, camera or accidental photograph captures both locations or labels together.

17. Choose paper, metal or another supported medium deliberately

Paper is inexpensive, easy to inspect and easy to destroy. Metal can improve resistance to heat, water and crushing, but quality, marking depth and corrosion resistance vary. Encrypted digital media adds password, device and long-term readability dependencies. SLIP39 changes the recovery model and requires compatible tools.

This first-setup guide does not declare one medium universally best. Choose a method whose creation, inspection and recovery procedure you understand. The separate seed backup comparison examines paper, steel, microSD and multi-share recovery without collapsing them into one recommendation.

18. Separate the backup from the wallet device

Storing the recovery phrase beside the phone or hardware wallet lets one theft, fire or search expose both. Separation should protect against the incidents relevant to your environment. A home safe may protect against casual discovery but can still share the same fire, flood or forced-access event as the device.

A secondary location must remain legally and practically accessible to the owner. A location that cannot be reached during an emergency is not a complete recovery plan. Consider access hours, identification requirements, travel restrictions and whether a trusted person can act if the owner is incapacitated.

19. Label without advertising the secret

A backup needs enough context to be recognized years later, but obvious labels such as “Bitcoin seed — main wallet” attract attention. Use a private inventory code that only the recovery plan explains. Never write the storage address of copy B on copy A.

Non-secret metadata can include the creation date, wallet family, expected word count, backup format, copy identifier and last inspection date. It must not include the recovery words, passphrase or precise second location in an online spreadsheet.

20. Treat an optional passphrase as another critical secret

Under BIP39, every passphrase produces a mathematically valid wallet. A typo does not generate a simple “wrong password” warning; it can open an empty wallet with different addresses. If the intended wallet uses a passphrase, recovery requires both the mnemonic and the exact passphrase.

Do not add a passphrase casually during a first setup. It can improve separation when managed correctly, but forgetting one character can permanently hide the intended accounts. Store it according to a deliberate plan, normally separate from the mnemonic, and document that a passphrase exists without exposing both components together.

21. Record a non-secret recovery map

A recovery map helps a future authorized user understand what must be recovered without revealing the secret itself. It can list the wallet type, backup format, device model, relevant networks, whether a passphrase or multisignature configuration exists and where official instructions can be found.

Keep public addresses or wallet fingerprints where appropriate. These allow a restored wallet to be checked against the intended account without exposing private keys. Do not place seed words, PINs or full passphrases in the map.

22. Test the first receiving address with a small amount

After setup, obtain a receiving address through the wallet and verify it on the trusted display when supported. Send a small test amount on the correct network. Confirm that the transaction appears and that the address matches the recorded public reference.

A receive test does not validate every recovery detail, but it establishes a known address and reduces the risk of funding the wrong wallet or network. Do not send the full intended balance merely because the interface displays a plausible address.

23. Plan a recovery test without destroying the only working copy

A robust test recreates the wallet in a supported, controlled environment and confirms a known public address. Do not wipe the only initialized device while it is the sole means of accessing funds. Use the manufacturer’s backup-check feature, a dedicated spare device or another procedure explicitly supported by the wallet.

Never type the phrase into a general website or unknown application for testing. A test that leaks the secret has failed even if it displays the expected address. For detailed verification methods, use the related backup-verification article.

24. Remove temporary traces after verification

Once permanent copies have been checked and stored, account for every temporary sheet, practice plate, packaging note and discarded envelope. Destroy drafts so the words cannot be reconstructed from a bin or recycling container. Clean the workspace without photographing the result.

If the phrase was ever entered on a connected computer, copied to a clipboard, uploaded, printed remotely or shown during screen sharing, do not assume deleting the file removes every copy. The safer response is to create a new wallet through a clean verified procedure and transfer assets to its new addresses.

25. Do not place the phrase in ordinary online storage

Email, cloud notes, chat history and photo libraries are designed for synchronization and convenience. They may create copies on multiple devices, backups and provider systems. Encryption can reduce some risks but also adds credentials and recovery dependencies that beginners may misunderstand.

An offline seed backup should remain offline. A password manager is valuable for unique account passwords and recovery codes, but storing the only cryptocurrency recovery phrase there concentrates access in one online vault. If an advanced encrypted digital backup is considered, it requires a separate threat model and should not be improvised during first setup.

26. What to do if someone saw or photographed the phrase

Assume that a full visible phrase may have been copied. Changing the wallet PIN or application password does not change the underlying keys. Create a new wallet with independently generated recovery material in a clean environment and move assets to addresses controlled by that new wallet.

  1. Do not announce the suspected exposure publicly.
  2. Prepare and verify a new wallet.
  3. Transfer the most valuable assets with correct network fees.
  4. Move remaining tokens and NFTs that justify the cost.
  5. Revoke or abandon old dApp relationships as appropriate.
  6. Retain non-secret transaction records for accounting.

27. What to do if one word is unclear

If the wallet is still accessible, do not guess online. Use its official backup-check function or create and verify a replacement backup according to the provider’s procedure. Compare the unclear word with the relevant official wordlist without entering the rest of the phrase.

If the device is unavailable, preserve the original medium and avoid repeated handling. A damaged but partially readable backup may require specialist recovery practices. Never send photographs of it to strangers claiming to provide support.

28. What to do if the backup is lost but the wallet still works

Treat the functioning wallet as a temporary opportunity, not proof that recovery is safe. Create a fresh independently backed-up wallet and transfer assets while access remains available. Simply writing down a phrase displayed by an unknown export tool may not cover every account or format.

Start with a small test transfer, verify the new destination and allow for native gas or network fees. Document the migration so that the old and new addresses are not confused later.

29. Inspect the backup without unnecessarily exposing it

Physical media can fade, corrode, warp, become wet or disappear during a move. Schedule a periodic inspection appropriate to the material and location. Confirm presence, tamper evidence and readability without photographing or reading the words aloud.

Record the inspection date and result separately using the copy identifier. An inspection log should say that copy A was present and legible, not reproduce its contents.

30. Revisit the plan after major changes

Review the recovery plan after changing wallets, adding a passphrase, adopting multisignature, moving home, changing legal arrangements or transferring the main balance to new keys. A backup can remain physically perfect while becoming operationally obsolete.

Do not overwrite an old backup until the new wallet has been created, verified, funded and recoverably documented. During migration, label old and new copies clearly so that an emergency does not restore the wrong wallet.

31. Common first-backup failures

Failure Why it matters Safer action
Phrase supplied in the package Another party may already know it Initialize the verified device yourself with fresh keys
Photo stored on a phone It may sync or leak through applications Create a new wallet if exposure cannot be ruled out
Words lack numbers Correct order may be unrecoverable Record every word in a fixed numbered position
Both copies share one safe One incident can destroy or expose both Use genuinely independent locations
Backup stored with device Theft can capture device and recovery path Separate them physically
Untested passphrase A typo opens a different wallet Verify a known address through a controlled restore
Online seed checker The phrase may be transmitted to an attacker Use official device-native verification

32. First seed phrase backup checklist

  • The wallet application or device was obtained from a verified source.
  • The recovery material was generated by the wallet, not selected by a person.
  • No preprinted or seller-provided phrase was accepted.
  • The workspace was private and free from unnecessary cameras.
  • Every word was recorded offline in its numbered position.
  • The word count, spelling and order were checked twice.
  • The wallet’s built-in confirmation was completed.
  • The backup format and optional passphrase requirement are understood.
  • Duplicate copies, if used, occupy independent protected locations.
  • The wallet device and recovery phrase are not stored together.
  • A known receiving address and small test transaction were verified.
  • A safe recovery-test method exists.
  • Temporary drafts and digital traces were removed.
  • A non-secret recovery map and inspection schedule exist.

33. Frequently asked questions

Should I create my own memorable seed phrase?

No. Use the recovery material generated by a verified wallet. Human-selected words are predictable and may not conform to the required format.

Can I photograph my phrase and delete the photo later?

This is unsafe because the image may be synchronized, cached, backed up or recovered. If a phrase has been digitally exposed, migrating to newly generated keys is safer than relying on deletion.

Is one paper copy enough?

One copy avoids duplication but creates a single point of failure. Whether to maintain a second copy depends on the risk of destruction, theft and unauthorized access at each available location.

Can I store the phrase in a password manager?

For a basic offline backup plan, keep it offline. Placing it in an online vault adds account, device and synchronization risks. Advanced encrypted backup designs require separate analysis.

Does a valid checksum prove it is my wallet?

No. It can indicate a structurally valid phrase, but another valid phrase or different passphrase may derive an entirely different wallet. Confirm a known public address through a controlled method.

Should I test recovery by resetting my hardware wallet?

Do not reset the only working device when it is the only access path. Prefer an official backup-check feature, a supported spare device or another controlled method described by the manufacturer.

Do I need to back up every receiving address?

Modern deterministic wallets can normally recreate many addresses from the correct recovery material, but wallet formats differ. Confirm how the specific wallet handles accounts, derivation paths and additional configuration.

Related One Crypto Library guides

Official standards and wallet-security resources

Use first-party specifications and manufacturer documentation for the current recovery workflow. Never enter a real recovery phrase into a page reached from an article or search advertisement.

Key takeaway: the first backup is successful only when it is accurate, private, recoverable and protected against realistic loss. Generate it through a verified wallet, preserve every word and position offline, verify a known address, separate copies thoughtfully and replace the wallet if the phrase may have been exposed.