Why are there so many naming conventions?

Different ecosystems standardized on different patterns. JavaScript and Java settled on camelCase for variables and PascalCase for classes; Python and Ruby use snake_case; CSS and HTML use kebab-case; SQL columns are typically snake_case; constants are usually UPPER_SNAKE. Following the host language's convention makes your code idiomatic and readable to that language's community, which is more important than personal preference.

How are word boundaries detected?

The tool detects whitespace, underscores, hyphens, and case transitions from lowercase to uppercase. So 'getUserName' splits into 'get', 'User', and 'Name'; 'snake_case' splits into 'snake' and 'case'; 'kebab-case' splits into 'kebab' and 'case'. The tokens are then rejoined using the target convention's separator and capitalization rules.

Does it handle acronyms correctly?

Acronym handling varies between tools and style guides. The common rule is that in camelCase, 'URL' is rendered as 'Url' with only the first letter capitalized; PascalCase uses the same approach. Some tools and style guides keep acronyms uppercase ('XMLHttpRequest'). Verify the output matches your team's convention and adjust manually if needed.

What about numbers in identifiers?

Numbers are usually treated as separate tokens at word boundaries. 'version2' splits into 'version' and '2'; 'v2_api' splits into 'v', '2', and 'api'. That's the default behavior in most tools. For cases where you want to keep something like 'html5' as a single token, you'll need to adjust the output manually.

Will it preserve special characters?

Most tools strip punctuation and symbols when converting to identifier formats like camelCase or snake_case, since those characters aren't valid in most languages' identifiers. For Title Case or sentence case, which preserve spaces and read like normal text, special characters are typically kept. Check the output for edge cases if you're converting something with unusual punctuation.

Can it batch-convert multiple lines?

Many tools support multiple lines or comma-separated input, with each line or item converted independently. This is useful for bulk-renaming variables, translating a list of API endpoints, or processing a list of database column names in one pass. Specific behavior varies by tool, so check before relying on it for a large batch.

Is the data sent to a server?

No. Case conversion is pure string manipulation that runs entirely in JavaScript in your browser, so your text never leaves your device. That makes it safe to use for confidential identifiers, internal API names, or anything else you'd rather not paste into a hosted service.

Case Converter

Convert text between uppercase, lowercase, title case, sentence case, and more online. Free case converter for any text format.

Text Tools

Instant results

Enter Your Text

Click to Copy Converted Text

lowercase

hello world

UPPERCASE

HELLO WORLD

Title Case

Hello World

Sentence case

Hello world

camelCase

helloWorld

PascalCase

HelloWorld

snake_case

hello_world

kebab-case

hello-world

CONSTANT_CASE

HELLO_WORLD

aLtErNaTe

hElLo WoRlD

InVeRsE

Swaps case

About Text Case Converter

Convert text between different case formats instantly. Useful for programming variable names, file naming conventions, formatting titles and headlines, and more.

How to Use Case Converter

Paste your text

Enter the text or identifier you want to convert. Single words, multi-word phrases, and full sentences all work.

View all conversions

The tool displays all common cases simultaneously — camelCase, PascalCase, snake_case, kebab-case, UPPER_SNAKE, Title Case, sentence case, UPPER CASE, and lower case.

Copy the format you need

Click the format you want to copy it to your clipboard. This is particularly useful when you're bulk-renaming variables during a refactor.

Iterate or batch convert

Process multiple items at once by pasting in a line-separated list, or convert individual identifiers one at a time. Conversions are instant — no submit button required.

When to Use Case Converter

Code refactoring

Renaming variables and functions across naming conventions is a routine part of keeping a codebase consistent. Convert snake_case database columns to camelCase JavaScript variables, PascalCase classes to kebab-case CSS files, or bulk-translate Python API responses to JavaScript-friendly camelCase. It saves a lot of manual editing time during a refactor, especially when you're moving identifiers between languages.

Content writing and editing

Long stretches of ALL CAPS text are hard to read, and Title Case or sentence case generally land better for publication. The tool quickly normalizes emphatic emails, screen-shouted social media copy, or anything else that arrived in the wrong register, so you can drop it into your CMS without manual retyping.

URL slug generation

Article titles need to become URL-safe slugs — 'My First Post!' becomes 'my-first-post'. Kebab-case with punctuation stripped and whitespace normalized is the standard pattern for blog URLs, file names, and identifiers, and the converter handles the transformation in one step.

Database to API mapping

SQL columns are typically snake_case while JSON keys for REST APIs tend to be camelCase, and class properties often want PascalCase. The converter helps when you're hand-rolling a mapping layer in a project without an ORM, or when you're connecting two systems whose naming conventions don't agree.

Case Converter Examples

Multi-format conversion

Input

convert this text

Output

camelCase: convertThisText\nPascalCase: ConvertThisText\nsnake_case: convert_this_text\nkebab-case: convert-this-text\nUPPER_SNAKE: CONVERT_THIS_TEXT\nTitle Case: Convert This Text\nSentence case: Convert this text\nUPPER CASE: CONVERT THIS TEXT

A single input transformed into all eight common case formats at once. You can pick the one that matches your target system, and seeing them side by side makes the relationships between conventions much clearer than memorizing each individually.

Code symbol conversion

Input

user_full_name

Output

camelCase: userFullName\nPascalCase: UserFullName\nkebab-case: user-full-name

A database column name moves cleanly into a JavaScript variable (camelCase), a React component name (PascalCase), or a CSS class (kebab-case). The semantic meaning stays identical; only the syntactic form changes for each language.

URL slug generation

Input

10 Tips for Better SEO in 2024!

Output

kebab-case: 10-tips-for-better-seo-in-2024\nsnake_case: 10_tips_for_better_seo_in_2024

An article title becomes a URL slug. Punctuation gets stripped, whitespace normalizes to a single separator, and everything lowercases. This is the standard pattern for blog URLs and file names that need to remain readable but URL-safe.

Tips & Best Practices for Case Converter

1.Pick the case for the context. JavaScript variables go in camelCase, classes and constructors in PascalCase, constants in UPPER_SNAKE_CASE, CSS classes in kebab-case, Python identifiers and most database columns in snake_case. Following the host language's convention makes the code feel idiomatic.
2.Watch how acronyms get handled. Is 'URL' rendered as 'Url' or 'URL' in camelCase? Conventions vary — some style guides keep acronyms uppercase ('XMLHttpRequest'), others lowercase everything after the first letter. Check your team's preference and verify the output matches.
3.Numbers in identifiers are an edge case. 'version2' and 'version_2' get treated differently by different tools, depending on whether numbers count as a word boundary. Inspect the output if you're converting identifiers that mix letters and digits.
4.Don't convert the values inside strings. The tool changes the entire input. If you paste in 'API_KEY = "AbC123"' and convert to camelCase, the value 'AbC123' will be mangled along with the variable name. Convert identifiers separately from the strings they contain.
5.Consistency beats personal preference. If you're adding a new file to a codebase that's already using snake_case, write the new code in snake_case even if you happen to prefer camelCase. Mixed styles are harder to read than any single style.
6.For Title Case, remember the small-word rule. 'The Lord of the Rings' is proper Title Case — articles and short prepositions stay lowercase unless they appear as the first word. Tools sometimes capitalize every word, which produces 'The Lord Of The Rings' and looks slightly off.

Frequently Asked Questions

The common formats are camelCase (JavaScript variables), PascalCase (classes), snake_case (Python and most databases), kebab-case (URLs and CSS), UPPER_SNAKE_CASE (constants), Title Case (headlines), Sentence case (body text), UPPER CASE (emphasis), and lower case (everyday text). Most converters generate all of them from a single input so you can pick whichever fits the target system.

Case Converter

About Text Case Converter

How to Use Case Converter

Paste your text

View all conversions

Copy the format you need

Iterate or batch convert

When to Use Case Converter

Code refactoring

Content writing and editing

URL slug generation

Database to API mapping

Case Converter Examples

Multi-format conversion

Code symbol conversion

URL slug generation

Tips & Best Practices for Case Converter

Frequently Asked Questions

Related Tools

Word Counter

Character Counter

Line Counter

String Reverse

Reverse Words

Sort Lines