Home›Case Converter

Text Case Converter

Convert text to UPPERCASE, lowercase, camelCase, snake_case, kebab-case and 12+ more formats

0 characters 0 words

Case Reference

  • camelCase — JS vars
  • PascalCase — Classes
  • snake_case — Python
  • CONSTANT_CASE — Constants
  • kebab-case — CSS/URLs
  • dot.case — Config files
  • Title Case — Headlines
  • Sentence case — Normal text

Related Tools

Word Counter Text Encrypt Hash Generator

Free Text Case Converter

Convert text to 16+ case formats instantly, including developer-friendly formats like camelCase, PascalCase, snake_case, CONSTANT_CASE and kebab-case, alongside typographic formats like Title Case, Sentence case, and fun transformations like sWaP cAsE. Handles complex text with mixed separators intelligently.

Features

16+ Case Formats

camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, dot.case, path/case, Title Case, Sentence case, UPPER, lower, sWaP, aLtErNaTiNg, Reverse, #HashTags and url-slug.

Instant Conversion

All 16 formats update simultaneously as you type — no button clicks required.

One-Click Copy

Click any result card to copy that specific format to your clipboard instantly.

Copy All

Export all 16 formats at once in a labelled list with one click.

Paste Support

Direct clipboard paste integration for fast paste-and-convert workflow.

Smart Word Detection

Intelligently splits words at hyphens, underscores, slashes, spaces and camelCase boundaries.

Who Uses This Tool?

DevelopersConvert variable names and function names between camelCase, snake_case and PascalCase.
SEO SpecialistsGenerate URL-friendly slugs from article titles for clean permalink structures.
Writers & EditorsApply consistent Title Case to headlines and headings across documents.
Social Media ManagersFormat hashtags and create visual interest with alternating case for posts.

Frequently Asked Questions

When should I use camelCase vs PascalCase?
camelCase (firstWordLower) is standard for JavaScript variables and functions. PascalCase (AllWordCapitalised) is standard for JavaScript classes, TypeScript interfaces and React components. Python uses snake_case for variables and functions.
What is kebab-case used for?
kebab-case (words-separated-by-hyphens) is the standard for CSS class names, HTML attributes, URL slugs and npm package names. It is the most human-readable format for identifiers.
What is CONSTANT_CASE?
CONSTANT_CASE (also called SCREAMING_SNAKE_CASE) is used for constant values in most programming languages — values that should not change during program execution.
What is a URL slug?
A URL slug is a URL-friendly version of text with spaces replaced by hyphens, special characters removed and all letters lowercased. For example, "Hello World! How Are You?" becomes "hello-world-how-are-you".

Pro Tip

When naming database columns, stick consistently to either snake_case or camelCase across your entire schema. Mixing conventions in a single database creates technical debt and makes queries harder to write and maintain.

Did You Know?

1978
camelCase Popularised
camelCase (also called "camel caps") was popularised in the late 1970s by programming languages and has been the dominant naming convention in JavaScript, Java and C# ever since. The term "camelCase" itself uses camelCase.
PEP 8
Python's Style Guide
Python's official PEP 8 style guide (published 2001) mandates snake_case for variables and functions, PascalCase for class names, and UPPER_CASE for constants. Following consistent naming conventions significantly improves code readability and team collaboration.
kebab
Why It's Called kebab-case
kebab-case gets its name because the words are "skewered together" by hyphens, like meat on a kebab skewer. It is the standard for CSS classes, HTML attributes, URL slugs and npm package names — anywhere hyphens are allowed but underscores are not.

Case Naming Convention Reference

Case StyleExampleUsed InNotes
camelCasemyVariableNameJS, Java, C#, Go (funcs)First word lowercase
PascalCaseMyClassNameClasses (all languages)Every word capitalised
snake_casemy_variable_namePython, Ruby, SQLWords joined by underscores
CONSTANT_CASEMAX_RETRY_COUNTConstants (all languages)All uppercase + underscores
kebab-casemy-css-classCSS, HTML, URLs, npmWords joined by hyphens
COBOL-CASEMY-VARIABLECOBOL, some HTTP headersUppercase + hyphens
dot.caseconfig.file.nameConfig files, Java packagesWords joined by dots
Train-CaseContent-TypeHTTP headersCapitalised kebab-case

More Questions

Which case should I use for different programming languages?
JavaScript/TypeScript: camelCase for variables/functions, PascalCase for classes, CONSTANT_CASE for constants. Python: snake_case for variables/functions, PascalCase for classes, UPPER_CASE for constants. CSS: kebab-case for class names and custom properties. Databases: snake_case for table/column names. URLs: kebab-case (SEO-friendly). File names: kebab-case or snake_case (avoid spaces).
Does naming convention affect SEO?
Yes, for URLs. Google prefers kebab-case (my-page-name) over snake_case (my_page_name) or camelCase (myPageName). Hyphens are treated as word separators by Google; underscores are not. "image-converter" as a URL reads as two words; "image_converter" reads as one word "imageconverter". Use hyphens in URLs for best SEO.
What is the "Train-Case" and where is it used?
Train-Case (also called "HTTP-Header-Case") capitalises every word and uses hyphens as separators: My-Header-Name. It is used in HTTP headers (Content-Type, Accept-Language, X-Request-ID). Unlike kebab-case, each word is capitalised. Some CSS properties use a similar style but in lowercase.

Common Mistakes

Mixing naming conventions in the same codebase
Having myVariable, my_variable and MyVariable for similar things in the same file creates cognitive load and signals poor code quality.
Pick one convention per language/layer and enforce it with a linter (ESLint, flake8).
Using spaces or special characters in file names
File names with spaces require quoting in terminal commands ("my file.txt") and cause problems in URLs and scripts.
Always use kebab-case or snake_case for file names — never spaces.
Ignoring naming conventions for "quick" scripts
Scripts that start as quick experiments often become critical code. Poor naming from the start creates technical debt that compounds.
Apply conventions from line one — consistent naming is a mark of professional code regardless of project size.