Advanced Text Case Converter

Why so many cases exist

"Case" describes how words are joined and capitalised, and different ecosystems standardised on different conventions decades ago. A programmer pasting user profile image needs userProfileImage for a JavaScript variable, UserProfileImage for a class, user_profile_image for a Python field, and user-profile-image for a CSS class or URL slug — the same words, four mechanical transformations. This tool runs your text through 16 transformations at once and shows every result side by side, so instead of retyping you just click the card you need to copy it. It updates live as you type, with a character counter so you can keep an eye on length.

The conventions, and exactly how they are produced

The conversions are smarter than a simple find-and-replace. The camelCase and PascalCase transforms split on spaces, hyphens, underscores, dots, and slashes, then capitalise accordingly — so feeding in my-old_file.name still produces a clean myOldFileName. The snake_case and kebab-case transforms additionally insert a separator at lowercase-to-uppercase boundaries, which means an existing camelCase input like getUserId correctly becomes get_user_id and get-user-id rather than one run-on word.

The four playful transforms

Beyond the practical conventions, the tool includes four novelty outputs:

• aLtErNaTiNg CaSe flips every other character by position, starting lowercase.
• rAnDoM cAsE chooses each character's case at random, so it differs on every keystroke — there is a "Random Case Again" button to reroll it without changing your text.
• Reverse text simply reverses the character order: hello → olleh.
• Mirror text maps each letter to an upside-down Unicode look-alike and reverses the order, so hello becomes oʅʅǝɥ — handy for eye-catching social posts where the platform allows raw Unicode.

A worked example

Type Fetch User Profile into the box. Instantly the camelCase card shows fetchUserProfile, PascalCase shows FetchUserProfile, snake_case shows fetch_user_profile, kebab-case shows fetch-user-profile, SCREAMING_SNAKE shows FETCH_USER_PROFILE, and dot.case shows fetch.user.profile. Click the kebab-case card and that slug is on your clipboard, ready to paste into a URL. The character counter at the top right reads 18 characters the whole time.

Why the boundary handling matters

The difference between a naive converter and a good one shows up at word boundaries. Consider an input that is already in one programming convention. Feed getUserID into snake_case and a naive tool that only splits on spaces would return getuserid — a single broken word — because there are no spaces to split on. This tool instead inserts a separator wherever a lowercase letter is followed by an uppercase one, so it correctly yields get_user_i_d from the camel humps. The same boundary rule powers kebab-case and, by extension, Header-Case, which is built on top of kebab-case and then re-capitalises each segment to produce HTTP-style Content-Type headers. Knowing this lets you predict the output: convert from a spaced phrase for the cleanest identifier, since multi-word inputs without internal capitals give the converter unambiguous boundaries.

Practical use cases

• Renaming variables across languages. Convert a single source phrase into the right identifier style for each codebase without hand-editing.
• Generating URL slugs. kebab-case turns an article title into a clean, lowercase, hyphenated slug in one click.
• Building constants. SCREAMING_SNAKE_CASE produces config and enum keys instantly.
• Cleaning up pasted headings. Title Case and Sentence case fix inconsistent capitalisation from copied text.

Common mistakes and limits

• Acronyms. Title Case lowercases the tail of each word, so NASA API becomes Nasa Api. Fix capitalised acronyms by hand after converting.
• Punctuation in identifiers. camelCase and snake_case strip the common separators but leave other punctuation in place; clean stray commas or quotes from the source first if you need a valid identifier.
• Sentence case and abbreviations. Sentence case capitalises after every ., !, or ?, so e.g. this may gain an unintended capital — review prose output.
• Mirror text portability. The upside-down glyphs are real Unicode characters, but some apps and fonts render them inconsistently; test before relying on them.

All 16 conversions run locally in your browser as you type — nothing you enter is sent to a server.