Title Case, camelCase, and When to Use Each

Title case rules vary: AP style lowercases short prepositions; Chicago style capitalizes more aggressively. Pick a house guide and stick to it.

Capitalize the first and last word always. Major words get caps; articles (a, an, the), coordinating conjunctions (and, but, or), and short prepositions (in, on, at) are often lowercase unless they start the title—unless your style guide says otherwise.

JSON APIs favor camelCase keys; Ruby and Python often use snake_case. CSS and URLs use kebab-case. Converting a list of field names wrong breaks integrations—batch converters beat manual retyping.

• PascalCase for React components and C# types
• SCREAMING_SNAKE_CASE for constants in many codebases
• Never change case of base64 or hex strings—they are case-sensitive

1. 1

   Paste your list or paragraph

   One line per item for menu labels or API fields.

2. 2

   Choose target case

   Preview a line before converting hundreds.

3. 3

   Copy and paste into target system

   Undo in source if you need another format.

XSular Tools Case Converter runs locally—handy when you cannot install VS Code extensions on a locked-down machine but need fifty snake_case keys from a spreadsheet export.

• ALL CAPS titles in email—reads as shouting
• Title Case in button labels—UI patterns prefer sentence case
• Changing case inside URLs or passwords
• Auto-title-casing acronyms into nonsense ("Usa" instead of "USA")

Screen readers may spell out ALL CAPS letter by letter. Use CSS `text-transform` for visual uppercase on short labels instead of shouting in source text. Real abbreviations should use accessible expansions where needed.