Skip to main content
AllDevToolsHub
🔡

Case Converter

100% Local

Transform text between camelCase, snake_case, PascalCase and more.

Case Converter
Input Text
44 chars · 9 words
All Conversions Preview
UPPERCASE

THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG.

lowercase

the quick brown fox jumps over the lazy dog.

camelCase

theQuickBrownFoxJumpsOverTheLazyDog

PascalCase

TheQuickBrownFoxJumpsOverTheLazyDog

snake_case

the_quick_brown_fox_jumps_over_the_lazy_dog

kebab-case

the-quick-brown-fox-jumps-over-the-lazy-dog

SCREAMING_SNAKE

THE_QUICK_BROWN_FOX_JUMPS_OVER_THE_LAZY_DOG

dot.case

the.quick.brown.fox.jumps.over.the.lazy.dog

path/case

the/quick/brown/fox/jumps/over/the/lazy/dog

Title Case

The Quick Brown Fox Jumps Over The Lazy Dog.

Sentence case

The quick brown fox jumps over the lazy dog.

11 Case Formats

Preview all case conversions simultaneously. Includes camelCase, snake_case, kebab-case, dot.case, path/case, SCREAMING_SNAKE, and more. All transformations happen instantly and locally.

Try:
This tool runs entirely in your browser. Your input is never uploaded, logged, or sent to AllDevToolsHub or anyone else, and it keeps working offline once the page has loaded.

Paste text and select a case. Works on multiple lines at once. Useful for batch renaming identifiers.

Overview

What is Case Converter?

Instantly convert text between programming and formatting cases: Title Case, Sentence case, kebab-case, and SCREAMING_SNAKE. Great for refactoring.
FAQ

Frequently Asked Questions

Reference

Technical Deep Dive

DEVELOPMENT TOOLS

Case Converter

Save time by instantly converting text between different programming and formatting cases. Supports Title Case, Sentence case, kebab-case, and screaming-snake-case. Perfect for refactoring and documentation.

Built for Devs

Designed by people who use these tools in production every day.

🧠

Smart Defaults

Reasonable assumptions out of the box, every assumption overridable when you need it.

🚀

Workflow-Friendly

Pairs with your IDE, CI, and code review, output drops into commits and PRs cleanly.

01 Convention Compatibility Matrix

Language Variable / Function Type / Class Constant
JavaScript/TScamelCasePascalCaseSCREAMING_SNAKE
Python / Rubysnake_casePascalCaseSCREAMING_SNAKE
Go / JavacamelCasePascalCaseUPPER_CASE
Rust / C++snake_casePascalCaseSCREAMING_SNAKE

02 Transformation Pipeline

1
Tokenization The input string is deconstructed into individual words based on separators, case shifts, and digit boundaries.
2
Normalization Tokens are cleaned of artifacts, and case-specific joining logic (underscores, hyphens, or caps) is applied.
3
Batch Serialization The final result is reconstructed, preserving line breaks for bulk refactoring of large identifier lists.

03 Where Case Conversion Saves Real Time

Every cross-language project pays a tax on naming-convention mismatches. Database columns, API contracts, CSS variables, env files, each has its own convention. Converting in bulk beats hand-renaming a list of 200 identifiers.

  • 🗄️
    Rename a database column to camelCase Your Postgres schema is user_id, created_at, last_login_at. The JavaScript ORM wants userId, createdAt, lastLoginAt. Paste the column list, hit camelCase, paste into the model definition.
  • 🔁
    Python ↔ JavaScript bridge Python's PEP 8 mandates snake_case for variables; JavaScript style guides mandate camelCase. When porting a Python class to TS, batch-convert the field names rather than retyping each one.
  • 🎨
    kebab-case for CSS variables Design tokens land as primaryColor in Figma but ship as --primary-color in CSS custom properties. The kebab transformation is the round-trip your token pipeline does on every build.
  • 📣
    SCREAMING_CONSTANTS for config Twelve-Factor App convention: env vars are SCREAMING_SNAKE_CASE. Converting a list of camelCase config keys to DATABASE_URL, REDIS_HOST, JWT_SECRET style in one pass.
  • 📜
    Style guide cite-points Google JS Style Guide, Airbnb JS Style Guide, PEP 8 (Python), Rust API Guidelines, Microsoft .NET naming guidelines, these are the canonical sources when a teammate questions a convention.

04 Worked Examples

EXAMPLE 1 · ONE IDENTIFIER, FIVE FORMATS
Source token: a user's first name field
camelCase           firstName

PascalCase FirstName
snake_case first_name
kebab-case first-name
SCREAMING_SNAKE FIRST_NAME


Typical placements:

JS variable, JSON field, Java method:  firstName
React component, Type, Class name: FirstName
Python attr, Rust var, SQL column: first_name
URL slug, CSS var, HTML attr: first-name
Env var, language constant: FIRST_NAME

Five formats for the same concept across a typical full-stack codebase. Manual conversion is error-prone, easy to drop a letter or capitalize the wrong character. Batch conversion against a known token list avoids that.




EXAMPLE 2 · ACRONYM HANDLING

Two competing style guides:

Token       Microsoft .NET style       Google / Airbnb JS style
"URL" Url (Pascal: Url) URL (preserve acronym)
"HTML id" HtmlId HTMLId
"XML HTTP" XmlHttp XMLHTTP (or XmlHttp, split opinion)

Real-world inconsistency in the standard library:

XMLHttpRequest     ← browser API (acronym preserved)
JSON.stringify ← JS built-in (acronym preserved)
Url.canParse ← .NET (Microsoft style)

Microsoft's guideline (PascalCase, with 2-letter acronyms uppercase and 3+ as Pascal) lost the platform war, most JavaScript and Python codebases preserve acronyms in full. Pick one style per project and lint it.




EXAMPLE 3 · ROUND-TRIP CASE LOSS

A common bug:

Start:          IOError
→ snake_case: io_error (lost: I and O were both initials)
→ camelCase: ioError (now lowercase i)
Round-trip: IOError ≠ ioError

Why it happens:

snake_case discards the acronym signal.
Once "IO" → "io", the converter cannot recover it.
Fix: keep an acronym dictionary, or never round-trip
identifier names that contain acronyms.

If your codegen pipeline goes JavaScript camel → Python snake → JavaScript camel, acronyms degrade. Generate from a canonical schema each time instead of round-tripping. Or normalize all acronyms to PascalCase-of-themselves at the schema level (IoError instead of IOError) so the round-trip is stable.




05 Related Tools

Case conversion sits inside larger refactoring and SEO workflows. These cover the adjacent steps.

You Might Also Need