Understand this tool
Change text case without retyping
- What the concept means
- Case conversion changes letter casing and often restructures word boundaries into naming conventions such as camelCase, snake_case, or kebab-case.
- Why it exists
- It provides repeatable identifiers or headings from ordinary text.
- When to use it
- Use it for drafts and code names, then review language-specific spelling and project conventions.
- What the result means—and does not mean
- The output is a mechanical transformation. It cannot infer intended acronyms, brand capitalization, grammar, identifier legality, or every locale-specific casing rule.
Unicode case is more than ASCII
Unicode maps characters among uppercase, lowercase, and titlecase forms. Some mappings change length, and locale can matter: Turkish dotted and dotless I is a familiar example. A byte-by-byte ASCII transformation is insufficient for general text.
camelCase and PascalCase encode word boundaries with capitalization; snake_case and kebab-case use separators. “Title case” is a language and editorial style concept, not merely capitalizing every token. Small words, punctuation, and names need context.
Key concepts
Key concepts
- Unicode casing
- Standard mappings among letter-case forms.
- Locale-sensitive casing
- Case behavior influenced by language conventions.
- camelCase
- Words joined with capitals after a lowercase first word.
- snake_case
- Lowercase words joined with underscores.
- kebab-case
- Lowercase words joined with hyphens.
- Title case
- Heading capitalization governed by language and style rules.
Method or process
How the process works
Unicode case is more than ASCII
Unicode maps characters among uppercase, lowercase, and titlecase forms. Some mappings change length, and locale can matter: Turkish dotted and dotless I is a familiar example. A byte-by-byte ASCII transformation is insufficient for general text.
camelCase and PascalCase encode word boundaries with capitalization; snake_case and kebab-case use separators. “Title case” is a language and editorial style concept, not merely capitalizing every token. Small words, punctuation, and names need context.
Compare the concepts
Common identifier styles
| Style | Example | Boundary signal |
|---|---|---|
| camelCase | helloWorld | Capital letters |
| snake_case | hello_world | Underscores |
| kebab-case | hello-world | Hyphens |
Common mistakes
Common mistakes
- Expecting mechanical title case to follow an editorial guide.
- Ignoring locale-specific letters.
- Assuming the output is a valid identifier in every language.
Edge cases and limits
Edge cases and limits
- Acronyms may need manual correction.
- Combining marks and uncased scripts do not behave like ASCII letters.