camelCase, snake_case & kebab-case Converter

Every programming language and system seems to have its own preferred naming convention, and moving a name between them is one of those small tasks that comes up constantly but is genuinely tedious to do by hand. This tool takes any input, however it is currently formatted, and converts it instantly into six common conventions at once: camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, and Title Case, with support for converting many names at once, one per line.

Why the same word gets written so many different ways

Naming conventions exist because most programming languages do not allow spaces inside identifiers, variable names, function names, file names, so every language and style guide has developed its own convention for representing multi-word names without spaces. JavaScript and Java both favor camelCase for variables and PascalCase for classes and components. Python and Ruby favor snake_case. CSS classes and URL slugs commonly use kebab-case. Environment variables and constants across nearly every language default to CONSTANT_CASE. None of these is more correct than another, they are just different conventions solving the same underlying problem, which is exactly why converting between them is such a frequent, low level task.

How this tool figures out where one word ends and the next begins

Converting into a new case is the easy part, the harder part is correctly figuring out the word boundaries in whatever format you started with. This tool detects boundaries from capital letters, in camelCase and PascalCase input, from underscores, in snake_case and CONSTANT_CASE input, from hyphens, in kebab-case input, and from plain spaces, in a normal sentence or Title Case input. It also handles a common tricky case correctly: an input like XMLParser or HTTPServer, where multiple capital letters appear together as an acronym, is split as XML, Parser rather than incorrectly splitting between every single capital letter, preserving the acronym as one unit the way a human reader would naturally interpret it.

Common situations where this actually gets used

This shows up more often than it might seem: converting a database column named user_email into a JavaScript property userEmail when mapping an API response, converting a React component name like NavigationBar into its file name navigation-bar.tsx to match a project's file naming convention, turning a JSON field into an environment variable name for a config file, or converting a list of spreadsheet column headers written as plain English phrases into valid variable names for a script. Pasting a whole batch of names at once, one per line, handles the more realistic case of renaming several fields together rather than converting a single word in isolation.

All six conventions generated together

Rather than picking a target format up front, every input is converted into all six conventions simultaneously, camelCase and PascalCase for JavaScript, TypeScript, Java, and similar languages, snake_case for Python, Ruby, and most database column naming, kebab-case for CSS classes, URL slugs, and file names, CONSTANT_CASE for environment variables and constants, and Title Case for display labels and headings. This means one paste answers the question for every context you might need it in, rather than requiring you to know in advance exactly which format you will end up needing.

Runs entirely in your browser

Word detection and every conversion happen instantly using plain JavaScript string logic in your browser, nothing you paste is sent to a server or stored. If your ultimate goal is a clean URL slug specifically, rather than a general programming identifier, our SEO URL Slug Generator is purpose built for that narrower case, handling stop word removal and special character stripping the way a URL slug specifically needs. Both this tool and that one are part of the same Developer Utilities collection.