Case Converter
Convert text between camelCase, PascalCase, snake_case, kebab-case and more.
About Case Converter
Naming conventions differ across programming languages, frameworks, and databases: JavaScript and Java use camelCase, Python uses snake_case, constants use CONSTANT_CASE, HTML/CSS uses kebab-case, and C# uses PascalCase. When moving data between systems or translating API responses, converting between these conventions manually is tedious and error-prone. This online case converter transforms any text into all major naming conventions simultaneously.
The converter handles smart boundaries: input like "user account ID", "userAccountId", "user_account_id", or "user-account-id" all convert correctly to every target format. It detects existing camelCase boundaries and treats spaces, hyphens, and underscores as word separators, so mixed input produces clean, predictable results.
Beyond variable naming, the tool is useful for URL slugs (kebab-case is the SEO-friendly standard for URLs), environment variable names (CONSTANT_CASE), database column names (snake_case is the PostgreSQL convention), file names, and even headline capitalization. Converting a whole list of fields takes seconds — paste once and copy each format you need.
The conversion logic runs entirely in your browser with instant updates as you type. There is no server round-trip, making it safe for proprietary field names, internal API schemas, or confidential configuration keys. Each result has a one-click copy button so you can grab exactly the format you need without retyping.
Frequently Asked Questions
What is the difference between camelCase and PascalCase?
camelCase starts with a lowercase letter (myVariableName), PascalCase starts with an uppercase letter (MyVariableName). JavaScript variables typically use camelCase, while class names and React components use PascalCase.
Which case should I use for URL slugs?
kebab-case (lowercase with hyphens) is the standard for URLs. Search engines treat hyphens as word separators, and URLs stay readable when copied as plain text.
Can it handle acronyms like "parseHTTPResponse"?
Yes. Consecutive capitals are treated as one word boundary, so "parseHTTPResponse" converts to parse_http_response (snake_case) and Parse Http Response correctly.
Does it support non-English characters?
The convention conversions work on ASCII letter boundaries. Non-ASCII characters are preserved as-is through the conversion, though most naming conventions restrict identifiers to ASCII anyway.