Skip to content
Jolly Ledger Ready

Backup & recovery

12, 20 or 24 words: understand wallet backup formats

By Jolly Ledger editorial · Published · Reviewed · 4 min read

Short answer

Word count is a clue to the backup format, not a complete recovery specification. Twelve and twenty-four words commonly indicate BIP-39; twenty words commonly indicate SLIP-39, which supports single-share and multi-share backups.

A wallet backup is structured data represented as words. The word list, encoding rules and recovery method matter alongside the length. A replacement device advertising “seed recovery” is not enough information: it must support your actual standard and the features used by your wallet.

Twelve and twenty-four words commonly mean BIP-39

BIP-39 describes how computer-generated randomness and a checksum become a mnemonic. Twelve words encode 128 bits of initial entropy, while twenty-four encode 256 bits. The standard also permits fifteen, eighteen and twenty-one words. It does not define a twenty-word mnemonic.

Those figures describe the format, not a guarantee about storage or handling. A correctly generated twelve-word BIP-39 backup is not inherently a defective backup that needs replacing. A photographed twenty-four-word backup can be exposed despite its greater entropy. Choosing words yourself or padding a phrase with extra words is not a valid way to improve it.

Twenty words commonly point to SLIP-39

SLIP-39 uses a different word list and encoding scheme to support secret-sharing recovery. Common implementations use twenty-word shares for a 128-bit master secret; longer secrets can use longer shares. A share includes information needed to interpret the backup, not just a fragment of a BIP-39 sentence.

Crucially, a twenty-word backup may be a single-share backup. It is not automatically one of several required cards. In a multi-share arrangement, the configured threshold determines how many compatible shares are needed. Two photocopies of one share do not count as two distinct shares toward that threshold.

This table is a starting point, not a detector for every wallet ever made. Other schemes exist. Check the documentation for the device or wallet that created the backup. Do not send the words to a support agent to ask which format they resemble.

Compatibility extends beyond the mnemonic

Support for a backup standard does not promise that every asset, network or account will immediately appear in one application. Account discovery can depend on derivation paths, script types and which account index was used. An optional passphrase must also be available exactly as originally used.

Keep those details in private recovery notes, separate from the words themselves. For threshold arrangements, distinguish multisig from multi-share backups: one governs signing and the other recovery. Neither label alone tells you everything needed to restore the intended accounts.

Before changing devices or backup schemes, use an official backup check where supported and plan a recovery rehearsal. Do not erase a working wallet to discover whether an unfamiliar format is compatible. Resolve uncertainty with official documentation while access still works.

Sources

  1. BIP-39: Mnemonic code for generating deterministic keys — Bitcoin BIPs
  2. SLIP-0039: Shamir’s Secret-Sharing for Mnemonic Codes — SatoshiLabs SLIPs
  3. Understanding Trezor wallet backups: 12, 20 or 24 words — Trezor

Reported facts are attributed to their sources. Spotted an error? Read our corrections approach.

Turn this into a preparation plan

Answer 16 calm questions about your setup. Get findings, scenario walkthroughs and a family briefing — on your own device, no account, no wallet connection, no recovery words.

Start your free checkupThe full preparation pack is free during launch beta. Planned one-time price: €39.