About online case conversion
Switch identifiers and prose between UPPER, lower, Title Case, camelCase, snake_case, kebab-case, and CONSTANT_CASE.
Online Case converter capabilities
Identifier splitting
Detects word boundaries in camelCase, PascalCase, snake_case, and kebab-case before applying the target style.
Naming conventions
- camelCase / PascalCase—common in JavaScript, Java, and C# APIs.
- snake_case—Python, Ruby, SQL columns, JSON from some backends.
- kebab-case—URLs, CSS classes, HTML attributes; CONSTANT_CASE—env vars and C macros.
Common use cases
API field rename
Map JSON keys from snake_case responses to camelCase in front-end code.
Database & ORM
Turn Java class names into table column styles your DBA expects.
Env & config keys
Switch between SCREAMING_SNAKE and kebab-case in deployment manifests.
Frequently asked questions
- When should I use snake_case vs camelCase in JSON?
- JavaScript and most browser APIs prefer camelCase; Python/Ruby stacks often emit snake_case. Pick one convention per boundary and convert at the edge rather than mixing in one object.
- Why did my acronym change oddly (e.g. HTTPResponse)?
- Automatic splitters guess word boundaries—HTTP+Response may become http_response or httpResponse depending on heuristics. For acronyms, edit the output or split manually.
- Does Title Case capitalize every word?
- This tool title-cases each detected word for quick headings. Formal title rules (skipping “and”, “the”) are not applied—that needs editorial style guides.