Twelve Capitalization and Naming Styles
Compare twelve capitalization and naming variations of your input. Uppercase, lowercase, title, sentence, alternating and inverse modes retain whitespace. Camel, Pascal, snake, kebab, constant and dot styles join tokens into naming suggestions. The original input stays available above the outputs.
Twelve outputs from one input
- Type or paste a selection into Text to change case. Random loads a sample phrase.
- Compare the twelve selectable output boxes and their UTF-16 lengths.
- Copy the variation you need. If copying fails, select that output and copy it manually.
- Check names, abbreviations and the target syntax before using the result. Clear removes the input and resets feedback.
How the case mappings behave
Uppercase and lowercase use JavaScript Unicode case mappings. Mappings can expand characters: sharp s becomes SS in uppercase. They are not locale-specific, reversible normalization or transliteration. Locale-specific case mapping can differ, for example in Turkish.
Title Case uses English Intl.Segmenter word boundaries, lowercases each word-like segment and capitalizes its first cased character. It is simple word capitalization, not AP, Chicago or another editorial title style. Sentence case lowercases the entire input and capitalizes its first cased character after any punctuation or spaces. It does not capitalize each sentence or preserve acronyms.
Naming modes split whitespace, hyphens, underscores and periods, plus lower/digit-to-uppercase and acronym-to-word boundaries. XML plus Http plus Request becomes xmlHttpRequest in camelCase. Other punctuation remains. Alternating Case starts lowercase and advances once per grapheme cluster containing a cased letter; spaces, emoji and uncased scripts do not advance it. Inverse Case flips individual cased letter code points and may differ from context-sensitive whole-word mapping.
Exact outputs, line breaks and tabs included
In the examples, \n denotes a line break and \t denotes a tab. Leading spaces are meaningful.
| Input | Mode | Output |
|---|---|---|
XMLHttpRequest | snake_case | xml_http_request |
ÉCOLE\tWORLD\n | Title Case | École\tWorld\n |
HELLO. WORLD! | Sentence case | Hello. world! |
straße | UPPERCASE | STRASSE |
Cleanups, naming suggestions and headings
Capitalization cleanup
Repair accidental Caps Lock on a short draft, then restore names and abbreviations manually.
Naming suggestions
Compare camel, Pascal or separator styles for a label. Validate identifiers in the actual language or framework.
Heading drafts
Start with simple word capitalization, then apply your publication’s editorial title rules.
Case-sensitive review
Compare outputs with the original using the Text Difference Checker before replacing important wording.
What the naming modes do not check
Kebab-case is not a URL sanitizer. Punctuation, emoji, non-Latin letters and leading numbers can remain in naming outputs, and a language’s reserved words still need checking. Naming modes intentionally remove delimiter runs and trim delimiter-only edges. Prose modes retain source whitespace, including whitespace-only input. A browser textarea or clipboard can normalize line endings differently from the helper. Sentence case lowercases the input and capitalizes only its first cased character, so later sentences and acronyms are not restored automatically. Naming outputs still need syntax, reserved-word and URL checks in the target system.
Do not expect a reversible edit: case expansion, word splitting and lowercasing can lose information. English segmentation is not an all-language editorial policy; browser Unicode data can change boundaries. Keep the original, especially for Turkish names, acronyms, code and identifiers that already have a defined casing convention.
Working on the exact text you will change
Work on the exact label or paragraph you intend to change. Inspect the selectable output, rather than relying on its mode name. For comparing drafts without altering capitalization, use Text Difference Checker. Over-limit input shows an error and no stale output; the size caps do not guarantee performance on every device. Browser textarea and clipboard newline handling can differ.