Where does Bitcoin vanity matching begin?
The vanity search starts after the fixed bc1q part of the address, so your custom prefix applies to the next characters after that segment.
Generate native SegWit Bitcoin wallets locally in your browser
Create Bitcoin addresses with optional vanity prefixes up to 5 characters, fully in WebAssembly with no server round-trip.
Leave this empty to generate the first valid wallet immediately.
0/5
Vanity Matching Rules
Bitcoin vanity matching starts after the fixed bc1q part of the address, so a prefix of sat targets the part that follows bc1q.
Allowed vanity characters: Base58 only, using 1-9, A-H, J-N, P-Z, a-k, and m-z.
Ready. Nothing is uploaded to a server during generation.
Address format
Mainnet native SegWit starting with bc1q.
Vanity window
Matches after the fixed bc1q prefix.
Returned data
Address, seed phrase, WIF key, and hex keys.
Output Preview
You will get a mainnet native SegWit address, a 24-word recovery phrase, the derivation path, and the exported private and public keys.
Bitcoin Address Generator creates mainnet Bitcoin wallets directly in the browser using a Go WebAssembly build. That means the address, recovery phrase, and private key material are generated on your device instead of being sent to a hosted wallet service.
The page also supports short vanity prefixes when you want an address that starts with a custom pattern after the fixed bc1q prefix. Because vanity search can take time, the tool lets you cap the runtime and attempt count before the search begins.
Open the page and leave the prefix blank if you only need a fresh Bitcoin wallet.
Enter up to 5 Base58 characters if you want a vanity prefix, then choose your search limit settings.
Generate the wallet and immediately store the recovery phrase and private key in a safe place.
Creating one-off browser-generated Bitcoin wallets.
Testing short vanity prefixes on native SegWit addresses.
Local-first wallet generation when privacy matters.
The vanity search starts after the fixed bc1q part of the address, so your custom prefix applies to the next characters after that segment.
No. The intended workflow is local browser execution through WebAssembly, so the generated address and keys stay on your device unless you copy them somewhere yourself.