Naming Conventions and Case Styles in Programming
What this converter does
Every naming convention in programming is really the same words rearranged with different separators and capitalization. This tool takes whatever text you type — a phrase, a variable name, a heading — and rewrites it into eleven case styles at once: camelCase, PascalCase, snake_case, CONSTANT_CASE, kebab-case, dot.case, path/case, Title Case, Sentence case, lowercase, and UPPERCASE. Instead of converting one format at a time, every result appears side by side, each with its own copy button.
It also reads the shape of your input first. If you paste helloWorld it recognises the camelCase boundary; if you paste hello_world it splits on the underscore. That detected format is shown above the results, so you always know how the tool interpreted your text before you copy anything.
When to use it
Developers reach for this most when a codebase mixes conventions. A JSON API might return snake_case keys while your JavaScript variables are camelCase, and a CSS class or URL slug wants kebab-case. Rather than retyping the identifier and risking a typo, you paste it once and grab the exact style the target file expects.
It is equally useful outside code: turning a rough phrase into a Title Case heading, normalising a filename into path/case, or producing a CONSTANT_CASE key for an environment variable. Because all eleven forms are generated together, comparing them or copying several at once takes a single glance.
Example: helloWorld in every style
Take the words hello world. As camelCase they become helloWorld; PascalCase gives HelloWorld; snake_case is hello_world and CONSTANT_CASE is HELLO_WORLD. The same words render as kebab-case hello-world, dot.case hello.world, and path/case hello/world. Title Case produces Hello World, Sentence case Hello world, and the plain lowercase and UPPERCASE forms round out the set. One input, eleven ready-to-copy outputs.
Notes and edge cases
Word boundaries are the tricky part. The converter treats existing camelCase humps, underscores, hyphens, dots, slashes, and spaces as split points, so mixed input like getUser_ID is broken into words before being reassembled. Numbers stay attached to the word they follow. Because the transformation only regroups and recases letters, it never translates or spell-checks — the meaning of your text is untouched. Use 'Copy All' to export every conversion as a JSON object when you need the full set in one paste.