For a seed-phrase wallet, record the exact recovery words in their original order, keep the backup offline and private, and use the provider's supported check to confirm it. Anyone who obtains usable recovery material may gain access to the wallet. Never send it to support.

Know which recovery material your wallet uses

Seed phrase, recovery phrase, and wallet backup often refer to an ordered set of words used to recover access. However, formats and account coverage differ. Determine the format your actual wallet generated instead of assuming every word list works in every application.

Trezor documents BIP39 and SLIP39 backups, including different word counts and single-share or multi-share arrangements. Compatibility matters when planning a replacement device. A count of words alone does not establish that another wallet can recover the same accounts.

A local application password or device PIN can protect day-to-day access without replacing recovery material. If the device is lost, remembering only that local credential may not recreate the wallet. Write down the recovery plan separately from assumptions about logging in.

Some products offer recovery arrangements that use an account service or another design. If your wallet does, follow that documentation. This guide addresses the task of securing a phrase-based backup rather than assuming every wallet must produce the same secret.

Record accuratelyStore privatelyCheck safely
A useful backup must be accurate, protected, and checked through a documented recovery verification process.

Make an exact record without creating extra exposure

  1. Use the official setup or backup flow in a private setting. Check that no screen-sharing session, camera, or untrusted observer can capture the words.
  2. Record each word with its position. Write legibly and keep the original sequence. Do not translate, abbreviate, reorder, or replace a word with a synonym.
  3. Check the completed record against the wallet's confirmation instructions. Resolve an uncertain letter or missing position immediately while the legitimate setup process allows it.
  4. Keep the phrase out of photographs, screenshots, email, messenger conversations, and ordinary shared cloud folders. A convenient copy can become an unnoticed second location of the secret.
  5. Use the wallet's documented backup-check feature where available. For hardware products, respect the device-specific instructions about the approved input method.
  6. Only fund the wallet after you have a complete, usable backup and understand the procedure for recovering access.

Choose storage for both privacy and survival

Consider who can access the location and what could damage the record. Water, fire, accidental disposal, and relocation are different failure modes from theft. A storage plan should address the realistic conditions of your home and access needs.

A durable medium may reduce some physical damage risk, but it still needs to preserve the exact words and order. Verify what has actually been recorded after transferring it to another medium. A strong container does not correct a transcription error.

If you keep more than one complete copy, each additional location creates both redundancy and another place someone might obtain the secret. Assess access at every location. Avoid leaving an unprotected spare merely because the primary record is well secured.

Do not improvise a recovery scheme by splitting a word list into arbitrary fragments and hoping to remember the missing pieces. Supported multi-share systems have defined recovery rules. If you choose such a system, document its format and required shares according to the provider's instructions.

Keep enough nonsecret information to understand what the backup belongs to. Product, backup standard, and relevant account information can help future recovery. Store this reference thoughtfully so it helps you without unnecessarily revealing where the secret is kept.

Check recovery without turning a check into a leak

Use the provider's built-in verification or documented recovery-check procedure. A website offering to validate any seed phrase is not a safe substitute. The checker would receive the secret you are trying to protect.

Follow the distinction between a hardware device and its companion software. A prompt on a computer claiming that a device needs repair can be an impersonation attempt. Start instructions from the official application or documentation and verify the approved input path for your model.

A recovery check should be planned while you still have working access. Do not erase a funded wallet just to see whether an untested backup is correct unless you understand and can safely follow the provider's actual procedure.

If a check reports a problem, preserve existing access and investigate carefully. Identify whether the issue is word accuracy, order, format, an additional passphrase, or an account not covered by that backup. Random retries in unrelated apps can expose the material without solving the cause.

If your wallet supports an additional passphrase, learn exactly how it changes recovery. It can create a different wallet when entered differently. Losing or mistyping that separate secret can therefore produce a valid-looking empty account rather than an obvious error.

Maintain the backup when your setup changes

Moving to a new phone does not automatically require creating a new recovery phrase. Restoring an existing wallet and generating a new wallet are separate actions. Know which one you are performing before replacing an old device.

Likewise, a phrase may not cover every account displayed in an application. Separately imported keys, hardware-linked accounts, and other recovery systems can have their own requirements. Inventory those account types using the wallet's documentation.

When changing where the backup is stored, verify that the new location actually contains the complete readable record before retiring the previous arrangement. Keep the process private and avoid temporary digital copies made merely for convenience.

Plan what happens if you cannot access the location. A recovery method that survives technically but is inaccessible when needed can still fail its purpose. Any trusted-person or inheritance plan requires careful control of who can obtain spending authority and under what conditions.

If the phrase has been exposed to an untrusted party, making a cleaner copy does not revoke the old secret. Treat that as a compromise of the affected wallet and follow official guidance for moving assets to a securely generated replacement where appropriate.

Your ongoing goal is specific: the right person can recover the intended accounts, while unauthorized people cannot obtain the material that enables that recovery. Revisit the plan when the wallet, storage conditions, or people with access change.

Review the record periodically for legibility and physical damage without unnecessarily exposing it. The purpose is to verify the storage arrangement, not to repeatedly import the secret into additional software. If someone else gains access to the storage location, assess whether the recovery material may have been copied even when the original record remains present.

Reader questions

Should I put the phrase into a support ticket to prove ownership?

No. Support does not need the phrase to inspect public addresses or explain recovery instructions.

Is a perfectly copied phrase enough if I used an extra passphrase?

You may also need the exact additional passphrase. Follow the recovery requirements for the wallet and accounts you created.

Can I replace one word because someone saw only that part?

Changing the written record does not change the existing wallet. Do not edit the backup as a way to revoke exposed information.

Sources and further reading