Convert text between UPPERCASE, lowercase, Title Case, Sentence case, camelCase, PascalCase, snake_case and kebab-case — all eight at once. Free, no sign-up — runs locally in your browser.
Eight cases, two families
The eight conversions split into two families that work
differently, and knowing which is which explains every output.
The display cases — UPPERCASE, lowercase, Title
Case and Sentence case — transform the text exactly as written:
your spacing and punctuation survive untouched, only letters
change. The identifier cases — camelCase,
PascalCase, snake_case and kebab-case — first split the text into
words (at spaces, underscores, hyphens and lower-to-upper
transitions, so "helloWorld" and "hello_world" are the same input),
lowercase those words, and rejoin them under the target style's
rules. That is why identifier conversions normalise: "HTTPS
connection" in camelCase is "httpsConnection", acronym and all —
the right answer for a variable name.
How to use this converter
- Type or paste once. All eight cases update live beneath the input — there is nothing to submit and no mode to pick first.
- Copy the row you need with its own Copy button; the label on the left names the style so you can check it against your project's convention.
- For identifiers, paste in any style you have — the splitter treats camel, snake, kebab and spaces as equivalent input.
- Your draft is kept in this browser for 7 days. Clear saved draft wipes it immediately.
Picking the right case
Case conventions are social contracts inside each ecosystem, and
the converter cannot choose for you — but the map is stable.
JavaScript, Java and C# write variables and functions in
camelCase and classes in PascalCase; Python and Ruby write
functions and variables in snake_case; CSS properties,
HTML data attributes and URLs use kebab-case; constants and
environment variables shout in SCREAMING_SNAKE_CASE (this tool's
UPPERCASE applied to a snake_case string). Beyond code, Title
Case headlines are the US publishing convention while Sentence
case has become the default for web interfaces and UK style —
whole style guides exist to arbitrate the little words, and this
tool's Title Case is the simple every-word rule, stated openly in
the FAQ. Consistency within a project matters more than the
particular choice; converting everything through one tool is one
way to keep it.
Frequently asked questions
Why convert cases with a tool instead of retyping?
Because identifier case is load-bearing. A variable renamed by hand from user_name to userName invites a one-letter slip that compilers may or may not catch, and a headline retyped in title case invites inconsistent choices (is it "The Lord Of The Rings" or "The Lord of the Rings"?). A converter applies one stated rule to the whole string at once: same input, same output, every time — which is also why the conversions here are documented rather than magical.
How are words split for camelCase, snake_case and friends?
All four identifier styles share one splitter: boundaries are found at lower-to-upper transitions ("helloWorld" → hello, World), at acronym ends ("HTTPSConnection" → HTTPS, Connection), and at any run of non-alphanumeric characters (underscores, hyphens, spaces). The words are then lowercased and rejoined per style. That normalisation is deliberate: it makes snake_case and camelCase exact inverses for typical identifiers, at the price of normalising deliberate internal capitals in brand-style names — "iPhone" becomes "iphone" in snake_case, which is correct behaviour for an identifier and wrong for a brand, so convert identifiers here, not logos.
Which case should I use where?
Follow the host language's convention rather than personal taste: JavaScript and Java use camelCase for variables and functions, PascalCase for classes and React components; Python and Ruby use snake_case for functions and variables; SQL and older C code favour snake_case too; URLs and CSS classes use kebab-case because URLs are case-insensitive in the host part and underscores sit awkwardly in links; environment variables and constants are traditionally SCREAMING_SNAKE_CASE. Headlines use Title Case (US publishing) or Sentence case (increasingly, UK and web style guides). When in Rome is the whole rule — mixed styles in one codebase are what linters complain about.
Does Title Case here follow a style guide?
It applies the simple headline rule: capitalise the first letter of every word and lowercase the rest of the word. Full style guides (AP, Chicago) lowercase short articles and prepositions — "The Lord of the Rings" — and capitalise the first and last words whatever they are. This tool deliberately does the simpler, predictable thing and says so; if you are publishing under a house style guide, treat the output as a first pass and adjust the little words by eye.
Is my text saved or sent anywhere?
It is converted locally in your browser and never transmitted. Like several other tools here it is auto-saved as a draft in this browser's local storage for 7 days, purely so an accidental refresh does not lose your place; the Clear saved draft button deletes it immediately, and it never leaves your device.
Dev