Case Converter
Standard and developer-focused case transforms. Private, local, and instant.
About this tool
This case converter transforms any input text into 14 naming and formatting conventions simultaneously, covering everything from standard writing formats (UPPERCASE, lowercase, Title Case, Sentence case) to programming identifier formats (camelCase, PascalCase, snake_case, kebab-case, SCREAMING_SNAKE_CASE, SCREAMING-KEBAB-CASE, dot.case, path/case) and novelty cases (Alternating CaSe, Inverse cASE). All formats appear in a live grid as you type - click any card to select it, copy the output, or apply it back as the new input for further transformation. File drag-and-drop, undo/redo, and export are also supported.
Real example
Input: hello world json parser utility v2
Selected outputs across formats:
UPPERCASE: HELLO WORLD JSON PARSER UTILITY V2 lowercase: hello world json parser utility v2 Title Case: Hello World Json Parser Utility V2 Sentence case: Hello world json parser utility v2 camelCase: helloWorldJsonParserUtilityV2 PascalCase: HelloWorldJsonParserUtilityV2 snake_case: hello_world_json_parser_utility_v2 kebab-case: hello-world-json-parser-utility-v2 SCREAMING_SNAKE_CASE: HELLO_WORLD_JSON_PARSER_UTILITY_V2 dot.case: hello.world.json.parser.utility.v2
All 14 formats are generated from the same input in one pass. The tokenizer splits on word boundaries and handles Unicode characters, so accented names and multi-word phrases convert correctly.
Common use cases
- Refactoring identifier naming conventions: When migrating a codebase from snake_case (Python) to camelCase (JavaScript) or vice versa, paste a list of variable names here to convert them in bulk and paste the result back. Faster than manual find-and-replace for multi-word identifiers.
- Generating URL slugs: Paste a blog post title or product name and use kebab-case output as the URL slug. Kebab-case is the standard for SEO-friendly URLs (
/my-post-title) and is required by most CMS platforms. - Normalizing CSV column headers: Data pipelines often expect consistent header casing. Paste messy column headers (mixed Title Case and spaces) and export snake_case or camelCase equivalents for use in database inserts or API payloads.
- Content and UI copy formatting: Convert a block of feature names to Title Case for marketing copy or Sentence case for UI labels, where only the first word is capitalized (matching standard button and tooltip conventions).
How it works
Input text is tokenized by extracting all Unicode letter and digit sequences ([\p{L}\p{M}\d]+), discarding punctuation and whitespace. For programming cases (camelCase, snake_case, etc.), tokens are lowercased first, then joined with the appropriate delimiter. PascalCase capitalizes every token; camelCase capitalizes all but the first. For writing cases (Title Case, Sentence case), the original word boundaries from the input are preserved. SCREAMING variants uppercase the final joined string. The "Clean up spacing" option collapses multiple spaces to a single space before tokenizing, which is useful for pasting text from PDFs or formatted documents.
Common mistakes
- Numbers in identifiers: A token like "v2" becomes "v2" in camelCase (lowercase) and "V2" in PascalCase. If you need "V2" to remain uppercase in camelCase (as in "parseV2Request"), you will need to manually adjust - the converter treats digits as word-boundary-neutral characters and does not infer acronym capitalization.
- Acronyms flattened to lowercase: "API Request" becomes "apiRequest" in camelCase, not "APIRequest". This is intentional - converting to "APIRequest" requires knowing which tokens are acronyms, which is ambiguous without a dictionary. If you need preserved acronym casing, apply the converter and then manually restore the acronym.
- Multi-line input produces single joined output: All lines are treated as one continuous text block. If you have a list of identifiers on separate lines, convert them one line at a time, or use a batch approach by processing them as a separated list.
FAQ
What is the difference between camelCase and PascalCase
camelCase starts with a lowercase letter (myVariable) and is the standard in JavaScript, Java, and TypeScript for variables and function names. PascalCase starts with an uppercase letter (MyClass) and is the standard for class names in most object-oriented languages.
What is SCREAMING_SNAKE_CASE used for
SCREAMING_SNAKE_CASE (all caps with underscores) is the convention for constants and environment variable names in most languages and platforms - for example, MAX_RETRY_COUNT, DATABASE_URL, API_KEY.
Can I convert a whole file
Yes. Use the file picker or drop a .txt or .md file onto the input area. The file content is loaded into the input and all formats are generated immediately.
Is my text sent anywhere
No. All transformations run locally in your browser using JavaScript string operations. Nothing is uploaded or stored.
Related tools
- Word Counter — count words and characters after converting case
- Diff Checker — compare text before and after case conversion
- Line Sorter — sort the case-converted lines alphabetically or reverse
- JSON Formatter — format JSON whose keys need camelCase or snake_case normalization