Handle an acronym in a name
Converting getHTTPResponse to snake_case produces get_http_response. The converter splits both lowercase-to-uppercase boundaries and acronym-to-word boundaries.
0 input code points → 0 output code points. Casing can change length: ß becomes SS in uppercase.
Title case capitalizes every word, including short words. Sentence case lowercases the rest of each sentence; review names and acronyms. Identifier styles remove punctuation and emoji and split camel-case boundaries. No transliteration or identifier validation is performed. Maximum input: 250,000 UTF-16 code units.
All conversions run locally in browser memory. No text-generation or translation service is used.
How to use the Case Converter
- 01
Paste your text into the original-text field.
- 02
Choose uppercase, lowercase, title, sentence, toggle, alternating, or an identifier style.
- 03
Select a casing language when rules such as Turkish dotted and dotless I matter.
- 04
Review names and acronyms in the preview, then copy the result or download a plain-text file.
Examples
Use Turkish casing
With Turkish selected, the lowercase form of I is ı and the uppercase form of i is İ. English casing uses a different mapping.
Keep combining marks together
A word written with a base letter and a combining accent retains its mark during conversion. Casing does not normalize the text to a different Unicode normalization form.
Title and sentence case rules
Title case capitalizes the first letter of each letter-or-number word and lowercases the remaining letters, including short words. It is a mechanical style rather than a publishing style guide. Sentence case treats a new line, or a period, exclamation mark, or question mark followed by whitespace, as a boundary. It uppercases the first letter and lowercases the rest. Proper names, acronyms, and abbreviations need review.
Identifier styles and Unicode
camelCase, PascalCase, snake_case, and kebab-case split existing case boundaries and treat punctuation as word separators. They preserve Unicode letters, combining marks, and numbers; emoji and punctuation are omitted. The output is not checked against a programming language’s identifier rules. Some Unicode case mappings expand to several characters, so output length can change.
What to know
- Case mappings follow the browser’s Unicode and language data. Sentence boundaries use punctuation and newlines; abbreviations and proper nouns need review.
- Input is limited to 250,000 UTF-16 code units. Identifier conversions do not transliterate or validate programming language syntax.
Common questions
Will title case preserve NASA or iPhone?
No. Title and sentence conversions lowercase the source before applying their rules. Review brand names, proper nouns, and acronyms after conversion.
Does alternating case count spaces?
No. Alternating case advances only for characters that have different uppercase and lowercase forms. Spaces, punctuation, numbers, and emoji do not advance the pattern.
Why does uppercase ß become SS?
Unicode full case mappings can expand one character into several. The converter uses the browser’s locale-aware string casing rather than assuming a one-to-one mapping.
Will a converted phrase be a valid variable name?
Not necessarily. Identifier styles remove punctuation but may start with a digit, retain non-ASCII letters, or produce a reserved word. Check the rules of the language where you plan to use it.