Regex for Bitcoin SegWit address (bech32)
bc1... Bitcoin SegWit address.
The Bitcoin SegWit address (bech32) regex is ^(bc1)[02-9ac-hj-np-z]{38,87}$ — copy it below, or open it in the explainer for a token-by-token breakdown.
The pattern
^(bc1)[02-9ac-hj-np-z]{38,87}$
Token-by-token breakdown
Every part of the pattern, left to right:
| Token | Meaning |
|---|---|
^ | start of string (or line in multiline mode) |
( | start of a capturing group |
bc1 | literal text “bc1” |
) | end of group |
[02-9ac-hj-np-z]{38,87} | between 38 and 87 times: any of: “0”, 2–9, “a”, c–h, j–n, p–z |
$ | end of string (or line in multiline mode) |
About this pattern
Identifier formats like UUIDs, hashes, and version strings have well-defined structures that regex captures cleanly. The pattern verifies format; checksums and validity against a registry need additional checks.
Quick usage in different languages
This exact pattern — with the correct escaping and idioms for each language:
- JavaScript:
/^(bc1)[02-9ac-hj-np-z]{38,87}$/.test(value) - Python:
re.match(r"^(bc1)[02-9ac-hj-np-z]{38,87}$", value) - Java:
Pattern.compile("^(bc1)[02-9ac-hj-np-z]{38,87}$").matcher(value).matches() - C# / .NET:
Regex.IsMatch(value, @"^(bc1)[02-9ac-hj-np-z]{38,87}$") - Go:
regexp.MustCompile(`^(bc1)[02-9ac-hj-np-z]{38,87}$`).MatchString(value) - Ruby:
/^(bc1)[02-9ac-hj-np-z]{38,87}$/.match?(value) - PHP:
preg_match('~^(bc1)[02-9ac-hj-np-z]{38,87}$~', $value)
The explainer’s Code tab regenerates these for any pattern you paste, and the downloadable cheat sheet bundles the breakdown, all seven snippets, and the pitfalls below onto one printable page.
Common pitfalls
- Anchored to the whole string. This pattern uses ^ and $, so it requires the entire input to match. To find it inside a longer text, drop the anchors and use the global (g) flag.
- Case sensitivity. Letter ranges are case-sensitive — use the i flag if the input case can vary.
- Validate beyond format. Matching the format doesn't guarantee the value is real. Confirm the bitcoin segwit address (bech32) against a source of truth (database, API, or checksum) where it matters.
Standards & sources
This pattern is based on the following authoritative specification(s) and issuing authorities. Formats can change — always confirm against the primary source.
Related patterns
More patterns in the Codes & IDs category:
- Bitcoin address (legacy)
- Ethereum address
- CSS hsl() / hsla() color
- Solana address
- CSS rgb() / rgba() color
- PEM-encoded key/certificate
See also
Browse all 300 patterns in the library, or open this regex in the interactive explainer to see a token-by-token breakdown, test against custom input, and generate code in seven languages.