How Case Converter works
Case Converter first splits your input into "words" using a tolerant rule (whitespace, hyphens, underscores, case boundaries, and slash as in camelCase tokens), then reassembles them in the chosen convention. Each output form is byte-exact: camelCase keeps the first word lowercase and capitalises the rest, PascalCase capitalises everything, snake_case joins lowercase with _, kebab-case joins lowercase with -, UPPER_CASE joins uppercase with _, Title Case joins Capitalised words with spaces.
How to use
Paste any identifier, headline, or filename and toggle the target case. The output is deterministic — running the tool twice always gives the same result. Useful for refactors and for normalising variable names across files.
Frequently asked questions
How does Case Converter decide what counts as a word boundary?
It splits on whitespace, hyphens, underscores, and any transition from lowercase to uppercase (so camelCaseToken becomes ["camel", "Case", "Token"]). Numbers are preserved and treated as their own boundary ("foo2Bar" → ["foo", "2", "Bar"]).
Will acronyms be handled correctly?
Each acronym is split into its own word by default, so "HTTPSConnection" → ["HTTPS", "Connection"] → "httpsConnection". The behaviour is predictable but you may want to tweak output for product-specific acronyms.
What about non-ASCII letters?
Unicode letters (Cyrillic, Greek, CJK, accented Latin) are recognised as word characters and split the same way. Output keeps the original letters in their new casing.
Which case should I use for environment variables?
UPPER_SNAKE_CASE. It is the convention used by virtually every shell, dotenv loader, and CI system.
Does it lose characters or change numbers?
No. Every letter and digit is preserved; only the case and the joining character change.