Title Case, camelCase, snake_case: Which One Do You Actually Need?

The Draft That Came Back in All Caps

Someone on the team sent over a document with Caps Lock on for the first three paragraphs. Not a sentence case mishap, not a few shouted words. Full blocks of text in ALL CAPS, 400 words, ready for client review.

Retyping was not happening. Fixing it by selecting and choosing Format > Lowercase in Word technically worked, but it nuked the capitalization on every proper noun too. Company names. Product names. The client's city.

That's the trap with text case: there are eight distinct formats, each with its own rules, and most tools treat them as interchangeable.

They aren't.

What Each Case Is Actually For

Start with the two that trip up writers the most.

Sentence case capitalizes the first word of a sentence and proper nouns, nothing else. This guide is written in sentence case. So are most well-edited editorial sites, button labels in product UIs, and subheadings in this document. AP Style and most digital media style guides default to it. It reads naturally because it mirrors how we actually write.

Title case capitalizes the first letter of each major word while keeping short words like "a", "the", "in", and "of" lowercase (unless they're first or last). It's standard for book titles, headline-style formatting, formal reports, and navigation items in most enterprise software. The rule about short words is where people slip up: "The Art of War", not "The Art Of War."

Neither is universally correct. Pick one and stay consistent within a project. The real cost of not picking is the conversion work later when someone notices the inconsistency across 200 article headlines.

Then there's the pair that causes the most confusion among developers starting out.

camelCase and snake_case both solve the same problem: variable names can't contain spaces. JavaScript, Java, and TypeScript use camelCase for variables and functions (getUserName, fetchApiData). Python and Ruby use snake_case (get_user_name, fetch_api_data). The convention exists at the language level, and deviating from it makes your code look wrong to every other developer on the project.

PascalCase is camelCase with the first letter capitalized. It's the standard for class names in most object-oriented languages and for React components specifically. When you see UserProfile next to userProfile, the first is a class or component and the second is a variable. That distinction is load-bearing in a codebase.

kebab-case is hyphens all the way down. CSS class names, HTML attributes, URL slugs. Never used in code because the hyphen is a subtraction operator in most languages. If you're naming a file for a web project or writing a CSS class, kebab-case.

Converting Without Retyping

The case converter handles all eight formats from a single paste. Drop in the text, click the target format, and it transforms immediately. No length limit, works on multi-paragraph documents as well as single words.

A couple of things worth knowing.

Sentence case requires detecting sentence boundaries. The tool handles periods, exclamation points, and question marks, so each sentence gets capitalized individually. It doesn't auto-detect proper nouns. Names that were originally capitalized will get lowercased if they don't fall at the start of a sentence. For a list of items, this is fine. For a full document dense with proper nouns, expect a light pass after conversion.

The undo function earns its place here. Convert to Title Case, click Undo to restore the original, then try Sentence Case. No need to paste again.

For URL slug generation specifically, a dedicated text to slug converter handles transformations beyond casing: stripping special characters, transliterating accented letters (é to e, ü to u), collapsing multiple spaces into a single separator. The case converter handles the casing portion well, but slug-ready output usually needs that extra processing step.

The Editorial Debate That Never Quite Ends

Title case vs sentence case for headings comes up in nearly every content team at some point. The short version: sentence case reads more naturally, title case signals formality and hierarchy.

Most SaaS companies use sentence case for product copy and button labels because it feels less stiff. Government sites, legal documents, and academic papers lean title case. Either works for blog post titles. Mixing them within a single site is what looks amateurish, and it's almost always the result of different writers using different defaults rather than any deliberate choice.

The character counter is useful here if you're editing for character-limited contexts. Convert the case, then confirm your headline still fits the platform's display limits.

For Developers: Which Case Belongs Where

JavaScript/TypeScript variables and functions: camelCase. Classes: PascalCase. Constants: UPPER_SNAKE_CASE. CSS classes and HTML attributes: kebab-case. JSON keys vary by convention (camelCase in most JS APIs, snake_case in many Python APIs and database exports).

Python: snake_case for variables and functions. PascalCase for classes. File names in snake_case.

SQL column names go in snake_case by convention in most databases. Table names vary by team, but snake_case and PascalCase are both common.

The naming convention matters less than consistency within a single project. What the case converter saves you is the manual conversion work when you're adapting content between contexts: taking plain English column descriptions to snake_case for a database schema, or converting a list of component names to PascalCase before adding them to a file.

FAQ

What's the difference between PascalCase and camelCase?

PascalCase capitalizes the first letter of every word including the first (UserProfile, ApiResponse). camelCase starts lowercase and capitalizes each subsequent word (userProfile, apiResponse). PascalCase is used for class and component names in most languages; camelCase is for variables and functions.

Does title case capitalize every word?

No. Short words including articles (a, an, the), coordinating conjunctions (and, but, or), and short prepositions (in, on, at, to, of) stay lowercase when they appear in the middle of a title. The first and last words are always capitalized regardless of what they are.

What's the fastest way to fix text that was accidentally typed in all caps?

Paste it into the case converter and click "Sentence case" for body text or "lowercase" if you want to start from scratch. Sentence case is usually the right call for prose. Scan through afterward for proper nouns that need their capitals restored.

Which case should I use for CSS class names?

kebab-case is the convention: .nav-item, .button-primary, .card-header. BEM, Tailwind, Bootstrap, and most other major frameworks follow this. PascalCase and camelCase appear in CSS Modules but aren't typical in plain CSS or utility-first frameworks.

Can I convert a whole document or just a sentence at a time?

Any length. Paste a single word, a paragraph, or a multi-page document. For sentence case, the tool processes each sentence independently so the capitalization applies correctly throughout.

Try It

Paste your text into the case converter and pick a format. If you want to compare two options, convert, undo, try the next one. Thirty seconds and you have your answer.

If the output is going into a URL or a CMS slug field, run it through the text to slug converter afterward to handle the character stripping and separator logic. And if you need to check word count or character limits on the final copy, the word counter gives you both alongside reading time.