BIP39 Mnemonic Demo

For learning and testing. Not a wallet.

See exactly how a recovery phrase is built: entropy, a SHA-256 checksum, 11-bit groups, and a 2,048-word list. Generate demo phrases for test fixtures, check a test phrase, and watch the 24 official test vectors pass in your browser. Never type a real recovery phrase into this or any web page.

Zero retention: your data never leaves this browser. Verify it yourself in DevTools

Loading the toolbox.

About BIP39 mnemonic

How Can You Verify That Nothing Leaves This Browser?

You do not have to take our word that any phrase or passphrase you type stays here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.

  1. Open your browser developer tools with F12, or Cmd+Option+I on a Mac, and select the Network tab.
  2. Reload the page and let it finish. You will see the page's own files, its web fonts, and one anonymous page-view request. Nothing has been typed yet, so none of them can contain any phrase or passphrase you type.
  3. Click the clear icon in the Network tab so that the log is empty.
  4. Generate a demo phrase, check a test phrase, and enter a passphrase.
  5. Look at the Network tab again. It is still empty. For extra proof, turn on offline mode after the page loads and the tool keeps working.

Only two things can add a line to that log, and neither carries any phrase or passphrase you type. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.

The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint, so a coding mistake could not quietly send any phrase or passphrase you type elsewhere.

What Is This Page For, and What Is It Not?

BIP39 mnemonic is a teaching and testing tool for developers. It shows how the BIP39 standard turns random bytes into the 12 to 24 words of a recovery phrase, generates demo phrases you can use as test fixtures, and checks phrases against the standard's rules and its official test vectors.

It is not a wallet, and the phrases it makes are demo-grade. That is about where they were made, not how: the randomness comes from the browser's cryptographic generator. A phrase shown on a web page has passed through a browser, its extensions, and possibly a screen recorder or a shoulder, and that is not where a phrase that holds money should ever be. This page derives no keys and no addresses, shows no balances, and makes no network request. It opens on public test vector #1, never on a random phrase, and every generated phrase is labeled DEMO.

How Does BIP39 Turn Entropy Into Words?

  1. Start with 128 to 256 bits of random entropy, in steps of 32 bits.
  2. Hash the entropy with SHA-256 and take the first entropy-length divided by 32 bits as a checksum: 4 bits for 128 bits of entropy, 8 bits for 256.
  3. Append the checksum to the entropy, giving a multiple of 11 bits: 132 bits for a 12-word phrase, 264 bits for 24 words.
  4. Cut the bits into 11-bit groups. Each group is a number from 0 to 2,047 and picks one word from the 2,048-word English list.

The math table on this page shows every group, its bits, its index, and its word, with the checksum bits highlighted in the last group. Edit the entropy hex and watch the words change. The English list is chosen so that the first four letters of every word are unique, which is why many wallets accept just four letters per word.

What Do the Entropy Bands Mean?

  • 12 words: 128 bits of entropy and a 4-bit checksum.
  • 15 words: 160 bits and a 5-bit checksum.
  • 18 words: 192 bits and a 6-bit checksum.
  • 21 words: 224 bits and a 7-bit checksum.
  • 24 words: 256 bits and an 8-bit checksum.

Even 128 bits is far beyond any brute-force search: 2 to the power 128 guesses is more than every computer on Earth could try in the age of the universe. Longer phrases add margin, but the real-world losses come from elsewhere: phrases that were photographed, typed into a phishing site, stored in a notes app, generated by a weak random source, or chosen by a person, because people pick words from a tiny, predictable fraction of the list.

Why Is the Last Word Special?

The last word holds the remaining entropy bits plus the checksum. For a 12-word phrase it carries 7 entropy bits and the 4 checksum bits, so for any 11 words exactly 128 of the 2,048 words can be last; the page lists them. That also means the checksum is weak protection: a single wrong word in a 12-word phrase still passes about one time in 16, and a 24-word phrase about one time in 256. A passing checksum says the words are plausible, not that they are the right words.

The phrase checker reports each word that is not in the list with its position and suggestions from the first letters, then checks the checksum and shows the entropy the words encode. If you paste a phrase that is valid and is not one of the official vectors, the page tells you plainly what to do if it ever protected real funds.

How Is the Seed Computed?

Wallets do not use the entropy directly. BIP39 runs the words through PBKDF2 with HMAC-SHA512, 2,048 rounds, and the salt mnemonic followed by an optional passphrase, giving a 64-byte seed. Both the words and the passphrase are normalized with Unicode NFKD first. The page computes the seed with the browser's Web Crypto API so you can compare it with the published value: the official vectors all use the passphrase TREZOR.

Every passphrase is valid and produces a completely different seed, so there is no error for a mistyped passphrase; a wallet simply opens a different, empty account. This page stops at the seed. Turning a seed into keys and addresses is the job of BIP32 and a real wallet, and this page deliberately does not do it.

How Should a Real Recovery Phrase Be Stored?

Everything above is about demo phrases. For a phrase that guards real funds, the safe habits are simple and strict:

  • Let the wallet or hardware device create it, offline, and write it down only by hand.
  • Never type it into a website, a browser extension, a chat, an email, or an AI assistant, and never photograph it or store it in a cloud drive or notes app. No legitimate support team will ever ask for it.
  • Keep the written copy on paper or stamped steel, in a place protected from fire, water, and curious visitors, and consider a second copy in a separate location.
  • If you add a BIP39 passphrase, store it separately from the words; losing it loses the funds.
  • Plan for inheritance: someone you trust should know how to find the phrase if something happens to you, without being able to use it today.

Sites that offer to validate or recover your phrase are a classic theft technique. If a real phrase has ever been typed into a web page, move the funds to a new wallet with a new phrase.

How Are the Official Test Vectors Used?

BIP39 implementations are tested against a published set of vectors: for each one, the entropy, the expected phrase, and the expected seed with the passphrase TREZOR. This page bundles the 24 English vectors and, every time it loads, checks all three directions for each: entropy to words, words back to entropy with the checksum, and words to seed. It also rebuilds the bundled 2,048-word list into the exact bytes of the published file and checks its SHA-256, so a damaged or altered list is caught before it is used. The result appears at the bottom of the tool, and the same checks run in the project's automated tests.

What Other Tools Are in the Generators Lane?

  • UUID: UUID v4 and v7, ULID, and NanoID in bulk, plus a decoder that reads timestamps back out.
  • .gitignore: Pick your languages, frameworks, OS, and editor; get one merged, de-duplicated .gitignore.
  • CSP: Build a Content-Security-Policy header or meta tag, with nonces, hashes, strict-dynamic, and Report-Only.
  • .htaccess: Apache rules for HTTPS, www canonical, compression, caching, headers, file blocking, and SPA fallback.
  • robots.txt: A robots.txt with your sitemap, private paths, crawl delay, and plain-English notes.
  • API mock: Define endpoints and responses, infer a schema from an example, and copy a no-dependency Node mock server with latency.
  • Meeting notes: Paste raw meeting notes; get actions, decisions, and open questions with an owner for each, as Markdown, JSON, or CSV.

Elsewhere in the toolbox: Hash, Base, Base58, TOTP, and more on the 2toolbox home page. Part of the 2suite.io privacy-first ecosystem.

Frequently Asked Questions

Can I use a phrase from this page for a real wallet?

No. Phrases here are for learning and test fixtures only. Let your wallet or hardware device create the phrase that will hold real funds.

Is the randomness weak?

No. Demo phrases use the browser's cryptographic random generator. They are demo-grade because they were shown on a web page, not because the math is weaker.

Why does my test phrase fail the checksum?

A word is wrong, missing, or out of order. The last word must match a checksum of the others, so most single-word mistakes are caught.

Does this page derive keys or addresses?

No. It stops at the BIP39 seed. There is no BIP32 key derivation, no address, no balance lookup, and no network request.

Which wordlists are supported?

The English list only, which nearly every wallet uses. BIP39 defines lists in other languages, and the same phrase in another language gives a different seed.

Was this helpful?