A wallet backup must preserve the information needed to regain access to its funds. In a BIP 39 wallet, mnemonic words encode generated randomness and a checksum, and are then used to derive a seed. BIP 39 permits 12, 15, 18, 21, or 24 words. These words are not selected as a memorable sentence by the user. The mnemonic specification.
Words, seed, keys, and outputs
BIP 32 describes deriving a hierarchy of keys from a seed. The recovery words and the individual spending keys are therefore related, but they are not interchangeable labels for the same object. Hierarchical key derivation.
Not every wallet uses BIP 39, and mnemonic words are not a rule that Bitcoin nodes enforce. Restoration has to match the wallet’s actual backup format.
A passphrase is part of the derivation
BIP 39 allows an additional passphrase. A different passphrase produces a different seed, including when the difference is a typo. The specification does not provide a server that can reset a forgotten passphrase or identify the intended wallet. Passphrase behavior.
That passphrase is conceptually different from a local app PIN, which may only control access to a particular installation.
Why the words may not be the whole backup
Restored software also needs to find the right outputs. Script types and key derivation paths can differ between wallets. Output descriptors record such information explicitly; multisignature arrangements add the need to reconstruct the spending policy and participating public keys. Why descriptors exist.
A backup plan should follow the documentation for the specific wallet and include an understood recovery process. Storing every copy in one place leaves them exposed to the same loss; sharing secret material exposes spending authority. Bitcoin.org’s security guide discusses backup completeness and storage risks. Backup guidance.
This article explains the concepts. It does not need your recovery words, and none of this site’s experiments asks for them. Continue with multisig to see why wallet policy also matters.