Download Cheat sheet PDF 12 pages · syntax, editors, patterns, Unicode, performance, debugging
Pattern

Regex for Bitcoin address (legacy)

P2PKH or P2SH Bitcoin address — starts with 1 or 3.

The Bitcoin address (legacy) regex is ^[13][a-km-zA-HJ-NP-Z1-9]{25,34}$ — copy it below, or open it in the explainer for a token-by-token breakdown.

The pattern

^[13][a-km-zA-HJ-NP-Z1-9]{25,34}$
Open in explainer → Download cheat sheet ↓

Token-by-token breakdown

Every part of the pattern, left to right:

TokenMeaning
^start of string (or line in multiline mode)
[13]any of: “1”, “3”
[a-km-zA-HJ-NP-Z1-9]{25,34}between 25 and 34 times: any of: a–k, m–z, A–H, J–N, P–Z, 1–9
$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: /^[13][a-km-zA-HJ-NP-Z1-9]{25,34}$/.test(value)
  • Python: re.match(r"^[13][a-km-zA-HJ-NP-Z1-9]{25,34}$", value)
  • Java: Pattern.compile("^[13][a-km-zA-HJ-NP-Z1-9]{25,34}$").matcher(value).matches()
  • C# / .NET: Regex.IsMatch(value, @"^[13][a-km-zA-HJ-NP-Z1-9]{25,34}$")
  • Go: regexp.MustCompile(`^[13][a-km-zA-HJ-NP-Z1-9]{25,34}$`).MatchString(value)
  • Ruby: /^[13][a-km-zA-HJ-NP-Z1-9]{25,34}$/.match?(value)
  • PHP: preg_match('~^[13][a-km-zA-HJ-NP-Z1-9]{25,34}$~', $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 address (legacy) against a source of truth (database, API, or checksum) where it matters.

Related patterns

More patterns in the Codes & IDs category:

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.


← Back to all patterns