Type or paste text, click a case, and copy the converted result.
Runs entirely in your browser — nothing you type here is sent to our server.
Case conventions exist because different contexts have different rules and readability needs. Prose uses Sentence case because that's how written language is normally punctuated; headings and titles often use Title Case for visual emphasis; and marketing copy occasionally reaches for UPPERCASE for shouting emphasis, though overusing it reads as aggressive and hurts readability.
Programming has its own conventions, largely because most programming languages don't allow spaces inside a variable or function name. camelCase and PascalCase pack multiple words together and use capitalization to mark word boundaries instead of spaces — JavaScript and Java commonly use camelCase for variables and PascalCase for classes, for instance. snake_case does the same job with underscores instead of capitalization, and is the convention in Python, Ruby, and most SQL database schemas. kebab-case, with hyphens, is the standard for URL slugs and CSS class names, since underscores are harder to read in a URL and hyphens are treated as word separators by search engines.
Written from what each site tells us about itself and how the directory works — see something off? Let us know.
Title Case capitalizes the first letter of every word (“This Is Title Case”), the style commonly used for headings and titles. Sentence case capitalizes only the first letter of each sentence and leaves the rest lowercase (“This is sentence case.”), matching normal prose.
These are naming conventions used in programming rather than everyday writing. camelCase (“myVariableName”) and PascalCase (“MyClassName”) are common for variables, functions, and class names in many languages; snake_case (“my_variable_name”) is preferred in others (like Python and Ruby) and for database column and file names; kebab-case (“my-page-slug”) is typical for URLs and CSS class names, since most systems don't allow spaces or underscores in a URL path.
No. Your original text stays in the input box; the converted result appears separately below it, so you can compare them or try a different case without retyping anything.
Basic case changes (uppercase, lowercase, Title Case, Sentence case) use JavaScript's built-in case-conversion functions, which correctly handle accented Latin letters and many other scripts. The programming-style conversions (camelCase, snake_case, and so on) strip anything that isn't a plain ASCII letter or digit, since that matches how those naming conventions are actually used in code and URLs.
