Text case conventions, when they matter and why
Case conventions determine readability and convey meaning across different contexts. In prose and UI copy, the choice between title case and sentence case affects tone: "Click the Submit Button" feels like 1990s software; "Click the submit button" reads naturally in modern interfaces. Most design systems (Google's Material Design, Apple's HIG, Microsoft's Fluent) standardise on sentence case for UI labels and title case only for formal headings. In code, case conventions are non-optional in most languages, using the wrong convention produces code that fails style reviews even when it runs correctly.
| Convention | Example | Standard use |
|---|---|---|
| camelCase | getUserById | JS/TS/Java/C# variables and functions |
| PascalCase | UserProfile | Classes, React components, C# types |
| snake_case | user_profile | Python, Ruby, SQL columns, URLs |
| kebab-case | user-profile | CSS classes, HTML attributes, URL paths |
| SCREAMING_SNAKE | MAX_RETRY_COUNT | Constants in most languages |
| Title Case | User Profile Page | Document headings, proper names |
| Sentence case | User profile page | UI labels, tooltips, error messages |
Practical uses for a batch case converter
Common workflows: converting a list of database column names (snake_case) into display labels (Title Case) for a report; converting a block of copy that came from a client in ALL CAPS into sentence case for a webpage; normalising a set of variable names from one language convention to another during a codebase migration; generating both the display name and URL slug from a product name in a single paste-and-convert step. Paste the whole block, multiple lines are processed individually.
Related: URL encoder for encoding slug values, Code minifier.