Thirteen case styles, one text box. Type or paste, pick a style, and the converted text appears below it ready to copy or to apply back over the input.
The one people reach for is title case, and the defaults show how it behaves: the quick brown fox jumps over the lazy dog becomes The Quick Brown Fox Jumps over the Lazy Dog. Every word is capitalised except the short joining words — "over" stays lower because it is not the first or last word.
What each style does
| Style | Example | Used for |
|---|---|---|
| Sentence case | Hello world. I am here. | Body copy, captions |
| lowercase | hello world | Tags, email addresses |
| UPPERCASE | HELLO WORLD | Labels, warnings |
| Capitalised | Hello World | Every word, including joining words |
| Title Case | The Quick Brown Fox Jumps over the Lazy Dog | Headlines, headings |
| camelCase | userProfileSettings | Variables, JSON keys |
| PascalCase | UserProfileSettings | Classes, components |
| snake_case | user_profile_settings | Database columns, Python |
| kebab-case | user-profile-settings | URLs, CSS classes |
| CONSTANT_CASE | USER_PROFILE_SETTINGS | Constants, environment keys |
| dot.case | user.profile.settings | Config namespaces |
| aLtErNaTiNg | aBcDeF | Mocking, emphasis |
| iNVERSE cASE | hELLO, wORLD! | Flipping existing capitals |
The six code styles share a rule: words are found by splitting on anything that is not a letter or digit, and by treating a lower-to-upper transition as a boundary. So User profile settings, user_profile_settings and userProfileSettings all convert to the same user-profile-settings in kebab case. Existing capitals are treated as word starts, which is what makes that work.
Proper nouns, acronyms and the keep list
Title case has to decide what a word is, and it decides by lowercasing first. iPhone becomes Iphone, McDonald becomes Mcdonald, and NASA becomes Nasa. That is correct title-case behaviour by one convention and wrong for the brand.
The keep list fixes it. Add ToolsHub4u, macOS, JavaScript and those strings keep their exact spelling wherever they appear. In the test, the quick brown fox jumps over the ToolsHub4u docs gave The Quick Brown Fox Jumps over the ToolsHub4u Docs, with the brand untouched and "docs" capitalised.
The keep list only applies to title case. Switch to sentence case and it is ignored: NASA said so. becomes Nasa said so., because sentence case lowercases the whole string before re-capitalising the first letter of each sentence. It does restore a standalone i to I, which is the one correction it makes.
Worked example: a heading and a variable
the 5 best noise-cancelling headphones for a long flight
Title case:
The 5 Best Noise-cancelling Headphones for a Long Flight
Sentence case:
The 5 best noise-cancelling headphones for a long flight
kebab-case:
the-5-best-noise-cancelling-headphones-for-a-long-flightThe heading keeps "for" and "a" lower because they are joining words in the middle. The slug lowercases everything and replaces every space with a hyphen, which is what a URL wants — though it keeps the digits, and most CMS slug fields do the same.
Two details in that example are worth noticing. Title case capitalised only "Noise" in "noise-cancelling", because the hyphen makes the second half a separate word; and kebab case left that hyphen where it was, since a hyphen is already the separator it would otherwise insert. Punctuation is discarded rather than transliterated, so Hello, World! becomes hello-world with no comma and no exclamation mark.
Which code style to pick
The choice is usually made for you by the language or framework, not by taste:
- camelCase — JavaScript and Java variables and functions; JSON keys in most APIs.
- PascalCase — React components, C# classes, type names.
- snake_case — Python variables, SQL columns, Ruby.
- kebab-case — URLs, CSS class names, HTML attributes, npm package names.
- CONSTANT_CASE — values that never change, and environment variable names.
- dot.case — config keys and event names, as in
user.profile.updated.
One warning: converting an existing name can collide. userID and user_id both become user-id, so a bulk conversion across a codebase is a refactor, not a formatting pass.
What it will not do
- No language awareness. It does not know that "Polish" is a nationality and "polish" is a verb, so title case lowercases the second meaning and loses the first.
- No sentence-boundary intelligence. Sentence case capitalises after any full stop, so "e.g. this" becomes "e.g. This".
- No accent handling in code styles. Only ASCII letters and digits survive the split, so
cafébecomescaf. - Whitespace tidy is optional. With it on, runs of spaces collapse, each line is trimmed and three or more newlines become two. With it off, the layout is preserved exactly.
- No undo. Applying the result back over the input replaces your original, so keep a copy before a second pass.
The safest habit with anything important: convert, read the first line, and check the words that are names. Those are the ones that change without warning.