Text Case Converter
Convert text between camelCase, snake_case, kebab-case, PascalCase, SCREAMING_SNAKE_CASE, Title Case, dot.case, path/case, UPPERCASE, lowercase and more in real time. Click any output to copy it instantly.
One identifier per line — all lines are converted to the chosen case.
| Case | Example | Common Use |
|---|
What is a Text Case Converter?
A text case converter instantly transforms a phrase or identifier into any naming convention used in software development and DevOps tooling. Instead of manually retyping or reformatting identifiers, you enter text once and receive every case variant simultaneously — camelCase, PascalCase, snake_case, SCREAMING_SNAKE_CASE, kebab-case, and more. This is invaluable when translating human-readable descriptions into code identifiers, configuration keys, or database column names.
Naming convention consistency is a fundamental aspect of code quality and API design. Inconsistent casing causes subtle bugs — for example, a REST API that returns userId in camelCase but expects user_id in snake_case for write requests. Teams working across multiple languages face this challenge constantly: Python conventionally uses snake_case, JavaScript uses camelCase, while command-line flags typically use kebab-case. A fast conversion tool eliminates the mental overhead of switching between conventions.
When to Use This Tool
- Refactoring variable names across languages: When porting code from Python (snake_case) to TypeScript (camelCase) or vice versa, use this tool to batch-convert all identifier names without introducing typos.
- Defining environment variable names: Convert a readable config description like "database connection timeout" into the correct SCREAMING_SNAKE_CASE format (DATABASE_CONNECTION_TIMEOUT) for use in Docker, Kubernetes, or twelve-factor apps.
- Generating API field names: When designing a REST or GraphQL API, quickly produce camelCase field names from a data model written in plain English, ensuring consistency across request and response schemas.
- Creating kebab-case URL slugs: Turn a page title or feature name into a URL-safe kebab-case slug for use in routing configuration, Helm chart values, or Kubernetes resource names.
How It Works
The converter first splits the input text into individual words by detecting boundaries — spaces, existing underscores, hyphens, and transitions between lowercase and uppercase letters (for splitting already-cased input like camelCase or PascalCase). Once the token list is established, each output format is generated by applying a transformation rule: snake_case joins tokens with underscores in lowercase, SCREAMING_SNAKE_CASE does the same in uppercase, kebab-case uses hyphens, PascalCase capitalises the first letter of every token, and camelCase does the same but lowercases the very first letter. All transformations run synchronously in the browser with zero server round-trips.
Frequently Asked Questions
What text cases does this tool support?
The tool converts between camelCase, PascalCase, snake_case, SCREAMING_SNAKE_CASE, kebab-case, Title Case, UPPER CASE, lower case, dot.case, path/case, and more. All conversions happen simultaneously from a single input — you type or paste once and every variant is generated instantly. This is particularly useful when you need to define the same concept across multiple contexts: a Kubernetes label (kebab-case), an environment variable (SCREAMING_SNAKE_CASE), a Go struct field (PascalCase), and a JSON API field (camelCase) all from the same descriptive phrase.
What is the difference between camelCase and PascalCase?
camelCase begins with a lowercase letter and capitalises the first letter of each subsequent word — for example, myVariableName or getUserById. PascalCase (also called UpperCamelCase) capitalises every word including the first — for example, MyVariableName or GetUserById. In practice, camelCase is the standard for variable and function names in JavaScript, Java, Go, and Kotlin, while PascalCase is reserved for class names, TypeScript interfaces, React components, and Go exported identifiers. Understanding this distinction prevents common naming errors when reviewing code or designing APIs.
When should I use SCREAMING_SNAKE_CASE?
SCREAMING_SNAKE_CASE — all uppercase letters with underscores separating words — is the conventional format for environment variables, constants, and externally injected configuration values. Examples include DATABASE_URL, AWS_ACCESS_KEY_ID, MAX_RETRY_COUNT, and REDIS_CONNECTION_TIMEOUT. Using this convention universally signals to engineers that a value is fixed configuration or a constant rather than a computed runtime variable. It is the standard across shell scripts, Docker and Docker Compose environment blocks, Kubernetes ConfigMaps and Secrets, GitHub Actions environment variables, and twelve-factor app configuration. Most linters and style guides for Python, Java, and C enforce this convention for module-level constants.