Are Electrum seed phrases BIP39?
A 12-word phrase does not identify its format. Learn to distinguish native Electrum seeds from imported BIP39 and preserve the recovery details that matter.

Not necessarily. A 12-word phrase can look like BIP39 and still be a native Electrum seed. Electrum uses its own version system for native seeds from version 2.0 onward; BIP39 uses entropy, a checksum and a word list with a different derivation. Familiar words, a 12-word length or an app accepting the phrase does not identify the format by itself. Electrum's official documentation says it does not generate BIP39 seeds, although the current program does support restoring BIP39 seeds as a separate mode.
Identify where the backup came from, which mode created it and which derivation path it needs. That prevents restoring a valid phrase into a different wallet and assuming the funds have disappeared. For example, a BIP39 backup created on another device and later imported into Electrum retains its BIP39 format; the most recent app does not turn it into a native Electrum seed.
Two formats that can look alike
BIP39: words that encode entropy and a checksum
In BIP39, a random source supplies the initial entropy. A checksum is added, and the result is split into 11-bit groups that select words from a 2048-word list. This produces standard lengths such as 12, 15, 18, 21 and 24 words. The BIP39 specification also defines how the mnemonic and an optional passphrase become binary seed material.
The list and checksum can validate a BIP39 phrase, but they do not tell you which wallet, network, account, script or derivation path will be used next. The same BIP39 phrase can lead to different addresses when restored with different paths or output formats. Preserve those wallet details with the backup; the word count cannot replace them. SeedAddress's guide to seed phrase length and entropy also explains why 24 words do not turn a predictable input into 256 bits of random entropy.
Electrum: a version is part of the format
Native Electrum seeds do not rely on validating a BIP39 checksum. Electrum's seed version documentation describes deriving a version from an HMAC of the normalized phrase. That version tells the software which derivation to follow and lets it check that the phrase belongs to a registered seed type, but recognizing a type does not prove that it is your original wallet or preserve its network, accounts, path or extension by itself.
In other words, two phrases with the same number of words can require completely different processes. The current implementation keeps Electrum-seed and BIP39 logic separate: mnemonic.py states that its mnemonic derivation does not follow BIP39, while keystore.py contains dedicated functions to validate and convert a BIP39 mnemonic. Even the normalization and derivation material differ. Do not try to make the formats match by reordering, translating or changing words.
What changed across Electrum versions
“Electrum seed” does not describe one historical generation. Versions before Electrum 2.0 used an older encoding based on a fixed word list. From version 2.0 onward, Electrum uses the version system documented above. Current software retains logic for recognizing old and modern types, but compatibility depends on the version, wallet type and recovery information you still have.
The official Electrum FAQ explains that a seed can recover a wallet and should be preserved, but it does not turn every word list into a native Electrum seed. An old backup, an imported phrase or a wallet with imported keys may require different data. Do not assume that “Electrum” always means one format.
Do not confuse a native Electrum seed extension with the wallet-file password. The extension participates in derivation and can change the keys; the password protects the local file, and changing it does not change the seed or addresses. The official FAQ explains that if you forget the password, you can restore from the seed, including its extension if used, and choose a new one. The code also keeps an Electrum extension separate from a BIP39 passphrase: they are not interchangeable when using the other mode (mnemonic.py, keystore.py).
Electrum can restore BIP39, but that is not native generation
Current Electrum code makes the distinction explicit in its wizard: when validating a seed, it separates the electrum variant from the bip39 variant. For BIP39 it checks the word list and checksum, derives seed material using the BIP39 rule, and asks for the matching path and script type. For an Electrum seed it uses its own version recognition and derivation. You can inspect that separation in the Electrum wallet wizard and the keystore implementation.
This means a BIP39 phrase imported into Electrum can work there without being a phrase Electrum would have generated natively. The BIP39 recovery tool scans active accounts across several conventions, and the supported BIP39 wallet formats list concrete paths and script types. Key derivation can be local, but that account scan queries Electrum servers for history and may disclose activity lookups; do not confuse it with an offline check or put a real phrase into a generic tool. Restoring BIP39 is therefore not just pasting words: you must choose the convention that explains the original wallet's addresses.
Support can differ between software and versions. A wallet may generate its own format, accept imported BIP39, accept both or support neither one. An app showing an “I have a seed” screen does not prove which interpretation it will apply. Check the documentation and origin of the backup before restoring it.
How to identify the format without exposing the phrase
-
Start with the origin. Record which app or device created the backup, its approximate version, whether the wallet was native, imported or multisig, and whether you saved a BIP39 passphrase, an Electrum extension, a path, a network or a script type. Do not type the words into this article, a form or a web checker.
-
Do not diagnose from length. Twelve words are common in BIP39 and Electrum, but 24 words do not prove BIP39 either. A familiar list only tells you that the vocabulary may overlap; it does not prove the derivation function.
-
Reproduce the original mode privately. Use a trusted installation and keep it offline where practical. Select the variant documented by the origin: native Electrum, imported BIP39 or another format. If the software asks for a BIP39 path or script type, that request is part of recovery, not an optional detail.
-
Compare a known public address. After restoring, compare a receiving address you already recorded. An empty wallet or a different address does not prove that the phrase is wrong: it may indicate the wrong variant, passphrase, path, network or discovery limit. Do not send funds to test a theory and do not erase the only working copy.
-
Treat an unknown-origin backup as unknown. Do not translate it, alter words to make it fit BIP39 or try online services. A phrase valid in one format can produce a different wallet in another. Translating a BIP39 phrase does not preserve the wallet either. Keep an independent offline backup with the details its recovery requires. SeedAddress's guide to checking a backup offline explains why a local check is safer than revealing words.
Where SeedAddress fits
SeedAddress derives a deterministic BIP39 mnemonic in the browser from coordinates, a password, a word list and a length. It adds no new random entropy and is not a private-key wallet generator. It also does not implement native Electrum seeds or automatically identify whether a phrase came from Electrum.
Do not enter a real Electrum phrase into SeedAddress to “convert” or check it. The application can help study its own deterministic inputs and limits, but Electrum recovery requires preserving the original format and wallet metadata. Use fictional labels and data for comparisons; never use a real phrase, password or key.