Case Conversion
Convert text between different case formats and naming conventions with ease
Input Text
Select Case Format
Case Conversion Tool Features:
- 13 Case Formats: Support for all common programming and text case conventions
- Batch Processing: Convert to all case formats simultaneously
- File Support: Upload and process text files up to 100MB
- Line Preservation: Option to maintain line breaks in multi-line text
- Copy & Download: Easy copying to clipboard and file downloads
About the Case Conversion Tool
Different contexts expect different naming conventions. Python and Ruby communities favour snake_case, JavaScript and Java use camelCase for variables and PascalCase for classes, CSS uses kebab-case, and constants are conventionally written in CONSTANT_CASE.
This tool converts text between twelve conventions, and can produce all of them from a single input so you can pick the one you need.
How to use it
- 1Paste your text, or upload a file if you are renaming in bulk.
- 2Choose the target convention — lowercase, UPPERCASE, camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, dot.case, path/case, Title Case, Sentence case or aLtErNaTiNg case.
- 3Use the convert-all option to see every convention at once.
- 4Copy the result. Line breaks are preserved by default, so multi-line input stays multi-line.
When you would use it
- Renaming a variable across a codebase — converting a list of column headers to camelCase or snake_case in one go.
- Turning a title into a URL slug, or turning a slug back into something readable.
- Standardising inconsistent column names in a CSV before importing it somewhere that expects one convention.
How it works, and what it does not do
Conversion is a set of string transformations rather than a dictionary lookup, which is why acronyms and digits behave predictably: a run of capitals is kept together instead of being exploded into single letters, and digits do not get glued onto the preceding word. “Convert all” runs every format over the same input at once, which is the quickest way to see which convention you actually want.
The one thing no case converter can do reliably is find word boundaries in input that has none. A run like “userid” cannot be split into “user” and “id” without a dictionary, so anything glued together stays glued together. Feed it text with real separators if you want meaningful output.
Frequently asked questions
What is the difference between camelCase and PascalCase?
Both join words without separators and capitalise the first letter of each subsequent word. The difference is the very first letter: camelCase starts lowercase (userAccountId), PascalCase starts uppercase (UserAccountId).
How does the tool decide where words begin?
It splits on whitespace, punctuation and the boundaries between lower-case and upper-case letters. That is why converting an existing camelCase string like userAccountId to snake_case correctly produces user_account_id.
Which convention should I use for URLs?
kebab-case is the conventional choice for URL slugs because hyphens are word separators for search engines, while underscores are not treated as separators. That makes hyphenated slugs slightly better for readability and indexing.
Will it handle accented or non-Latin characters?
Standard case conversion works on Latin letters. Accented characters are passed through unchanged, and non-Latin scripts generally have no case distinction, so they are left as they are.
What is the difference between snake_case and kebab-case?
Only the separator: snake_case uses underscores, kebab-case uses hyphens, and both are lowercase. Kebab-case is the safer choice for URLs and CSS class names; snake_case is conventional in Python and SQL.
Does it work for non-English text?
It operates on characters, so accented and non-Latin text is upper- and lowercased correctly. The conventions themselves were designed around English word separators, so they are not meaningful for languages that do not put spaces between words.