Case Converter

How it works

This tool converts text between casing styles directly inside your browser tab — no server, no upload, no waiting. Whatever style you paste in, the text is first split into individual words using boundary detection that understands spaces, underscores, hyphens, and camelCase/PascalCase capitalization changes (including acronym runs like "XML" or "URL"), then rejoined in whichever style you pick.

Title Case follows the conventional "smart" rule used in book and article titles: short connector words stay lowercase in the middle of a title but are always capitalized at the start and end. Sentence case capitalizes the first letter after every period, question mark, or exclamation point. The four programming-identifier styles — camelCase, PascalCase, snake_case, and CONSTANT_CASE — are the ones you'll recognize from variable, class, and constant naming conventions across most programming languages.

Limitations

Word-boundary detection is a heuristic, not a dictionary lookup — an unusual mix of capitalization can occasionally split or join words differently than you'd expect, particularly with numbers embedded in identifiers. Casing operations always use fixed, locale-independent rules rather than your browser's language setting, specifically to avoid locale quirks like Turkish's dotted/dotless "I" silently changing results.

FAQ

Is this case converter really free?

Yes — completely free, with no size limits and no account required. Everything runs in your browser, so there's no server cost to recoup.

Does Title Case capitalize every word?

No — it uses the conventional "smart" title case rule: short connecting words like "a", "the", "of", and "and" stay lowercase unless they're the first or last word, matching how book and article titles are actually styled (e.g. "The Lord of the Rings", not "The Lord Of The Rings").

Can I convert FROM camelCase or snake_case, not just to it?

Yes — the input is analyzed for word boundaries regardless of its original style, so "myVariableName", "my_variable_name", and "My Variable Name" all convert identically to any target case, including correctly splitting acronym runs like "XMLHttpRequest" into "XML", "Http", "Request".

Why does uppercasing "i" sometimes behave unexpectedly in other tools?

Some case converters use locale-aware casing, which under a Turkish system locale turns "i" into "İ" (with a dot) instead of the expected plain "I" — a classic bug that can silently corrupt code identifiers. This tool always uses fixed, locale-independent casing so results are consistent everywhere.