Skip to content
Spellkit

Case Converter

Convert text to UPPER, lower, Title, camelCase, snake_case, kebab-case and more.

  • UPPERCASE
  • lowercase
  • Title Case
  • Sentence case
  • camelCase
  • PascalCase
  • snake_case
  • kebab-case
  • CONSTANT_CASE

What is Case Converter?

Case Converter turns any text into nine formats at once — UPPERCASE, lowercase, Title Case, Sentence case, camelCase, PascalCase, snake_case, kebab-case, and CONSTANT_CASE. Every format is computed instantly with a copy button per row, and word boundaries are detected across spaces, hyphens, underscores, and camelCase. Convert text case online for free, right in your browser.

Key features

  • Nine formats: UPPER, lower, Title, Sentence, camel, Pascal, snake, kebab, CONSTANT
  • All formats computed at once — no mode to pick
  • Word boundaries detected in camelCase, hyphens, underscores, and acronyms
  • One-click copy button next to every format
  • Live character and word count

Case Converter — camelCase, snake_case, Title Case & more

Type a phrase once and get it back in nine different cases at the same time — no mode to choose, no "convert" button to press. The moment you type, all nine rows recompute and a live character and word count updates in the corner. It is meant for two crowds at once: developers renaming a variable across naming conventions, and writers who need a headline in Title Case or a paragraph in Sentence case.

The nine formats

UPPERCASE, lowercase, Title Case, Sentence case, camelCase, PascalCase, snake_case, kebab-case, and CONSTANT_CASE. Each sits in its own row with a Copy button, so you can grab getUserId for JavaScript, get_user_id for Python or SQL, get-user-id for a URL slug or CSS class, and GET_USER_ID for an environment variable — all from the same input. There is a Load sample button if you just want to see the nine outputs side by side before pasting your own text.

How word boundaries are detected

This is where a case converter earns its keep, and where the details matter. The splitter breaks your text into words on spaces, hyphens, and underscores — and also on camelCase transitions. So fooBarBaz, foo-bar-baz, and foo_bar_baz all resolve to the same three words and produce identical output in every case. It handles two boundary types specifically:

  • A lowercase-or-digit followed by an uppercase letter splits (getURL2Pathget, URL2, Path... within the acronym rule below).
  • A run of capitals followed by a capital-then-lowercase splits the acronym off: HTMLParser becomes HTML + Parser, not H, T, M, L, Parser.

That acronym rule is the part naive converters get wrong. It means parseJSONResponse round-trips cleanly to parse_json_response and back to parseJsonResponse without mangling the initialism.

Two behaviors worth knowing

Title Case and Sentence case are treated differently from the programmer cases. Title Case capitalizes the first letter of every whitespace-separated chunk while leaving your existing spaces and punctuation exactly where they are — it does not run the word-splitter, so well-known stays hyphenated rather than becoming Well Known. Sentence case lowercases everything, then re-capitalizes the first letter after each ., !, or ?. Neither one applies the "small words stay lowercase" style guide rule, so The Lord Of The Rings capitalizes of and the too.

The programmer cases (camel, Pascal, snake, kebab, constant) do the opposite: they normalize each word to a single case and rejoin with the separator, discarding your original punctuation entirely. Feed in a full sentence and snake_case will happily turn it into one long underscore-joined identifier.

Privacy

Every one of the nine conversions is plain string manipulation running in your browser. Nothing you paste is uploaded, logged, or stored — the page holds only what is currently in the box.

Frequently asked questions

How does it handle acronyms like HTMLParser?
It splits the acronym at the right boundary, so HTMLParser becomes HTML + Parser rather than H, T, M, L, Parser. That means parseJSONResponse round-trips cleanly to parse_json_response and back to parseJsonResponse without mangling the initialism — the detail most naive converters get wrong.
Why does Title Case capitalize small words like 'of' and 'the'?
Title Case simply capitalizes the first letter of every whitespace-separated chunk; it doesn't apply style-guide rules that keep articles and prepositions lowercase. It also leaves your punctuation in place, so 'well-known' stays hyphenated instead of becoming two separate words.
Do I have to choose a format before converting?
No. All nine formats — UPPERCASE, lowercase, Title, Sentence, camelCase, PascalCase, snake_case, kebab-case, and CONSTANT_CASE — are computed at once the moment you type, each in its own row with a copy button. A live character and word count updates alongside them.
What's the difference between the camelCase and PascalCase output?
Both strip separators and capitalize each word after the first, but camelCase lowercases the very first word (getUserId) while PascalCase capitalizes it too (GetUserId). camelCase suits JavaScript/TypeScript variables; PascalCase suits class and component names.
What happens to punctuation and spaces in the programmer cases?
For camel, Pascal, snake, kebab, and constant, spaces, hyphens, underscores, and other punctuation are treated as word boundaries and discarded, then words are rejoined with the target separator. So pasting a whole sentence into snake_case produces one long underscore-joined identifier rather than preserving your original layout.

Privacy

Every case format is computed locally from the text you type; nothing you enter is sent to a server.