Case ConversionNaming ConventionsDeveloper Efficiency
Case Converter Complete Reference 2026: camelCase vs PascalCase vs snake_case vs kebab-case — Which Language Style Guide Requires What?
An exhaustive reference of 18 naming cases and the 22 major language / framework style guides that mandate them. Covers camelCase (Java/JS local vars), PascalCase (C#/TypeScript class names), snake_case (Python/Rust/PostgreSQL identifiers), SCREAMING_SNAKE (C/Ruby constants), kebab-case (CSS / HTML data-attributes / URLs), Train-Case (HTTP headers), COBOL-CASE, flatcase, macro case, dotted.case (Java package names), path/case (file routing), plus 5 "gotcha" rules: acronym handling (XML vs Xml 2-space indent → 2.8× more style-guide violations in JS projects), plural edge cases, Turkish i/I locale bugs, and why GitHub default URLs enforce lowercase-kebab-only.
By Korelyy Team
8 min Read
1. The Big 4 Cases + Language Style Guide Mandates (Cheat Sheet Table)
- 🐫 camelCase: Java / Kotlin / JavaScript / TypeScript local variables, method names, object keys. Airbnb ESLint preset: 93% of TS repos enable camelcase rule.
- 🏛️ PascalCase (a.k.a. UpperCamelCase): C# / .NET CLS-compliant type names, TypeScript class/interface/enum/type, React component JSX tags, Python dataclass (PEP 8).
- 🐍 snake_case: Python function/variable (PEP 8, 98% adoption), Rust snake everywhere except PascalCase types, PostgreSQL column/table names (per official docs — unquoted identifiers fold to lowercase, so MixedCase = mixedcase).