Camel Case Regex

Replacement

Regular expression

/^[a-z][a-zA-Z0-9]*$/

Pattern breakdown

Part	Meaning
`Anchor or context`	Use anchors when you need whole-string validation.
`Main token`	The core token sequence describes the accepted text shape.
`Character class`	Character classes limit which characters are valid.
`Quantifier`	Quantifiers control how many characters or groups are accepted.
`Flags`	Use language-specific flags such as i, m, or u only when needed.

Should match

userProfileId

Should not match

user_profile
not matching sample
userProfileId invalid
user_profileuserProfileId

Test cases

Input	Expected	Why it matters
`userProfileId`	Match	Representative valid input for this pattern.
`user_profile`	No match	Common invalid or boundary input.
`(empty string)`	No match	Common invalid or boundary input.
`not matching sample`	No match	Common invalid or boundary input.
`userProfileId invalid`	No match	Common invalid or boundary input.
`user_profileuserProfileId`	No match	Common invalid or boundary input.

JavaScript

const re = /^[a-z][a-zA-Z0-9]*$/;
re.test(input);

Python

import re
bool(re.search(r"^[a-z][a-zA-Z0-9]*$", text))

PHP

$ok = preg_match('/^[a-z][a-zA-Z0-9]*$/', $value) === 1;

Java

Pattern pattern = Pattern.compile("^[a-z][a-zA-Z0-9]*$");
pattern.matcher(value).find();

Go

re := regexp.MustCompile(`^[a-z][a-zA-Z0-9]*$`)
ok := re.MatchString(value)

Notes and production use

Camel Case regex is useful as a practical starting point. Test it against your real input, avoid using it as the only security control, and prefer a parser when the format has complex grammar.

Performance tip: avoid running complex regular expressions repeatedly on very large untrusted strings without limits. Prefer anchored validation patterns, cap input length before matching, and use a parser when the target format has nested grammar.

Camel Case