Codebases and style guides disagree on how identifiers should be written — variables in camelCase, classes in PascalCase, database columns in snake_case, URLs and CSS classes in kebab-case, environment variables in CONSTANT_CASE. Converting text between them by hand is tedious and error-prone.
This tool first splits the input into individual words — recognizing word boundaries from spaces, underscores, hyphens, and existing camelCase capitalization — then rejoins them in the target case, so it works whether you paste plain text, an existing identifier, or a multi-word phrase.
Conversion happens entirely in your browser; nothing you type is sent anywhere.
What's the difference between camelCase and PascalCase?
Both join words without spaces and capitalize each word's first letter; camelCase leaves the very first letter lowercase (myVariableName), while PascalCase capitalizes it too (MyVariableName).
How does this split words in input without spaces?
It splits on existing separators (spaces, hyphens, underscores) and on camelCase/PascalCase boundaries, so myVariableName or my-variable-name both convert correctly to any other case style.
Why would I need snake_case vs kebab-case?
The right style is usually dictated by convention — snake_case is standard for Python variables and many database column names, while kebab-case is common in URLs, CSS classes, and file names.