Can You Translate a BIP39 Seed Phrase into Another Language?
Learn why translating a BIP39 phrase does not preserve a wallet and which language, inputs and offline backup you need for recovery.

Do not translate a BIP39 seed phrase as if it were an ordinary sentence. The words are not a description of one secret that can be switched into another language later: they form exact text that the BIP39 process turns into a binary seed. Changing the words changes that text and therefore normally changes the derived wallet.
If you need to restore a wallet, keep the phrase exactly as it was created and use a recovery flow that supports it. A wallet interface can be in Spanish while its wordlist is English, Japanese or another BIP39 list. The language of the menus and the language of the mnemonic are separate settings.
What a BIP39 phrase represents
The BIP39 specification describes a mnemonic as a human-readable way to carry computer-generated entropy. The process takes the entropy and its checksum, concatenates their bits and splits them into groups of 11 bits. Each group becomes an index from 0 to 2047 that points to a position in a 2048-word list. The ordered result is the phrase.
This means that a word is not selected for its meaning. Its value in the phrase is the position it occupies in the particular list and the order in which it appears. Two words that look equivalent in a dictionary can have entirely different positions, or one of them may not belong to the BIP39 list that the wallet expects.
Why the same entropy does not preserve the same seed
There are three layers to keep separate:
- Entropy and checksum: the initial bits that are encoded into indexes.
- Mnemonic: the words selected from one wordlist in one exact order.
- BIP39 binary seed: the result of converting the mnemonic text with PBKDF2.
The same entropy can be encoded with another list and produce different words for the same indexes. That can be useful when an application creates the phrase from the beginning with a compatible language. It does not turn the phrase you already have into an interchangeable translation. The Trezor reference implementation shows the boundary: to_mnemonic looks up words by indexes in a list, while to_seed normalizes the mnemonic and runs PBKDF2-HMAC-SHA512 over that mnemonic text.
The consequence is that BIP39 uses normalized text, not decoded entropy, to create the seed. Re-encoding the same indexes with another list can preserve entropy and checksum, but if the normalized text changes, expect a different seed and wallet. The list's name is not a PBKDF2 input: identical NFKD text and passphrase produce the same result, even when lists share words. Changing the language does not guarantee recovery of the original wallet.
A manual translation can fail in several ways. A translated word may not exist in the chosen list, so the wallet cannot recognize it. The translated sequence may have an invalid length or checksum. In the least obvious case, it may happen to be a valid sequence, but it will derive another seed and another wallet. An application accepting the input does not prove that the original wallet was preserved.
NFKD is not translation
NFKD is a technical text normalization. The specification and the reference implementation apply it to the mnemonic and passphrase before PBKDF2 runs. It helps handle some Unicode character representations consistently, but it does not turn an English word into its Spanish equivalent or interpret a sentence.
This distinction matters especially for lists with non-Latin characters or particular separators. Normalization does not mean removing accents or correcting mistakes. Do not change words, letter case or separators yourself: keep the original words, their order and the format expected by compatible software.
The wallet interface language is separate
A wallet can show its buttons in Spanish and still expect an English mnemonic. Another wallet may offer a localized list when creating a backup but import it differently across versions. BIP39 discourages generating mnemonics with non-English lists because wallet compatibility may be more limited; that guidance does not authorize converting an existing phrase.
The Trezor wallet-backup guide treats backup words as the data used to recover a wallet. For recovery, follow the documentation from the device or application manufacturer. Select the language or list that matches the original backup if the flow asks for it, and verify the restore without uploading the words to a website.
Do not confuse a BIP39 mnemonic with the optional passphrase either. The phrase and its passphrase are separate inputs; translating one does not compensate for changing the other. The difference between a phrase, passphrase and SeedAddress password explains why an application password cannot replace backup words.
What changes when you choose a language in SeedAddress
SeedAddress generates the mnemonic in the browser from the selected coordinates, a password, a language and a word length. Its v1 implementation preserves a precision-9 geohash and calculates HMAC-SHA-256 using the UTF-8 hexadecimal text of the password's SHA-256 digest as its key. It then encodes the bits for the selected length as words from the chosen BIP39 list. In a new session, the interface language may suggest an initial language; always confirm the phrase-language selector rather than relying only on the site's visible language.
The language is therefore a real recovery input. If you keep the exact coordinates, password and length but choose another list, SeedAddress preserves the encoding bits and may show different words. When entered into a wallet, the later conversion to a seed depends on the resulting normalized text. You should not treat two languages as interchangeable translations of one backup.
SeedAddress does not add new random entropy because the input is a particular place, and it does not create addresses, xpubs or private keys. A 24-word phrase also does not guarantee 256 bits of security if its source was deterministic or predictable. The inherited five-character minimum is a compatibility check, not a recommendation for a new password. Read the SeedAddress recovery guide and the difference between BIP39 lengths and entropy for the relevant limits.
What to do with an existing backup
If you already have a phrase, keep an offline copy and do not rewrite it as a translation. Document the recovery manufacturer or software and the wordlist language if known, without entering the words into a connected application. Keep any configured BIP39 passphrase separately and offline too. Preserve every exact input required by a deterministic method: SeedAddress recovery depends on its inputs, not only the visible place name.
To check a backup, use a trusted offline device or procedure and follow the official documentation. Do not paste the phrase into a translator, web checker, chat or tool that promises to convert it. If you believe the words were exposed, follow the response plan for a compromised phrase to move funds to a new wallet initialized with random entropy; translating them neither revokes nor protects the original wallet.