1001Ferramentas
Aa Dev

Programming Case Converter (camelCase, snake_case)

Convert text between camelCase, PascalCase, snake_case, SCREAMING_SNAKE_CASE, kebab-case, dot.case, Title Case and more with one click. Perfect for renaming variables and API fields.

Formats produced

  • camelCase — myVariable (JS, Java)
  • PascalCase — MyVariable (C#, React components)
  • snake_case — my_variable (Python, SQL)
  • SCREAMING_SNAKE_CASE — MY_VARIABLE (constants)
  • kebab-case — my-variable (CSS, URLs)
  • dot.case — my.variable (config files, i18n)
  • Title Case — My Variable (headings)
  • Sentence case — My variable (prose)
  • UPPER CASE / lower case — plain folding

Convert text between case formats

A good chunk of programming is naming things, and every language, database or API follows its own convention: camelCase, snake_case, kebab-case, PascalCase. Swapping one for another by hand is tiring and leaves room for mistakes. This converter turns any text between all those formats with a click.

The cases most common in development are covered, from camelCase, PascalCase, snake_case and SCREAMING_SNAKE_CASE to kebab-case, dot.case, Title Case and others. Renaming a variable or standardising an API field becomes a matter of seconds. One name at a time, though: a line break counts as a word separator, so pasting a whole list fuses it into a single identifier.

Paste the text in the format you have, copy it in the format you need, and forget the manual rework. The conversion happens in the browser itself, with the text never leaving it.

Frequently asked questions

Can I convert a list with one name per line in one go?
No. A line break falls under the same rule as a space, a hyphen, an underscore or a dot: they all count as word separators. Pasting ten names on ten lines gives you one long identifier with all ten glued together, not ten results. Until batch conversion exists, feed it one name at a time, or paste the list, convert it and split the output by hand afterwards. The result block only shows up once the field holds something other than whitespace.
Why did parseHTTPResponse come out as parseHttpResponse, with the acronym lowercased?
Because everything is normalised to lowercase before being reassembled. The splitter does handle the acronym correctly, breaking the text into parse, http and response, but it then re-capitalises only the first letter of each word. That is how PascalCase ends up as ParseHttpResponse and camelCase as parseHttpResponse. SCREAMING_SNAKE_CASE hides the issue, since everything goes uppercase anyway. If an acronym has to stay fully capitalised, fix it by hand after copying.
What happens to accented characters in a name?
They stay put, because nothing is transliterated: minha variável becomes minhaVariável in camelCase and minha-variável in kebab-case. JavaScript accepts that, but URLs, database column names and CSS classes usually will not, so strip the accents before pasting if that is where the output is headed. Word splitting also treats only A to Z as uppercase, which means minhaÁrvore is never cut at the Á and comes out as a single word.

Related Tools