Code Case Converter

Frequently Asked Questions

• What naming cases does it convert between?+
  It produces eight forms from any input: camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, dot.case, Title Case and Sentence case. You type once and see every form at once, each with a one-click copy button, so you can grab whichever your language or style guide requires.
• How does it split my input into words?+
  It detects word boundaries from any mix of separators — spaces, underscores, hyphens and dots — as well as the case transitions inside camelCase and PascalCase, including runs of capitals from acronyms. So “getHTTPResponse”, “get_http_response” and “Get HTTP Response” all break into the same underlying words before being recombined.
• What is the difference between camelCase and PascalCase?+
  Both join words with no separators and capitalise each word, but camelCase leaves the first word lower-case (myVariableName) while PascalCase capitalises it too (MyVariableName). By convention camelCase is used for variables and functions in many languages, and PascalCase for classes, types and components.
• When should I use snake_case versus kebab-case?+
  snake_case (words joined by underscores) is the norm for variables and functions in Python and Ruby and for SQL identifiers, and it is safe in nearly all programming contexts. kebab-case (words joined by hyphens) is used where hyphens are valid — URLs, CSS class names, HTML attributes and many file names — but not for code identifiers, since a hyphen reads as a minus sign.
• What is CONSTANT_CASE for?+
  CONSTANT_CASE — also called SCREAMING_SNAKE_CASE — uses all capitals with underscores and conventionally marks values that do not change: constants, enum members and environment variables (like MAX_RETRIES or DATABASE_URL). The all-caps styling signals “do not reassign this” at a glance.
• How are acronyms handled?+
  The converter treats a run of capital letters as a single word boundary, so “HTMLParser” splits into “html” and “parser”. This means acronyms are normalised consistently. If your project has a specific convention for acronyms in camelCase (such as “httpUrl” versus “httpURL”), review the output, as style guides differ on this fine point.
• Why does consistent naming matter?+
  Because code is read far more often than it is written. A consistent case convention lets readers infer what a name represents — a class, a constant, a URL segment — without checking its definition, and it keeps a codebase looking coherent. Most teams pick a convention per language and enforce it with a linter; this tool helps you convert quickly when moving names between contexts.
• Can I convert a whole sentence?+
  Yes. Although it is aimed at identifiers, it works on any phrase, which is handy for generating a slug from a title (kebab-case), a constant name from a label (CONSTANT_CASE), or a readable heading from a variable (Title or Sentence case). Numbers are preserved as part of the words around them.
• Is my input sent anywhere?+
  No. All the splitting and recombining happens in your browser. Nothing you type is transmitted, logged or stored, so it is safe to use with private code, identifiers or internal names.
• Is the Code Case Converter free?+
  Completely free, with no account or limit. It works offline once the page has loaded and collects no data.