Case Converter
One input, every naming convention — ready to paste into code, URLs or filenames.
Why naming conventions are not cosmetic
Each language and each layer of a system has a convention. JavaScript variables and functions use camelCase; classes and React components use PascalCase; Python and database columns use snake_case; CSS classes and URL slugs use kebab-case; constants use CONSTANT_CASE.
Mixing them is not merely ugly — it causes real bugs when a serialiser, an ORM or a JSON encoder maps names automatically. A userName field that becomes user_name in one path and username in another will eventually break a lookup.
How word boundaries are detected
The tricky part of case conversion is splitting a string that has no separators. This tool splits on non-alphanumeric characters, then also at case transitions: getUserID becomes get, User, ID because an uppercase run followed by a lowercase letter marks a new word. Numbers stay attached to the word they follow, so v2Api → v2, Api.
Accents and non-Latin text
Letters outside ASCII are preserved as word characters, so café menu keeps the é. For a URL slug you usually want it transliterated (cafe) — that is a separate step, which the slug generator on this site handles with Unicode decomposition.
The one conversion that is not reversible
Going to lowercase and back loses the original word boundaries. userid cannot be split back into user id without a dictionary. That is why acronyms in identifiers should be written consistently — either userId or userID, never both in the same codebase.
Frequently asked questions
Does it handle acronyms like ID or URL?
parseHTMLResponse splits into parse, HTML, Response, producing parse_html_response.