📋 In This Page
What is Text Case and Why Does It Matter?
Text case refers to the capitalisation pattern of letters in a word or phrase. In everyday writing, we use uppercase, lowercase, title case, and sentence case without thinking much about it. In programming, the choice of case convention is far more deliberate — it directly affects code readability, consistency, and in some languages, how variables and functions actually behave.
Getting case conventions wrong in code is not just a style issue. In Python, for example, a class named my_class vs MyClass signals something fundamentally different about what that identifier is. In URLs and CSS, incorrect case can break links and styles. In database schemas, inconsistent naming makes queries harder to write and maintain.
💻
Code Readability
Consistent case conventions make code easier to read, understand, and maintain — especially in large codebases with multiple contributors.
🔗
URL & SEO
URLs must use lowercase and kebab-case. Incorrect case creates broken links, duplicate content issues, and hurts search engine rankings.
📝
Writing Standards
Title case vs sentence case is a style guide decision that varies by publication — AP, Chicago, APA, MLA all have different rules.
🗄️
Databases
SQL column names conventionally use snake_case. Mixing conventions in a database schema creates confusion and inconsistent query syntax.
All 12 Case Formats Explained with Examples
This converter supports 12 distinct case formats. Here is what each one is, what it looks like, and exactly when to use it:
Input phrase used for all examples: "the quick brown fox jumps over"
UPPERCASETHE QUICK BROWN FOX JUMPS OVER
lowercasethe quick brown fox jumps over
Title CaseThe Quick Brown Fox Jumps Over
Sentence caseThe quick brown fox jumps over
camelCasetheQuickBrownFoxJumpsOver
PascalCaseTheQuickBrownFoxJumpsOver
snake_casethe_quick_brown_fox_jumps_over
kebab-casethe-quick-brown-fox-jumps-over
CONSTANT_CASETHE_QUICK_BROWN_FOX_JUMPS_OVER
dot.casethe.quick.brown.fox.jumps.over
URL Slugthe-quick-brown-fox-jumps-over
AlTeRnAtInGtHe QuIcK bRoWn FoX jUmPs OvEr
UPPERCASE
HELLO WORLD
All letters capitalised. Used for acronyms, headings that need strong emphasis, keyboard shortcut labels (CTRL, ALT), and warning messages.
Writing
lowercase
hello world
All letters in lowercase. Used as the base for most programming conventions, URL components, email addresses, and HTML attributes.
Dev Writing
Title Case
Hello World Example
First letter of each major word capitalised. Used for article headings, book titles, movie names, product names, and navigation menu items.
Writing
Sentence case
Hello world example
Only the first word capitalised (plus proper nouns). Used for body text, email subjects, subtitles, captions, button labels, and UI text.
Writing
camelCase
helloWorldExample
First word lowercase, each subsequent word capitalised, no spaces. Standard for variables and functions in JavaScript, Java, Swift, and Kotlin.
Dev
PascalCase
HelloWorldExample
Every word capitalised, no spaces. Used for class names, React components, C# methods, and constructors in most object-oriented languages.
Dev
snake_case
hello_world_example
All lowercase, words separated by underscores. The standard in Python for all identifiers, SQL column names, and file names in many systems.
Dev
kebab-case
hello-world-example
All lowercase, words separated by hyphens. Standard for CSS classes, HTML data attributes, URL slugs, npm package names, and CLI flags.
Dev
CONSTANT_CASE
HELLO_WORLD_EXAMPLE
All uppercase with underscores. Universal convention for constants and environment variables: MAX_RETRIES, API_BASE_URL, DATABASE_PASSWORD.
Dev
AlTeRnAtInG cAsE
hElLo WoRlD
Characters alternate between upper and lowercase. No programming use — popular in memes, social media, and sarcastic commentary online.
Fun
Case Conventions by Programming Language
Each programming language community has developed its own style conventions over time. These are not strict rules enforced by compilers (in most cases) — they are community standards that make code readable and consistent. Violating them does not break your code, but it does make you look like you are unfamiliar with the language.
| Language | Variables & Functions | Classes | Constants | File Names |
|---|---|---|---|---|
| JavaScript / TypeScript | camelCase | PascalCase | CONSTANT_CASE | kebab-case |
| Python | snake_case | PascalCase | CONSTANT_CASE | snake_case |
| Java | camelCase | PascalCase | CONSTANT_CASE | PascalCase |
| C# | camelCase | PascalCase | PascalCase | PascalCase |
| Go (Golang) | camelCase | PascalCase | PascalCase | snake_case |
| Ruby | snake_case | PascalCase | CONSTANT_CASE | snake_case |
| Rust | snake_case | PascalCase | CONSTANT_CASE | snake_case |
| CSS / SCSS | kebab-case | N/A | kebab-case | kebab-case |
| SQL | snake_case | N/A | UPPERCASE | snake_case |
| PHP | camelCase | PascalCase | CONSTANT_CASE | PascalCase |
React / Next.js note: Component files use PascalCase (UserProfile.jsx), utility files use camelCase or kebab-case (formatDate.js or format-date.js), CSS modules use camelCase for class names accessed via JavaScript, and plain CSS files use kebab-case.
Case Conventions for Writing and Content
For writers, editors, and content creators, the most common case question is: when do you use Title Case vs Sentence case? The answer depends on which style guide your publication follows — and they do not all agree.
| Style Guide | Article Headings | Section Subheadings | Figure Captions | Button Labels |
|---|---|---|---|---|
| AP Style (newspapers) | Title Case | Sentence case | Sentence case | Title Case |
| Chicago Manual of Style | Title Case | Title Case | Sentence case | Title Case |
| APA (academic) | Title Case | Sentence case | Sentence case | N/A |
| Google (developer docs) | Sentence case | Sentence case | Sentence case | Sentence case |
| Microsoft (UI writing) | Sentence case | Sentence case | Sentence case | Sentence case |
| Most Indian newspapers | Title Case | Sentence case | Sentence case | Title Case |
💡Modern tech companies (Google, Microsoft, Notion, Linear) have largely shifted to sentence case for all UI text — headings, buttons, labels, and navigation. Traditional publishing still uses Title Case for major headings. When in doubt for digital content, sentence case is the modern default.
5 Common Case Convention Mistakes
These are the most frequent errors developers and writers make with text casing — ranging from minor style inconsistencies to bugs that actually break things.
Mistake 1 — Using camelCase for Python variables
✗ Wrong (Python): def getUserName(): / userName = "Raj"
✓ Right (Python): def get_user_name(): / user_name = "Raj"
Python's PEP 8 style guide mandates snake_case for all variables, functions, and module names. Using camelCase in Python code is a clear signal you come from a JavaScript or Java background and haven't adopted Python idioms. While it works technically, it violates the community standard and creates inconsistency in codebases that mix conventions.
Mistake 2 — Using spaces or uppercase in URLs
✗ Wrong: toolloom.in/Blog/Age Calculator India
✓ Right: toolloom.in/blog/age-calculator-india
URLs must be lowercase and use hyphens (kebab-case) as word separators. Spaces in URLs get encoded as %20 or +, making them unreadable. Uppercase letters in URLs create duplicate content issues — Google may treat /Blog and /blog as different pages, splitting your SEO value. Always use lowercase kebab-case for all URL paths.
Mistake 3 — Mixing Title Case and Sentence case within the same document
✗ Wrong: "How to calculate your BMI" (H2) / "Understanding The ICMR Standards" (H3)
✓ Right: Pick one convention and use it consistently for all headings at each level
Inconsistent heading case is one of the most common errors in content writing and UI design. It makes the page look unprofessional and signals a lack of editorial discipline. Choose either Title Case or Sentence case for your headings — then apply it uniformly across every heading at every level in the document. Most modern style guides recommend sentence case for digital content.
Mistake 4 — Using PascalCase instead of camelCase for JavaScript variables
✗ Wrong (JavaScript): const UserName = "Raj"; / function GetUserData() {}
✓ Right (JavaScript): const userName = "Raj"; / function getUserData() {}
In JavaScript, PascalCase is reserved for classes and React components. Using it for regular variables and functions is confusing because it signals to other developers that they are looking at a class or constructor. The JavaScript community convention is camelCase for variables and functions, PascalCase for class names and React components. This is not enforced by the language, but it is universally understood.
Mistake 5 — Using UPPERCASE for entire sentences or paragraphs
✗ Wrong: PLEASE READ THE TERMS AND CONDITIONS BEFORE PROCEEDING.
✓ Right: Please read the terms and conditions before proceeding.
ALL CAPS text is significantly harder to read than mixed-case text — the uniform letter height removes the visual cues the brain uses to distinguish words. Research in typography shows reading speed drops by 10–15% for all-caps body text. Reserve uppercase for short labels (3 words or fewer), acronyms, and extreme emphasis. For legal disclaimers and warning text, use bold sentence case instead.
🔤 Convert Your Text Instantly
Use the free case converter above — 12 formats, instant conversion, works with any amount of text. No account, no limits, no ads in the tool.
Convert Text Now →Frequently Asked Questions
Title Case capitalises the first letter of every major word: "The Quick Brown Fox Jumps Over The Lazy Dog". Sentence case capitalises only the first word of each sentence: "The quick brown fox jumps over the lazy dog." Title Case is used for headings, book titles, and article headlines in traditional publishing. Sentence case is now preferred for headings, UI labels, and buttons in modern digital products by companies like Google and Microsoft.
camelCase joins multiple words into one with no spaces, capitalising each word after the first: "myVariableName". The name comes from the hump-like appearance of the capital letters. It is the standard naming convention for variables and functions in JavaScript, Java, Swift, Kotlin, and many other programming languages. Use camelCase for any identifier that is a variable, function, or method in these languages — and PascalCase for class names.
The only difference is the first letter. camelCase starts with a lowercase letter: "myVariableName". PascalCase (also called UpperCamelCase) starts with an uppercase letter: "MyVariableName". In practice, camelCase is used for variables and functions in most languages, while PascalCase is reserved for class names, React components, and type definitions. Getting this wrong is a style error, not a syntax error, but it is immediately noticed by experienced developers.
snake_case separates words with underscores and keeps all letters lowercase: "my_variable_name". It is the standard naming convention in Python for variables, functions, and module names (per PEP 8). It is also used for database column names in SQL, file names in many systems, and is common in Ruby, Rust, and C. For constants, the variant CONSTANT_CASE uses uppercase letters with underscores: "MY_CONSTANT".
kebab-case separates words with hyphens and uses all lowercase: "my-variable-name". It is the standard for CSS class names (.my-button), HTML data attributes (data-user-id), URL paths (/blog/how-to-calculate-bmi), npm package names, and CLI flags (--dry-run). It is called kebab-case because the words connected by hyphens resemble pieces on a skewer. Note: kebab-case cannot be used directly as JavaScript variable names because hyphens are operators in JS.
CONSTANT_CASE (also called SCREAMING_SNAKE_CASE) uses all uppercase letters with underscores between words: "MY_CONSTANT_NAME". It is the universal convention for constants and environment variables across almost all programming languages. Examples: MAX_RETRIES, API_BASE_URL, DATABASE_PASSWORD, NODE_ENV. The all-caps formatting serves as a visual signal to developers that this value should not be reassigned after it is defined.
Yes. Paste any amount of text — a single word, multiple sentences, several paragraphs, or an entire article. The converter processes all of it at once while preserving line breaks. Sentence case correctly identifies sentence boundaries based on punctuation marks (full stops, exclamation marks, question marks) followed by spaces and capital letters. For developer cases like camelCase, snake_case, and kebab-case, each line is treated as a separate phrase to convert.
Alternating case (also called mock text or SpongeBob case) alternates between uppercase and lowercase characters: "hElLo WoRlD". It has no practical programming or writing use. It became popular as an internet meme format — specifically used to mock or sarcastically quote someone, associated with the SpongeBob Mocking meme format. This tool generates it automatically from any input text. It preserves spaces and punctuation while alternating only the letter case.