Case Converter

What is a case converter?

What this tool does

This tool converts any text into nine case styles at once: UPPERCASE, lowercase, Title Case, Sentence case, camelCase, PascalCase, snake_case, SCREAMING_SNAKE, and kebab-case. Paste or type in the input field and every variant updates live. Click Copy next to the format you need — conversion runs entirely in your browser.

Why you need it

Every language and platform prefers a different naming convention. JavaScript uses camelCase for variables; Python and Ruby favor snake_case; CSS classes and URLs often use kebab-case; database columns may be SCREAMING_SNAKE. Renaming identifiers by hand across a refactor is tedious and error-prone. A live converter lets you preview all formats from one string and copy the right one for your stack, CMS field, or API schema.

Case mismatches cause real bugs: a REST path defined as user-profile but referenced as userProfile in client code fails silently until runtime. Design systems often require kebab-case for CSS modules while TypeScript props stay camelCase. When onboarding to a new codebase, converting a sample identifier across all nine formats helps you internalize local conventions without memorizing regex recipes or IDE macros for each style.

How to use it

1. Paste or type your text in the input field.
2. Watch every case style update live as you type.
3. Click Copy next to the format you need.
4. Use Clear when you start a new string, or Load sample to see a demo phrase.

Practical examples

• Convert user_profile_id to userProfileId when moving a Python model to TypeScript.
• Turn a headline into Title Case for a blog post and kebab-case for its URL slug.
• Generate SCREAMING_SNAKE constants from a multi-word phrase for environment variables.
• Normalize mixed input like myAPI_key into clean tokens before picking a convention.
• Convert a database column name like created_at to createdAt when mapping rows to a JavaScript API response object.

How it works

The converter tokenizes input by splitting on spaces, underscores, hyphens, and camelCase boundaries. Each token is normalized to lowercase internally, then reassembled according to the target format: joined without separators for camelCase and PascalCase, underscores for snake variants, hyphens for kebab-case, spaces with capitalization rules for Title and Sentence case. Punctuation attached to words is preserved where possible. All processing is client-side — nothing uploads to Kitnax.

Title Case and Sentence case apply English-style capitalization rules to each token after splitting, while programming cases ignore capitalization in the source string and rebuild from normalized tokens. That means HELLO_WORLD and hello world produce the same camelCase output. SCREAMING_SNAKE uppercases every token and joins with underscores — useful for constants and environment variable names. Because all variants derive from one token list, you can trust that userProfileId, user_profile_id, and user-profile-id refer to the same conceptual identifier.

Common mistakes

• Expecting acronyms to stay uppercase in camelCase — APIKey vs apiKey depends on how tokens were split.
• Using Title Case output as a URL slug without further lowercasing and hyphenation.
• Pasting sentences with punctuation and expecting clean identifier output — strip or simplify first.
• Confusing PascalCase (classes) with camelCase (variables) when copying into strict linters.
• Converting full sentences with articles and prepositions to camelCase — strip filler words or start from a short noun phrase instead.

FAQ

Related tools

• Slug Generator
• Find & Replace
• Word & Character Counter
• Regex Tester