Skip to content

Case Converter

Type once, get 14 conventions. camelCase, snake_case, kebab-case, and eleven more.

Splits on spaces, hyphens, underscores, dots, slashes, and camelCase boundaries.

Type text above to see all 14 case conversions

How the Case Converter Works

Type or paste any text, the tool first splits it into 'words' by detecting boundaries: spaces, underscores, hyphens, dots, slashes, and camelCase transitions (e.g. 'helloWorld' → ['hello', 'World']). Then each of the 14 case formats applies its own join rule to that word list.

The split is intentionally aggressive: it handles mixed inputs like 'some-slug_to convert.to/any_case' smoothly. Each conversion card shows the result, the framework or context where that casing is standard, and a copy button.

References & Conventions

There is no single RFC governing naming conventions — they vary by language and ecosystem. The general topic is documented in the Wikipedia: Naming convention (programming) article.

Ecosystem standards: camelCase — JavaScript, Java, TypeScript variables and methods. PascalCase — classes and components in most OOP languages. snake_case — Python (PEP 8), Ruby, SQL column names, file names. kebab-case — CSS class names, HTML attributes, URL slugs, CLI flags. SCREAMING_SNAKE_CASE — environment variables, constants in Python/C/Go. Train-Case — HTTP headers (Content-Type, X-Api-Key).

What's here, and what's not

14 case formats: UPPERCASE, lowercase, Title Case, Sentence case, camelCase, PascalCase, snake_case, kebab-case, SCREAMING_SNAKE_CASE, Train-Case, dot.case, path/case, aLtErNaTiNg CaSe, and iNVERSE cASE. Splits on spaces, hyphens, underscores, dots, slashes, and camelCase boundaries. Each card shows the ecosystem where the format is standard.

What isn't here: locale-aware title casing (The Chicago Manual of Style rules for articles and prepositions), unicode-specific casing for non-Latin scripts, smart capitalization that skips words like 'and'/'of' in titles, or bulk file renaming. This tool is a plain text converter — for code-aware renaming, use your IDE's rename refactoring.

Naming Conventions by Language and Context

camelCase (firstName, getUserById): JavaScript variables, functions, and TypeScript properties. Java variables and methods. JSON keys in most APIs.

PascalCase (UserProfile, GetUserById): JavaScript/TypeScript class names, React components, C# classes and methods. Also called "UpperCamelCase."

snake_case (user_first_name, get_user_by_id): Python variables, functions, and module names (PEP 8). Database column and table names (SQL). Ruby method names.

SCREAMING_SNAKE_CASE (MAX_RETRIES, API_BASE_URL): constants in most languages (JavaScript, Python, C). Environment variables.

kebab-case (user-profile, get-user-by-id): CSS class names, HTML attributes, URL slugs, file names in web projects. Cannot be used in most programming language identifiers because - is a minus operator.

Title Case (The Quick Brown Fox): book titles, article headlines, document headings, button labels in English UI.

Sentence case (The quick brown fox): general prose, subheadings in technical writing, UI body text.

Related tools: Slug Generator, Word Counter, Character Counter, and Lorem Ipsum Generator.

Title Case Rules and Edge Cases

Chicago Manual of Style: capitalize all words except articles (a, an, the), coordinating conjunctions (and, but, or, for, nor, so, yet), and prepositions shorter than 5 letters — unless they are the first or last word.

AP Style: capitalize all words except articles, coordinating conjunctions, and prepositions of any length — unless they are the first or last word.

APA Style: for reference titles, only capitalize the first word and proper nouns (sentence case); for journal article titles in running text, capitalize all major words (title case).

Common mistake: "The Cat In the Hat" vs "The Cat in the Hat", the preposition "in" should be lowercase in Chicago/AP style.

Automated title case converters cannot perfectly handle every edge case — proper nouns, intentional lowercase brand names like iPhone, or domain-specific capitalization always require a manual review of the output.

Frequently Asked Questions

Which case should I use in JavaScript?
In JavaScript and TypeScript: camelCase for variables, parameters, and function names (e.g. getUserName); PascalCase for classes, React components, and TypeScript types/interfaces (e.g. UserProfile); SCREAMING_SNAKE_CASE for module-level constants (e.g. MAX_RETRY_COUNT); kebab-case for CSS classes and HTML attributes.
Which case does Python use?
Python follows PEP 8: snake_case for variables, functions, and module names; PascalCase (CapWords) for class names; SCREAMING_SNAKE_CASE for constants. Package names use all-lowercase (no underscores preferred). These conventions are enforced by linters like flake8, pylint, and ruff.
How does the word split work for camelCase input?
The splitter uses two regex rules to find camelCase boundaries: (1) a lowercase letter followed by an uppercase letter — e.g. 'helloWorld' splits into ['hello', 'World']; (2) a sequence of uppercase letters followed by an uppercase+lowercase — e.g. 'HTMLParser' splits into ['HTML', 'Parser']. Then it also splits on spaces, underscores, hyphens, dots, and slashes.
What is Train-Case used for?
Train-Case (also called HTTP-Header-Case) capitalizes the first letter of each word and separates with hyphens: Content-Type, X-Api-Key, Authorization. HTTP/1.1 headers are conventionally written in Train-Case, though HTTP/2 lowercases all headers internally. It is also occasionally used in some configuration file formats.
What is the difference between title case and sentence case?
Title Case Capitalizes the First Letter of Most Words, Like a Book Title. Sentence case only capitalizes the first word of a sentence and proper nouns, like normal prose. Title case is used for headlines, headings, and titles; sentence case is standard for body text, email subject lines (in some style guides), and UI labels in conversational interfaces.
Which naming convention should I use for database columns?
Snake_case is the standard for SQL databases (PostgreSQL, MySQL, SQLite), it avoids case-sensitivity issues between databases and is consistent with SQL keywords (which are case-insensitive but conventionally uppercase). Avoid camelCase in SQL column names: firstName can become firstname depending on the database engine and collation settings. ORM frameworks (Drizzle, Prisma, SQLAlchemy) typically map snake_case DB columns to camelCase or PascalCase in application code automatically.

By Bam's Thinkery — Updated