/

Case Converter

Processed Client Side

Convert text between camelCase, snake_case, PascalCase, kebab-case, and 8 more formats instantly.

Input · 1 lines · 43 chars
1 lines · 43 chars
Length: 43Lines: 1Size: 43 BytesCursor: 1:1
Conversions
lowercasethe quick brown fox jumps over the lazy dog
UPPERCASETHE QUICK BROWN FOX JUMPS OVER THE LAZY DOG
Title CaseThe Quick Brown Fox Jumps Over The Lazy Dog
Sentence caseThe quick brown fox jumps over the lazy dog
camelCasetheQuickBrownFoxJumpsOverTheLazyDog
PascalCaseTheQuickBrownFoxJumpsOverTheLazyDog
snake_casethe_quick_brown_fox_jumps_over_the_lazy_dog
kebab-casethe-quick-brown-fox-jumps-over-the-lazy-dog
CONSTANT_CASETHE_QUICK_BROWN_FOX_JUMPS_OVER_THE_LAZY_DOG
dot.casethe.quick.brown.fox.jumps.over.the.lazy.dog
path/casethe/quick/brown/fox/jumps/over/the/lazy/dog
no casethe quick brown fox jumps over the lazy dog

Bookmark this tool now — skip the search next time you need it.

About Case Converter

This tool runs entirely in your browser. Whatever you paste is processed on your own device and is never uploaded, logged, or sent to any server.

Type or paste any text and see it converted into twelve naming conventions at once — lowercase, UPPERCASE, Title Case, Sentence case, camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, dot.case, path/case, and plain spaced words. Because every result is shown simultaneously, you never have to pick the conversion first; you paste once and copy whichever row you need. The word splitter understands existing casing, so it correctly breaks up an input that is already camelCase or snake_case before rebuilding it in the target convention, which is what makes it usable for renaming variables rather than just reformatting sentences. Nothing has to be clicked to see a result: the twelve rows recompute on every keystroke, so the tool works as a live reference for what a given name looks like in each convention.

Key features

  • Twelve conversions computed at once — no mode to select, every result is visible together
  • Programming cases: camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, dot.case, and path/case
  • Prose cases: lowercase, UPPERCASE, Title Case, and Sentence case
  • Smart word splitting that correctly separates an input already written in camelCase, snake_case, or kebab-case
  • Handles punctuation, digits, and mixed separators without producing doubled delimiters
  • Per-row copy button, so you take exactly the variant you want
  • Live update as you type, with no convert step in between
  • Multi-word phrases and whole sentences handled as readily as single identifiers, so it works for slugs as well as for variable names
  • Entirely client-side — nothing you paste is uploaded

How to use it

  1. Type or paste your text into the input pane.
  2. Scan the list of conversions in the output pane — all twelve update live.
  3. Find the convention you need.
  4. Click the copy button on that row.

Tips & common mistakes

  • Conventions by ecosystem: camelCase for JavaScript variables, PascalCase for React components and classes, snake_case for Python and SQL columns, kebab-case for URLs, CSS classes, and filenames, CONSTANT_CASE for environment variables.
  • It converts an existing convention as happily as plain prose, so pasting a variable name is the fast way to rename it across a stack with different conventions.
  • kebab-case is the right choice for URL slugs — search engines treat hyphens as word separators and underscores as joiners, so my_post_title reads as one token.
  • Title Case here capitalises every word. Editorial style guides usually leave short articles and prepositions lowercase, so a headline may still need a manual touch-up.
  • Acronyms are a known rough edge in every case converter: an input containing API or URL may come out as Api or camelCased in a way you did not intend — check those rows before using them.
  • dot.case is what you want for nested config keys and i18n translation keys; path/case matches directory structures and some routing schemes.
  • Renaming across a boundary is where this earns its place: an API that returns snake_case fields consumed by a camelCase codebase means every field name is converted twice, and doing that by hand is where typos come from.
  • Digits are treated as part of the word they touch, so utf8Encoder stays one token rather than splitting before the 8. If you want a separator there, put one in the input.
  • To check the length or word count before or after converting, use the Word & Character Counter.

Related tools

Browse all 8 Text tools

Frequently asked questions

9

Paste your text and choose the target case from the buttons — camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, and more are available.

It splits on uppercase letter transitions (camelCase → camel + Case), underscores, hyphens, and spaces — so myVariableName, my_variable_name, and my-variable-name all produce the same word list.

Yes — numbers are treated as part of the word they are attached to. For example, base64Encode remains intact and does not get split at the digit boundary.

Yes — paste an entire sentence and each word is converted. Useful for generating SCREAMING_SNAKE_CASE environment variable names or Title Case headings.

camelCase for JavaScript variables, PascalCase for React components and classes, snake_case for Python and SQL columns, kebab-case for URLs, CSS classes, and filenames, and CONSTANT_CASE for environment variables.

Search engines treat a hyphen as a word separator and an underscore as a joiner, so my_post_title is read as a single token while my-post-title is read as three words. kebab-case is the right choice for slugs.

Acronyms are the known rough edge in every case converter — an input containing API may come out as Api in PascalCase. Check those rows before using them rather than assuming the result is right.

Yes. The word splitter understands existing camelCase, snake_case, and kebab-case input and breaks it apart before rebuilding it, which is what makes this usable for renaming identifiers across languages.

dot.case suits nested configuration keys and internationalisation translation keys, while path/case matches directory structures and some routing schemes.