Case Converter

Free case converter tool. Instantly convert any text to camelCase, PascalCase, snake_case, kebab-case, or UPPER_SNAKE_CASE in one click.

What Case Converter Does

Takes a plain text string — including phrases with spaces, mixed casing, punctuation, or special characters — strips all non-alphanumeric separators, and outputs the word sequence reformatted into the selected naming convention: camelCase, PascalCase, snake_case, kebab-case, or UPPER_SNAKE_CASE.

Who Uses This Tool

Case Converter is built for Frontend and backend developers renaming variables or functions, API designers standardizing field names, database engineers formatting column names, DevOps engineers writing environment variable keys, technical writers normalizing identifier formatting, code reviewers enforcing naming convention consistency. Whether you are processing data as part of an automated pipeline or need a quick one-off conversion in your browser, the tool requires no installation and no account — paste your input and get your result in seconds.

Primary Use Case

Converting a plain English phrase or inconsistently cased identifier into a specific programming naming convention to use directly in code without manual reformatting.

The Problem It Solves

Manually reformatting identifiers across naming conventions requires carefully capitalizing, inserting, or replacing separators on every word — a process that introduces typos and inconsistencies when applied repeatedly across many variable names or field keys. Switching between conventions mid-project, such as from snake_case to camelCase when changing languages or frameworks, is especially tedious at scale. This tool handles the full tokenization and reformatting automatically, treating any separator — spaces, hyphens, underscores, mixed casing — as equivalent input.

Example

Input
hello world example text
Output
helloWorldExampleText

When to Use This Tool

Use this tool when preparing variables for programming languages, formatting API fields, standardizing naming conventions, or converting human-readable text into code-friendly identifiers.

What to Do With the Output

Paste directly into source code as variable, function, or class names, insert into API schema field definitions, use in database column name declarations, embed in environment variable keys, or drop into configuration files requiring a specific naming convention.

Common Mistakes to Avoid

Numbers in the input are treated as word-boundary tokens and preserved in place — getUserProfile2Data will not split the 2 from adjacent letters unless a separator is present. All non-alphanumeric characters including dots, slashes, and apostrophes are stripped and treated as word separators, so abbreviations like user's or file.name tokenize into multiple words. UPPER_SNAKE_CASE output always uses underscores as separators regardless of input formatting. Input that is already in a casing format like camelCase will be flattened into individual lowercase tokens before re-conversion, so switching between conventions works correctly without pre-cleaning.

How It Works

The input string is trimmed, then all non-alphanumeric characters are replaced with spaces using a regex substitution, collapsing all separator types — spaces, hyphens, underscores, punctuation — into a uniform whitespace-delimited word array. The array is filtered to remove empty tokens. Each conversion function then maps over the word array: camelCase lowercases all words and capitalizes the first letter of each word except the first; PascalCase capitalizes the first letter of every word; snake_case joins all lowercased words with underscores; kebab-case joins all lowercased words with hyphens; UPPER_SNAKE_CASE uppercases all words and joins them with underscores.

Pro Tip

Use the swap button after converting to run a second conversion on already-formatted output — for example, convert a snake_case database column name to camelCase for a JavaScript object key, then swap and convert to kebab-case for a CSS custom property, all without re-entering the original input.

Also Known As

Case Converter is also commonly referred to as camelCase converter, snake case converter, kebab case converter, PascalCase generator, SCREAMING_SNAKE_CASE converter, variable name formatter, identifier case converter, text to camelCase, string case transformer, naming convention tool. All of these terms describe the same conversion — no matter what you call it, this tool handles it.

Frequently Asked Questions

Yes. The tokenizer strips all non-alphanumeric characters and splits on whitespace, but camelCase and PascalCase input without spaces will be treated as a single token. To split an existing camelCase identifier, insert spaces between words first before converting.
Numbers are treated as valid alphanumeric characters and preserved in place within the output. They do not act as word separators unless surrounded by non-alphanumeric characters.
Every word is fully uppercased and joined with underscores — for example, get user profile data becomes GET_USER_PROFILE_DATA. This format is standard for environment variable names and constants.
No. All non-alphanumeric characters including apostrophes, dots, slashes, and commas are treated as word separators and stripped from the output. The remaining alphabetic and numeric tokens are reassembled in the selected format.
Yes. Paste the snake_case column name, select camelCase, and the output is ready to use as a JavaScript variable name. The underscore separators are recognized as word boundaries and removed in the reformatted output.
Yes. kebab-case output produces all-lowercase words joined by hyphens, which is the standard format for CSS class names, HTML attributes, and CSS custom properties like --user-profile-data.