Text and Strings
Convert text with explicit word boundaries and a separate result.
Your text is processed in this browser and is not uploaded.
Result is out of date; export is disabled.
A case converter is useful when a field list mixes userName, User ID and account_status. Paste the list once, choose a naming style and keep each source line as a separate result.
For prose, uppercase to lowercase changes the letters while leaving punctuation and spacing in place. Naming styles instead rebuild words with separators; switching between these two tasks can therefore change more than capitalization.
Title Case retains the spaces in a heading, while snake_case joins its words with underscores. Compare the separate output before copying so the destination receives the kind of text it expects.
With case splitting enabled, XMLHttp becomes XML and Http. Number splitting is separate: version2Value keeps version2 together by default, or becomes version, 2 and Value when enabled.
Find a format using its displayed name or technical spelling, such as PascalCase. Each run prepares all eleven results. Searching filters choices; selecting a format displays its ready result without running the conversion again.
Automatic conversion waits 350 ms after an edit. Disable it to reveal Convert and run with Ctrl/Cmd+Enter. Input or option changes disable export until a fresh result is ready.
Example, Clear and Use result as input show a proposed replacement and its before/after length and changed-line count. Apply confirms it; Undo restores the preceding input and result. Copy and TXT export take only the selected style.
Lowercase, uppercase, title and sentence styles retain punctuation, repeated spaces and line endings. Title capitalizes each word; sentence capitalizes after supported sentence marks and at line starts.
Choose camelCase or PascalCase for joined words; snake_case, kebab-case, dot.case and path/case use their respective separators. CONSTANT_CASE joins uppercase words with underscores.
Case splitting recognizes lower-to-upper transitions and the final capital before lowercase in an acronym run. Number splitting adds letter–digit boundaries; turning it off leaves version2 together.
Unicode default does not depend on your device language. English, Turkish and German can be chosen explicitly. Turkish uppercasing maps i to İ; German uppercasing can expand ß to SS.
There are eleven: lowercase, uppercase, title, sentence, camel, Pascal, snake, kebab, constant, dot and path. Use the format search to locate the style, then review its separate output.
Yes. Each naming conversion works one line at a time and preserves line endings and empty lines. Prose formats also keep line boundaries; sentence mode starts a new sentence on each line.
The input limit is 200,000 UTF-16 code units. Some symbols take two units, so this is not a count of visible characters. Oversized input produces an error rather than a partial result.
Words are joined, the first word is lowercase and later words begin with a capital: user account becomes userAccount. Preserve acronyms can produce userAPI, but an initial API still becomes api.
PascalCase also capitalizes the first word: user account becomes UserAccount. With acronym preservation enabled, user API becomes UserAPI. Check your project conventions before using the generated name.
Found a word boundary that looks wrong?
Use the case converter to check a heading or naming list, adjust its boundaries and export the selected result.