Which conventions does it produce?

Nine: camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, dot.case, Title Case, UPPERCASE and lowercase. All are shown at once from the same input, each with its own copy button.

Do I need to tell it what form my input is in?

No. The text is split into words first, recognising capital letters, underscores, hyphens and spaces as boundaries, so any of the supported forms is accepted as input and converts to all the others.

What is the difference between camelCase and PascalCase?

Only the first letter. camelCase starts lower case, as in userName, and PascalCase starts upper, as in UserName. By convention camelCase names variables and functions while PascalCase names classes, types and components, which is why the distinction is worth preserving.

Why is kebab-case used in URLs?

Because hyphens are unambiguous there. Search engines have long treated hyphens as word separators and underscores as joiners, URLs are case-insensitive in the host part and inconsistently handled elsewhere, and an underscore can be hidden by the underline styling of a link. The same reasoning applies to CSS class names.

How does it handle acronyms?

A run of capitals is treated as a single word, so a name containing an acronym keeps it intact rather than exploding into individual letters. This matters for names with terms like API, URL or ID, where the alternative would be unusable output.

How are digits treated?

They stay attached to the word they appear in rather than forcing a boundary, so a name like user2Name converts sensibly. If you need a digit to start a new word, separate it in the input with a space or an underscore.

Is Title Case here the same as editorial title case?

No. This capitalises every word, which is predictable. Editorial style guides leave short articles, conjunctions and prepositions lower case except at the start or end of a title, and they disagree with each other about the details. Use the output as a base and adjust to your style guide.

Can it convert several names at once?

The tool converts the input as a single name. For a list, convert them one at a time, or use the bulk replacement tool in the Japanese edition with a regular expression if you have a long list to process mechanically.

What happens with non-Latin text?

Characters without a case distinction, such as Japanese or Chinese, pass through unchanged, and the conventions that only change separators still apply. Accented Latin characters are upper- and lower-cased correctly.

Are the names I convert sent to a server?

No. The conversion runs in your browser, and nothing you type is transmitted, stored or logged.

Case Converter – camelCase, snake_case, kebab-case & More

Case Converter

// INPUT

// Case Converter: Features

It reads whatever you give it

The input is broken into words before anything else happens, using the boundaries each convention implies: a capital letter starting a new word in camelCase, an underscore in snake_case, a hyphen in kebab-case, a space in ordinary prose. That means you can paste helloWorld, hello_world, hello-world or hello world and get the same nine results, which is what makes converting between conventions a single step rather than two.

The conventions and where they belong

camelCase is the default for variables and functions in JavaScript, Java and Swift. PascalCase names classes, components and types almost everywhere. snake_case is the Python and Ruby convention and the usual form for database columns. kebab-case belongs in URLs, CSS class names and HTML attributes, where an underscore is awkward and a capital letter is not preserved. CONSTANT_CASE marks environment variables and compile-time constants. dot.case appears in configuration keys and namespaced settings.

Crossing boundaries is where it earns its place

A single system frequently uses three conventions at once: snake_case columns in the database, camelCase fields in the JSON API, and PascalCase types in the code. Adding a field means writing the same name three ways, and a batch of fields means doing it a dozen times. Converting mechanically removes the typo that otherwise surfaces as a null value nobody can explain.

Title Case and the limits of an algorithm

Title Case here capitalises the first letter of each word, which is the predictable behaviour. Real editorial title case is more subtle: style guides leave short prepositions, articles and conjunctions in lower case unless they begin or end the title, and they disagree with each other about which words qualify. Treat the output as a starting point for a heading rather than as house style applied automatically.

Safe for unreleased schema and field names

The conversion runs as you type and nothing is transmitted, stored or logged, so internal field names, unreleased feature names and schema identifiers are all safe to paste. Each result has its own copy button, so taking one form without disturbing the others is a single click.

// Case Converter: FAQ

Which conventions does it produce?: Nine: camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, dot.case, Title Case, UPPERCASE and lowercase. All are shown at once from the same input, each with its own copy button.
Do I need to tell it what form my input is in?: No. The text is split into words first, recognising capital letters, underscores, hyphens and spaces as boundaries, so any of the supported forms is accepted as input and converts to all the others.
What is the difference between camelCase and PascalCase?: Only the first letter. camelCase starts lower case, as in userName, and PascalCase starts upper, as in UserName. By convention camelCase names variables and functions while PascalCase names classes, types and components, which is why the distinction is worth preserving.
Why is kebab-case used in URLs?: Because hyphens are unambiguous there. Search engines have long treated hyphens as word separators and underscores as joiners, URLs are case-insensitive in the host part and inconsistently handled elsewhere, and an underscore can be hidden by the underline styling of a link. The same reasoning applies to CSS class names.
How does it handle acronyms?: A run of capitals is treated as a single word, so a name containing an acronym keeps it intact rather than exploding into individual letters. This matters for names with terms like API, URL or ID, where the alternative would be unusable output.
How are digits treated?: They stay attached to the word they appear in rather than forcing a boundary, so a name like user2Name converts sensibly. If you need a digit to start a new word, separate it in the input with a space or an underscore.
Is Title Case here the same as editorial title case?: No. This capitalises every word, which is predictable. Editorial style guides leave short articles, conjunctions and prepositions lower case except at the start or end of a title, and they disagree with each other about the details. Use the output as a base and adjust to your style guide.
Can it convert several names at once?: The tool converts the input as a single name. For a list, convert them one at a time, or use the bulk replacement tool in the Japanese edition with a regular expression if you have a long list to process mechanically.
What happens with non-Latin text?: Characters without a case distinction, such as Japanese or Chinese, pass through unchanged, and the conventions that only change separators still apply. Accented Latin characters are upper- and lower-cased correctly.
Are the names I convert sent to a server?: No. The conversion runs in your browser, and nothing you type is transmitted, stored or logged.

// How to Use Case Converter

Paste a name or phrase

Enter the text in whatever form you have it: camelCase, snake_case, kebab-case or ordinary words with spaces. The tool works out the word boundaries itself.
Read all nine forms

Every convention is shown at once, so you can see the form you need without choosing a target first. This is what makes it quick when a name has to exist in three places at once.
Copy the one you need

Each result has its own copy button. Copy the database column form, then the API field form, then the type name, without re-entering anything.

Category Text