Skip to content
Text tools

Case Converter

Type an identifier or phrase and see it converted at once to nine naming styles: camelCase, PascalCase, snake_case, CONSTANT_CASE, kebab-case, dot.case, path/case, Title Case and Sentence case. Words are split at spaces, underscores, hyphens, dots, slashes and case changes, and a run of capitals such as HTTPServer is split into http and server. Digits stay attached to the neighboring letters (base64Encode becomes base64 and encode), and a pasted list is converted line by line. It suits renaming variables, translating between API and database naming, and making file names and URL slugs. Because every word is lowercased before being rebuilt, URL becomes Url and capitalized acronyms are not preserved. Characters such as Japanese are not converted. Everything runs in your browser.

Quick convert

StyleResult
camelCasehelloWorld—
PascalCaseHelloWorld—
snake_casehello_world—
CONSTANT_CASEHELLO_WORLD—
kebab-casehello-world—
dot.casehello.world—
path/casehello/world—
Title CaseHello World—
Sentence caseHello world—

Bulk convert

Convert JSON keys

Renames every key in a JSON document (for example camelCase ⇄ snake_case) and leaves the values untouched. Handy when an API and your code use different naming.

Guide

How to use & features

  • Type a single identifier or phrase into "Quick convert" to see all 9 naming styles at once.
  • Each row has its own "Copy" button so you can grab just the style you need.
  • "Bulk convert" lets you paste a multi-line list and convert it all to one chosen style at once.
  • Bulk mode is handy when you need to align JSON keys or a CSV header row to a different naming convention.
FAQ

FAQ

  • How are identifiers with digits (e.g. item2Name) split?

    A digit stays attached to whatever word it was already part of. "item2Name" splits into "item2" and "Name", and "base64Encode" splits into "base64" and "Encode" — digits are never pulled out as their own word.
  • Are acronyms like HTTP or URL handled correctly?

    Yes. A run of uppercase letters like "HTTPServerError" is split right before the next capitalized word begins, so it's recognized as three words: "HTTP", "Server", "Error".
  • What's the difference between "Quick convert" and "Bulk convert"?

    "Quick convert" takes one identifier and shows all 9 naming styles at once, useful for comparing styles side by side. "Bulk convert" takes a multi-line list and converts every line to one style you pick — useful for converting a whole set of JSON keys or a CSV header row at once.
  • Does it support non-Latin text, like Japanese or Chinese?

    It can split on explicit separators (spaces, underscores, etc.) in any script, but the automatic camelCase/PascalCase word-boundary detection (based on uppercase/lowercase transitions) assumes Latin letters. Non-Latin identifiers split correctly as long as they already use spaces or punctuation as separators.
Use cases

Common use cases

  • Converting naming conventions across languages

    Bridge the gap between a database column name (snake_case) and a JavaScript/TypeScript variable name (camelCase), or any other language/framework naming mismatch.
  • Bulk-converting JSON keys or CSV headers

    Paste a whole list of API response keys or a CSV header row and convert them all to a different naming convention at once with bulk mode.
  • Generating environment variable or constant names

    Type a setting name once and instantly see its CONSTANT_CASE env-var form and kebab-case CLI-flag form side by side.
  • Sanity-checking naming during code review

    Compare an existing variable name against the "correct" conversion to quickly spot naming-convention drift.
Notes

Notes & limitations

  • Word splitting is fully automatic

    Word boundaries are inferred from upper/lowercase transitions and separators. Special proper nouns like "iOS" or "macOS" may not split the way you expect, so always review the result visually.
  • Digits never become their own word

    "item2Name" is treated as two words, "item2" and "Name" — there is no way to pull the digit out into its own "item", "2", "Name" split.
  • No automatic word-boundary detection for non-Latin scripts

    Identifiers in Japanese, Chinese, and similar scripts only split correctly where an explicit separator (space, underscore, etc.) is present.

Articles for this tool

Recent Articles