Text Case Conventions for Developers
Case Conversion
When to Convert Case
Transform identifiers and labels between naming conventions — camelCase for JavaScript variables, snake_case for Python and SQL, kebab-case for URLs and CSS, PascalCase for class names, and more. Select the target format in Tool Settings.
Real-World Examples
user profile id → userProfileId (camelCase)
UserProfileId → user_profile_id (snake_case)
HTTPHeader → http-header (kebab-case)
Common Mistakes
- Converting acronyms inconsistently —
XMLParservsXmlParser - Applying case rules to sentences instead of identifiers
- Mixing conventions within one API (snake_case JSON keys vs camelCase in docs)
Developer Tips
- Pick one convention per language ecosystem and stick to it
- Title Case is for headings; CONSTANT_CASE is for environment variables and enum values
- Switch the target case tab in Tool Settings before running
Frequently asked questions
Which case formats are supported?
camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, and Title Case. Select the target in Tool Settings.
How does the tool detect word boundaries?
It splits on spaces, hyphens, underscores, and transitions between lowercase and uppercase letters. Multiline input is converted line by line for structured cases.
Will converting change my string length significantly?
Case changes preserve letters. Separator style (hyphens vs underscores) affects length slightly.