Case Converter
Different languages and frameworks use different naming conventions — JavaScript uses camelCase, Python uses snake_case, CSS uses kebab-case, Go uses PascalCase for exported symbols. Manually converting between formats across language boundaries is tedious and error-prone. This tool converts between 8 naming formats in real time — results appear as you type, no button click needed.
Supports camelCase, PascalCase, snake_case, kebab-case, dot.case, SCREAMING_SNAKE, Train-Case, and space-separated — 8 formats total. Auto-detects input format and displays all conversions simultaneously. Double-click any result to copy.
Enter a variable name to convert to all naming conventions
📖 Case Converter Guide
Why Naming Conventions Matter
Every programming language has its own naming convention: JavaScript/TypeScript uses camelCase (variables) and PascalCase (classes/components), Python uses snake_case, CSS uses kebab-case, Go uses PascalCase for exported identifiers, Java constants use SCREAMING_SNAKE. When a project spans multiple languages — say a Python backend + TypeScript frontend + PostgreSQL database — the same field can have three different formats. Manual conversion is tedious and error-prone. This tool syncs all 8 formats in real time.
8 Formats Explained
- camelCase: First word lowercase, subsequent words capitalized. Standard for JavaScript/TypeScript variables and functions.
- PascalCase: Every word capitalized. Used by React components, C# classes, Go exported identifiers.
- snake_case: All lowercase with underscores. Python variables/functions, PostgreSQL column names, Ruby methods.
- kebab-case: All lowercase with hyphens. CSS class names, HTML attributes, URL slugs.
- SCREAMING_SNAKE: All uppercase with underscores. Constants, environment variables, enum values.
- dot.case: Words separated by dots. Some configuration key formats.
- Train-Case: Capitalized words with hyphens. HTTP header field names (Content-Type).
- Space separated: Plain readable text for human-facing displays.