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

Regex for Twitter/X handle

Twitter @handle — 1-15 alphanumeric/underscore.

The Twitter/X handle regex is @([A-Za-z0-9_]{1,15})\b — copy it below, or open it in the explainer for a token-by-token breakdown.

The pattern

@([A-Za-z0-9_]{1,15})\b
Try in explainer → Download cheat sheet ↓

What it matches

  • @elonmusk
  • @user_123
  • @A
  • @_underscore

What it doesn't match

  • @toolonghandleabcd
  • @user-name
  • @user.name

Notes & gotchas

Twitter usernames are 1-15 characters, letters/digits/underscores only. Word boundary at end prevents matching @user_foo@bar as @user_foobar.

Code in your language

Use the explainer's Code tab to generate ready-to-paste snippets in JavaScript, Python, Java, .NET, Go, Ruby, and PHP for this pattern.

Open in explainer →

Token-by-token breakdown

Every part of the pattern, left to right:

TokenMeaning
@literal text “@”
(start of a capturing group
[A-Za-z0-9_]{1,15}between 1 and 15 times: any of: uppercase letters, lowercase letters, digits, “_”
)end of group
\bword boundary

About this pattern

Identifying and validating user identity (names, contact info, IDs) is one of the most common reasons developers reach for regex. The pattern below handles the format check; for full validation always confirm against a source of truth (database, API, or document).

Quick usage in different languages

This exact pattern — with the correct escaping and idioms for each language:

  • JavaScript: /@([A-Za-z0-9_]{1,15})\b/.test(value)
  • Python: re.match(r"@([A-Za-z0-9_]{1,15})\b", value)
  • Java: Pattern.compile("@([A-Za-z0-9_]{1,15})\\b").matcher(value).matches()
  • C# / .NET: Regex.IsMatch(value, @"@([A-Za-z0-9_]{1,15})\b")
  • Go: regexp.MustCompile(`@([A-Za-z0-9_]{1,15})\b`).MatchString(value)
  • Ruby: /@([A-Za-z0-9_]{1,15})\b/.match?(value)
  • PHP: preg_match('~@([A-Za-z0-9_]{1,15})\b~', $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

  • Not anchored. Without ^ and $ this can match a substring anywhere in the input — add anchors if you need the whole value to conform.
  • ASCII letters only. [a-zA-Z] excludes accented and non-Latin letters (é, ü, ß, ñ, and non-Latin scripts). For international input use Unicode properties like \p{L} with the u flag.
  • Escape it correctly per language. In Java and JavaScript strings each backslash must be doubled (\\d); in Python, Go, and C# use raw/verbatim strings so the backslashes survive.
  • Validate beyond format. Matching the format doesn't guarantee the value is real. Confirm the twitter/x handle against a source of truth (database, API, or checksum) where it matters.

Related patterns

More patterns in the Identity & contact 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