Text Case Converter
Convert text between UPPERCASE, lowercase, Title Case, camelCase, snake_case, and kebab-case instantly.
No data sent to serverRelated Tools
What is a Text Case Converter?
A text case converter transforms text between different capitalization and naming conventions. Developers frequently need to convert between naming styles when working across different programming languages, file formats, and coding standards.
This tool supports six common formats: UPPERCASE (all capitals), lowercase (all small), Title Case (first letter of each word capitalized), camelCase (used in JavaScript and Java variables), snake_case (used in Python, Ruby, and SQL), and kebab-case (used in CSS classes and URL slugs).
All conversions are displayed simultaneously, so you can see all output variations at once and copy whichever format you need.
How to Use
- Type or paste your text into the input box.
- All six case variations appear instantly below as you type.
- Click the Copy button on any output card to copy that format to your clipboard.
Naming convention reference
| Style | Example | Where used |
|---|---|---|
| UPPERCASE | HELLO WORLD | Constants in many languages, SQL keywords |
| lowercase | hello world | Plain text, HTML attributes |
| Title Case | Hello World | Headings, book titles, UI labels |
| camelCase | helloWorld | JavaScript/TypeScript variables, Java/C# methods |
| PascalCase | HelloWorld | Class names (most languages), TypeScript types, React components |
| snake_case | hello_world | Python, Ruby, Rust, SQL columns, env vars (lowercase form) |
| SCREAMING_SNAKE_CASE | HELLO_WORLD | Environment variables, constants in C/Python/JS |
| kebab-case | hello-world | CSS classes, URL slugs, npm package names, HTML attributes |
Common conversion scenarios
- API response transformation: server returns
snake_caseJSON, frontend needscamelCase— bulk-convert keys - Migrating between languages: porting Python (snake_case) to JavaScript (camelCase) or vice versa
- SQL ↔ ORM: database columns in snake_case, models in PascalCase / camelCase
- URL slug generation: blog post titles → kebab-case for SEO-friendly URLs
- CSS classes from data: dynamic class names from labels need kebab-case
- Environment variables: convert configuration values to SCREAMING_SNAKE_CASE for
.env
FAQ
When should I use camelCase vs snake_case?
Follow the language convention. camelCase is standard in JavaScript/TypeScript (variables, methods), Java, C#, Swift. snake_case is preferred in Python (PEP 8), Ruby, Rust, SQL columns. Mixing within a project signals lack of code review.
What is kebab-case used for?
CSS class names (.btn-primary), HTML attributes (data-user-id), URL slugs (/blog/my-post), npm package names, file names on case-insensitive systems (avoid MyFile.js on git working across Mac/Linux).
Does it handle multi-word input correctly?
Yes — the converter splits on spaces, underscores, hyphens, and camelCase boundaries. "hello world", "hello_world", "hello-world", and "helloWorld" all produce the same results.
Does it handle Unicode (Korean / Chinese / Japanese)?
UPPERCASE / lowercase work for any Unicode characters that have case. CJK characters don't have case, so they pass through unchanged. camelCase / kebab-case treat each character as a "word boundary" only at ASCII spaces/separators.
What about Title Case rules for "of", "the", "a"?
This tool capitalizes every word. True English Title Case (AP/Chicago style) leaves articles, conjunctions, and short prepositions lowercase except at the start. For strict editorial Title Case, manually adjust.
Are there other conventions I should know?
Yes — dot.case (e.g., com.example.app Java packages), Train-Case (HTTP headers like Content-Type), STUDLY_CAPS (SQL constants in some legacy systems), flat case (no separator: helloworld). Most are language-specific.
⚠️ Reference Only
Output is generated based on your input and is provided for reference. Results may vary depending on your specific use case, edge cases, or environment-specific behavior. We do not guarantee accuracy of conversions, validations, or computed values.
Always verify critical outputs against official documentation or production environments. We are not responsible for any decisions or losses based on these tool results.