English
Convert text between camelCase, snake_case, kebab-case, and more.
Last updated
helloWorldFromCoddyHelloWorldFromCoddyhello_world_from_coddyHELLO_WORLD_FROM_CODDYhello-world-from-coddyHello-World-From-Coddyhello.world.from.coddyhello/world/from/coddyHello world from coddyHello World From CoddyHELLO WORLD FROM CODDYhello world from coddyA case converter takes a phrase or identifier and rewrites it in every common naming style — camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, Title Case, Sentence case, and more. Developers reach for it constantly: refactoring variable names, generating database column names, writing API field names that match a style guide, and turning user-entered text into URL slugs.
Different ecosystems prefer different cases. JavaScript and Java like camelCase; Python and Ruby like snake_case; CSS classes and URLs use kebab-case; environment variables and constants use CONSTANT_CASE. A case converter lets you flip a phrase into the right style without doing it character-by-character in your head.
The hard part isn't the rewriting — it's the *tokenizing*. A case converter has to split mixed input like XMLHttpRequest, iOSDevice, or read_HTML5Tags into the right words first, then re-join them in the chosen style. Smart tokenizers handle acronyms (XML, iOS) and digits gracefully.
_ - .), and digit boundaries before re-joining.XMLParser round-trip as xmlParser or xMLParser? Pick the convention your codebase uses and stay consistent.Drop in a single phrase, an identifier, or a whole list. Mixed input — camelCase, snake_case, spaces — is fine.
The converter shows the input rewritten in 10+ cases. Pick the one your codebase uses.
Toggle handling of acronyms, digits, and special characters if your style guide has specific rules.
Click any variant to copy it to your clipboard. Useful when refactoring across files or filling in OpenAPI specs.
How the same phrase looks across the most common naming conventions.
| Style | Example | Where it's used |
|---|---|---|
camelCase | userName | JavaScript variables, Java methods |
PascalCase | UserName | Class names in most languages, React components |
snake_case | user_name | Python, Ruby, database columns |
SCREAMING_SNAKE_CASE | USER_NAME | Constants, environment variables |
kebab-case | user-name | URLs, CSS classes, shell flags |
Title Case | User Name | Headings, labels |
Sentence case | User name | UI copy, prose |
Train-Case | User-Name | HTTP headers (X-Request-Id) |
dot.case | user.name | Config keys, namespaced settings |
flatcase | username | Domain names, package slugs |
user profile photo
camelCase: userProfilePhoto · PascalCase: UserProfilePhoto · snake_case: user_profile_photo · kebab-case: user-profile-photo · CONSTANT_CASE: USER_PROFILE_PHOTO
Same words, five styles. Pick the one that matches the file you're editing.
const accessTokenExpiresAt = ...;access_token_expires_at = ...Most teams keep one canonical name in their domain model and translate it at the boundary between languages or between API layers.
10 Best Practices for REST APIs
10-best-practices-for-rest-apis
Slugs are kebab-case + lowercase + safe characters only. They double as URL segments and CSS class names.
userName, user_name in the same module). Pick a style and enforce it with a linter.XmlParser vs XMLParser). Decide once per codebase and stick with it.userName and username may be the same column on PostgreSQL but different on MySQL.accessTokenExpiresAt). It's the dominant style for variables and methods in JavaScript and Java.access_token_expires_at). It's idiomatic in Python, Ruby, and most relational database column names.UserProfile), camelCase does not (userProfile). PascalCase is reserved for class names and React components in most ecosystems.é → e), and remove characters that aren't letters, digits, or hyphens. Most case converters offer a slugify mode that does all of this in one step.