Which case goes where
Convention, not law — but strong convention: camelCase for JavaScript/Java variables, PascalCase for classes and React components, snake_case for Python and SQL, kebab-case for URLs, CSS classes, and file names, CONSTANT_CASE for environment variables and constants. Following the local dialect is free readability; fighting it is a code-review comment waiting to happen.
Title case is the tricky one
Real style guides (AP, Chicago) lowercase short words — "of", "the", "and" — with rules that disagree with each other. This converter capitalizes every word, the simple convention most interfaces use; for a publication headline, apply your house style's small-word rules on top. Sentence case, meanwhile, has quietly won modern UI writing — Google's and Apple's guidelines both prefer it for buttons and headings.
Frequently asked questions
What's the difference between camelCase and PascalCase?
Only the first letter: camelCase starts lowercase (userName), PascalCase uppercase (UserName). Convention assigns camel to variables and functions, Pascal to types, classes, and components.
Does the converter understand existing camelCase?
Yes — it splits on case boundaries as well as spaces, hyphens, and underscores, so someVarName converts cleanly to some_var_name or SOME_VAR_NAME.
Why avoid spaces and capitals in file names and URLs?
Case-sensitivity differs across systems and spaces need escaping — kebab-case survives everywhere unchanged, which is why it owns URLs (and helps SEO by separating words unambiguously).
What is aLtErNaTiNg case for?
The mocking-SpongeBob meme register — sarcasm in text form. It has exactly one use and this page supports it dutifully.