Trezor Multi-share Backup divides one wallet backup into several different SLIP39 recovery shares and requires a chosen threshold to restore the wallet. A 3-of-5 setup, for example, survives the loss of any two shares while one stolen share is insufficient for recovery. This flexibility removes one physical point of failure only when the threshold, locations and recovery instructions are designed and tested correctly.
Last reviewed: September 30, 2026. Supported devices, firmware requirements, backup formats and Trezor Suite workflows can change. Confirm every critical step in current official Trezor documentation and on the trusted device display. Never enter recovery shares into a website or share them with support. This independent guide is educational and is not professional security or legal advice.
What is Trezor Multi-share Backup?
Multi-share Backup is a wallet recovery system based on SLIP39. Instead of one complete mnemonic being sufficient, the wallet creates several recovery shares and defines how many must be combined. The minimum required number is the threshold.
A share is not a fragment to type into an ordinary password field. It is a structured mnemonic with identifiers, recovery information and a checksum. Shares belonging to one set work together according to the configuration created by the Trezor.
SLIP39 and Shamir Backup
SLIP39 is the current name of the mnemonic sharing standard used by Trezor. Older documentation often calls the feature Shamir Backup because its threshold construction is based on Shamir’s Secret Sharing. In Trezor documentation, both names can refer to the same family of wallet backups.
Modern Trezor SLIP39 shares normally contain 20 words. Older formats and third-party descriptions may differ, so never infer compatibility from word count alone.
BIP39 versus SLIP39
| Feature | BIP39 backup | SLIP39 Multi-share Backup |
|---|---|---|
| Typical structure | One complete 12- or 24-word mnemonic | Several distinct recovery shares |
| Recovery requirement | One complete copy | Any valid combination meeting the threshold |
| Loss tolerance | Depends on duplicate full copies | Defined by total shares minus threshold |
| Theft risk | Every full copy controls the wallet | Fewer than threshold shares are insufficient |
| Changing backup structure | Usually requires a new wallet for a new mnemonic | Supported modern SLIP39 wallets can create a new backup set |
| Compatibility | Very broad | Requires explicit SLIP39 support |
Single-share and Multi-share SLIP39
A modern Single-share Backup is a 1-of-1 SLIP39 configuration: its one share can restore the wallet. Multi-share uses multiple shares with a threshold greater than one. Trezor identifies current Single-share backups with structural information; official documentation notes that the third and fourth words can appear as academic academic.
Do not type words into an online checker to identify the format. Use the device and official Trezor Suite guidance.
How thresholds work
| Setup | Shares required | Shares that can be lost | Main trade-off |
|---|---|---|---|
| 2-of-3 | Any two | One | Simple resilience, but two locations can recover |
| 3-of-5 | Any three | Two | Good redundancy with more administration |
| 4-of-6 | Any four | Two | Higher collusion threshold but harder recovery |
| 5-of-5 | All five | None | Every lost share causes permanent failure |
A 3-of-5 configuration does not require specific numbered shares. Any three shares from that same set can meet the threshold. Shares from unrelated sets cannot be mixed.
How to choose a threshold
Model both theft and loss. A low threshold improves availability but allows fewer compromised locations to restore the wallet. A high threshold resists collusion but can turn one disaster or unavailable person into permanent loss.
Ask:
- How many independent locations exist?
- Could one fire, flood or burglary affect several?
- How many custodians might become unavailable together?
- Could people holding enough shares cooperate prematurely?
- Can an heir identify the threshold and valid set?
- Can the owner retrieve enough shares during travel restrictions or an emergency?
Supported Trezor devices
Current Trezor documentation lists Multi-share Backup support for Trezor Safe 7, Safe 5, Safe 3 and Model T with compatible firmware. Model One uses BIP39 rather than the same Multi-share workflow. Firmware versions older than the required SLIP39 implementation may not restore newer sets.
Check the exact model and firmware before creating or testing a backup. Do not update a critical device until its existing backup has been verified.
Understand 12, 20 and 24 words
Trezor devices can use different defaults depending on model, setup date and chosen format. A 12- or 24-word backup is commonly BIP39. A current 20-word backup is commonly SLIP39 Single-share or Multi-share.
Word count alone does not reveal the wallet, passphrase or derivation path. Record the model, format, approximate setup date and one public address without writing sensitive words into a digital note.
How recovery shares are structured
Current 20-word SLIP39 shares contain identifiers and threshold information as well as encoded recovery data and a checksum. Trezor documentation explains that the first words help identify related shares and the final words contribute to error detection.
The checksum helps detect mistakes; it does not make a photographed share safe. A person collecting enough valid shares can restore the wallet without the original device.
Creating a new Multi-share Backup
- Use a genuine supported Trezor with current official Trezor Suite.
- Confirm the device backup status and firmware compatibility.
- Choose Multi-share Backup in the official setup workflow.
- Select total shares and threshold deliberately.
- Write each share in order on a separate durable medium.
- Confirm every word on the Trezor as requested.
- Label shares without exposing the wallet balance or full storage map.
- Store each share separately.
- Run Check backup before meaningful funds depend on the setup.
- Document a recovery procedure that reveals no share words.
Upgrading from Single-share Backup
Supported modern 20-word Single-share wallets can create a Multi-share backup through Trezor Suite without moving funds. The device uses the existing wallet secret to create a new valid recovery set.
Not every older backup can use this direct path. Trezor says 12- and 24-word BIP39 backups and older SLIP39 formats from before the newer standard may require a new wallet and onchain transfer instead. Follow the current upgrade guide for the exact device and backup date.
The old backup remains valid
Creating a new backup set does not change the wallet’s private keys. Therefore, the previous Single-share or Multi-share set can still restore the same wallet. It is not remotely revoked.
This is vital when upgrading: distributing five new shares does not improve theft resistance if an old complete Single-share remains in an insecure drawer. Conversely, destroying the old backup before validating the new set can remove the only proven recovery path.
A safe upgrade sequence
- Verify the existing backup on-device.
- Confirm the format is eligible for direct upgrade.
- Create the new Multi-share set through Trezor Suite.
- Check each share and the complete threshold recovery logic.
- Record one known public address for verification.
- Distribute the new shares to planned locations.
- Audit every copy of the old backup.
- Only then decide whether to retain or securely destroy the old set.
Changing the threshold or number of shares
Shares cannot simply be appended to an existing set and its threshold cannot be edited in place. A supported wallet creates a new backup configuration. The shares in that new set are not interchangeable with the old shares.
After verification, update custodians and recovery documentation. Track old shares until they are securely destroyed or intentionally retained.
Where to store recovery shares
Separate locations should have genuinely independent risks. Three drawers in one house are three hiding places, not three disaster domains.
Possible locations include a secured home location, a bank box, a professional custodian or a trusted person with clear instructions. Consider fire, flood, political access, inheritance rules and the possibility that a custodian becomes unavailable.
Paper versus metal
Paper is easy to write and inspect but vulnerable to water, fire and decay. Metal can improve physical durability but must support the correct number and order of SLIP39 words.
Verify that a product fits the actual 20-word share and permits unambiguous spelling. A durable plate containing an incorrectly recorded word is still an invalid backup.
How to label shares safely
A label should help an authorized recovery without advertising “crypto wallet worth $500,000.” Use a private inventory code, set identifier and share number where useful. Keep the map explaining locations separately from the shares.
Do not add the passphrase, device PIN and complete threshold instructions to every share. That can collapse several security layers into one object.
Never digitize recovery shares casually
Do not photograph shares, email them, place them in ordinary cloud storage or type them into a password manager. Digital copies can propagate through backups, thumbnails, sync services and compromised devices.
Support needs public addresses, device model, firmware version and error text—not recovery words.
Check backup in Trezor Suite
The official Check backup workflow lets the Trezor verify recovery information without exposing the wallet secret to the computer. Begin from verified Trezor Suite and read every device prompt.
Test shares after creation and periodically after moving physical storage. Never use a website that asks users to type all shares to confirm them.
Recovering with multiple shares
- Obtain enough shares from the same backup set to meet the threshold.
- Use a genuine compatible Trezor in the official recovery workflow.
- Enter each share on the trusted device as instructed.
- Check that identifiers and progress match the expected set.
- Complete recovery only after threshold shares are accepted.
- Apply any separate passphrase exactly.
- Add the relevant accounts and compare a known public address.
Staggered recovery
Supported Trezor recovery can accept shares across different sessions, allowing the device and custodian to travel between locations without bringing every share together. Trezor states that an entered share cannot later be read back from the device by someone who steals it.
Staggering reduces co-location risk but adds logistics. Maintain physical control of the Trezor, verify firmware and never let a custodian type a share into a computer.
If one share is lost
If the remaining shares still meet the threshold, the wallet remains recoverable. Treat an unexplained loss as possible compromise, not merely damage.
Create a new backup set while the wallet and threshold remain accessible, verify it, distribute the replacements and retire the old shares. A lost share cannot be revoked within its original set.
If too many shares are lost
If remaining shares fall below the threshold and no other valid backup exists, they cannot reconstruct the wallet. Trezor cannot override the mathematics or recover missing words.
If the original device still works, create a new valid backup or move assets to a newly backed-up wallet before device failure. Do not reset the only working Trezor.
Shares from different sets cannot be combined
A share from an old 2-of-3 set and shares from a new 3-of-5 set do not make a hybrid recovery. Set identifiers prevent unrelated shares from reconstructing a secret.
Keep inventory records clear after backup changes and securely dispose of obsolete material only after verification.
Multi-share Backup and passphrases
SLIP39 protects the wallet backup. An optional passphrase derives another wallet on top of the recovered secret. Even a correct threshold of shares opens the wrong or empty accounts if the intended passphrase is missing or mistyped.
The passphrase becomes its own single point of failure. Record it exactly and store it separately according to a deliberate plan. Our guide to Trezor passphrase wallets explains that recovery boundary.
SLIP39 versus multisig
| Question | SLIP39 Multi-share | Multisig |
|---|---|---|
| What is divided? | Backup of one wallet secret | Signing authority across independent keys |
| Daily spending | One restored/active signer can sign | Multiple signers approve according to policy |
| Blockchain awareness | None; backup structure is offchain | Wallet script or account enforces several keys |
| Main purpose | Resilient recovery | Distributed transaction authorization |
SLIP39 can back up one key used in a multisig wallet, but it does not replace the other independent keys or wallet configuration.
Inheritance planning
Heirs need a non-secret explanation of the threshold, locations or custodians, compatible recovery method and any separate passphrase. They do not necessarily need enough shares before the intended event.
A plan can distribute shares between family, a legal professional and secure locations so no single party can act alone. Review local inheritance and custody law with a qualified adviser.
Testing recovery safely
A second compatible Trezor allows recovery testing without wiping the only working device. Enter threshold shares on-device, apply the passphrase if any and compare a known public address. No funds need to move.
If a spare device is unavailable, use Check backup. Do not manufacture a crisis by resetting the only signer before the new set has been validated.
Common mistakes
- Choosing all-of-all and accidentally eliminating redundancy.
- Storing every share in one building.
- Photographing shares for convenience.
- Mixing shares from old and new sets.
- Assuming the old Single-share becomes invalid after upgrade.
- Destroying the old backup before checking the new one.
- Giving one person enough shares for unilateral access.
- Forgetting that a passphrase is separately required.
- Confusing Multi-share with multisig.
- Attempting direct upgrade from an ineligible older format.
- Entering words into an online verification tool.
- Leaving heirs with shares but no recovery context.
Multi-share Backup checklist
- The device and firmware support the intended SLIP39 format.
- The threshold balances theft and loss realistically.
- Every share is complete, ordered and legible.
- Locations do not share one disaster risk.
- No digital photographs or plaintext files exist.
- The backup has passed the official check.
- A known public address is documented separately.
- Old backups remain tracked until deliberately retired.
- Any passphrase has an independent recovery plan.
- Heirs or emergency custodians understand the procedure.
Frequently asked questions
What is Trezor Multi-share Backup?
It is an SLIP39 backup divided into several recovery shares. Any valid combination reaching the chosen threshold can restore the wallet.
How many shares can Trezor create?
Current Trezor documentation allows up to 16 shares in a backup configuration. Choose the number for a real storage plan, not simply the maximum.
What does 3-of-5 mean?
Five shares exist and any three from the same set can recover the wallet. Up to two can be unavailable.
Can one Multi-share recovery share access my funds?
Not when the threshold is greater than one. A modern Single-share 1-of-1 backup is different because its only share is complete for recovery.
Can I add another share later?
Not to the existing set. Create a new backup configuration, verify it and then manage the old shares deliberately.
Does upgrading invalidate my old backup?
No. Trezor states that the old valid backup can still restore the wallet. This provides fallback but also remains a theft risk.
Can I upgrade a 12- or 24-word backup directly?
Current direct upgrade targets compatible modern 20-word SLIP39 backups. Older BIP39 or legacy formats may require a new wallet and transfer.
What happens if I lose one share?
If the remaining shares meet the threshold, recovery still works. Consider replacing the set if the share may be compromised.
Is SLIP39 the same as multisig?
No. SLIP39 distributes recovery of one wallet secret. Multisig requires several independent keys to authorize transactions.
Can I use a passphrase with Multi-share Backup?
Yes, but it remains separately required. Losing it can make the wallet unrecoverable even with enough valid shares.
Should I keep shares in a password manager?
Trezor recommends keeping wallet backups offline. Do not photograph or type recovery shares into internet-connected software.
Final perspective
Trezor Multi-share Backup can replace one fragile master copy with a recovery policy that tolerates loss and resists theft of an individual share. The benefit comes from the whole design—not merely creating more word lists.
Choose a realistic threshold, separate physical risks, verify the set and track every older backup. A sophisticated threshold cannot repair unclear records, co-located shares or a missing passphrase.
Official sources and further reading
- Trezor — Multi-share Backup
- Trezor — Upgrading to Multi-share Backup
- Trezor — Recovering with Multi-share Backup
- Trezor — SLIP39 FAQs