Text Case Styles Explained: camelCase, snake_case, kebab-case & More
A practical guide to the most common text case styles — when to use each one and how to convert between them instantly.
Every developer has copy-pasted a heading into code and had to manually reformat it as camelCase or snake_case. Every writer has wondered whether a word in a title should be capitalised. Text case conventions exist everywhere — in code, in content, in URLs — and keeping them consistent matters.
The eight most common case styles
UPPER CASE — every letter is capitalised. Used for acronyms (NASA, URL), constants in code (MAX_RETRIES), and emphatic headings.
lower case — every letter is small. Used in filenames, some programming styles, and CSS class names.
Title Case — the first letter of each word is capitalised. Standard in English book titles, film names, and article headings. Style guides disagree on whether short words like “and” or “the” should be capitalised — our converter capitalises every word for simplicity.
Sentence case — only the first word of each sentence is capitalised, like normal prose. Increasingly preferred by modern style guides (Google, AP, most SaaS products) for UI copy, headings, and button labels.
camelCase — words are joined with no spaces; the first word stays lowercase and each subsequent word starts with a capital. Used for variable and function names in JavaScript, Java, Swift, and many other languages.
PascalCase — identical to camelCase but the very first letter is also capitalised. The standard for class names, React components, TypeScript interfaces, and C# types.
snake_case — words are joined with underscores and everything is lowercase. The convention for Python variable and function names, Ruby methods, and database column names.
kebab-case — words are joined with hyphens and everything is lowercase. The standard for CSS class names, HTML data attributes, URL slugs, and file names.
Why consistency matters
Mixing case styles in a codebase is a common source of bugs. A JavaScript object key userId is not the same as user_id — one will silently return undefined while the other works. Enforcing a single style per context (camelCase for JS variables, snake_case for DB columns, PascalCase for classes) eliminates an entire category of typo-related errors.
In URLs, kebab-case is strongly recommended by Google. Search engines treat hyphens as word separators, which improves keyword recognition. belun.app/text/text-case-converter is better for SEO than belun.app/text/textCaseConverter.
Tips for choosing the right style
- Follow the language convention first. Python enforces PEP 8 (snake_case); most JS/TS linters default to camelCase for variables, PascalCase for constructors.
- Pick one style for your content system. If your CMS slugs are kebab-case, make sure your file names match.
- Use Sentence case for UI. Research from UX teams at Google and Apple suggests Sentence case is easier to scan than Title Case for interface labels.
- Reserve UPPER CASE sparingly. Overuse makes content feel like shouting and hurts readability.
How to convert case quickly
The Text Case Converter handles all eight styles in your browser with no signup. Paste your text, click a button, and copy the result. The conversion happens client-side — nothing is sent to a server.
It also handles mixed input: if you paste theQuickBrownFox (camelCase) and click snake_case, it correctly splits on the capital letters and produces the_quick_brown_fox.
Try the Text Case Converter now — paste any text and convert between UPPER, lower, Title, Sentence, camelCase, PascalCase, snake_case, and kebab-case in one click.