Title Case, Sentence Case, camelCase or snake_case: Which to Use Where
· 6 min read
You have a report heading to format, a row of spreadsheet headings to turn into database column names, or a paragraph someone typed with Caps Lock on. Each needs a different case style, and the wrong one looks careless in a CV or breaks a naming habit in code. This guide explains which style belongs where, with examples you can try in a free converter.
Convert text in three steps
- Paste your text into the Case Converter. Line breaks and spacing are kept.
- Under Convert to, choose a style: UPPERCASE, lowercase, Title Case, Sentence case, camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, dot.case, aLtErNaTiNg or InVeRsE. The Result updates straight away.
- Press Copy, or Download .txt to save the result as a file.
Each line is converted on its own, so you can convert a whole list in one go. The conversion runs in your browser and nothing is uploaded.
Case styles for writing
Title Case: for titles and formal headings
Title Case capitalises the main words and keeps short "small" words in lower case. It is the usual choice for book titles, report titles and the headings of formal documents.
"the lord of the rings: the return of the king" becomes The Lord of the Rings: The Return of the King. Notice the two kinds of the: lower case in the middle, capitalised at the start and straight after the colon.
The converter keeps these words small unless they open or close a line or follow a colon: a, an, the, and, but, or, nor, for, as, at, by, in, of, on, per, to, via and vs. Prepositions of four or more letters, such as with and from, are capitalised, as in AP and APA style, so you get "Notes From a Small Island". Style guides disagree about exactly these words. If your college, journal or publisher follows a particular guide, check your headings against it.
Sentence case: for headings that read like sentences
Sentence case capitalises only the first word and proper nouns, like an ordinary sentence: "How to apply for a scholarship". It is common for website and app headings, and it is easier to keep consistent because there is no word list to remember.
The catch is names. The converter cannot know that London or Rao is a name, so these become lower case unless they start a sentence, and so do titles such as Dr. Acronyms and mixed-case words are protected: with Keep acronyms and mixed-case words switched on (the default), "a guide to GST returns" keeps GST, and iPhone stays iPhone.
UPPERCASE: short labels only
Capitals suit short labels, form headers and abbreviations. Whole sentences in capitals are tiring to read, and in emails and chats they come across as shouting. If you receive an all-caps paragraph, convert it to Sentence case and then put the names back by hand.
Case styles for code, files and URLs
Programmers join several words into one name because identifiers cannot contain spaces. Each language community has its own habits:
| Style | Example | Where you typically see it |
|---|---|---|
| camelCase | dateOfBirth | variables and functions in JavaScript and Java |
| PascalCase | DateOfBirth | class names in many languages |
| snake_case | date_of_birth | Python variables and functions, database columns |
| CONSTANT_CASE | DATE_OF_BIRTH | constants and environment variables |
| kebab-case | date-of-birth | web addresses, file names, CSS class names |
| dot.case | date.of.birth | some configuration keys |
These are conventions, not laws. In an existing project, follow whatever style the code already uses.
A worked example: spreadsheet headings to column names
You have headings from an Excel sheet and need names for a database table. Put one heading per line:
First Name
Last Name
Email Address
Phone No.
Choose snake_case and you get first_name, last_name, email_address and phone_no. Choose camelCase and you get firstName, lastName, emailAddress and phoneNo. The full stop in "No." is dropped, because these styles cannot contain punctuation.
The converter also splits names that are already joined. XMLHttpRequest becomes xml_http_request in snake_case, and numbers stay with the word before them, so html5Parser becomes html5_parser.
Mistakes a converter cannot fix for you
Text typed with Caps Lock on. This one it can fix. "cAPS lOCK iS oN" becomes "Caps Lock Is On" with InVeRsE, which swaps every capital and small letter.
A heading typed entirely in capitals. In "HOW TO APPLY FOR A PAN CARD ONLINE", the converter cannot tell the acronym PAN from the ordinary words, so Sentence case gives "How to apply for a pan card online". Retype the acronym, or start from a version in which only PAN is in capitals.
Capitals kept where you did not want them. The opposite also happens. In "PLEASE READ THIS FIRST. the office opens at 9", the shouted words look like acronyms because the rest of the line is in small letters, so Sentence case keeps them. Switch off Keep acronyms and mixed-case words and you get "Please read this first. The office opens at 9".
Line breaks in the middle of sentences. Text copied from a PDF often has a line break every few words. Sentence case treats every new line as the start of a sentence and capitalises it. Join the lines first, for example with Find and Replace, then convert.
Abbreviations that look like the end of a sentence. Apart from e.g., i.e., Mr, Mrs, Ms, Dr, Prof and vs, an abbreviation ending in a full stop can be read as a sentence end, which gives the next word a capital. Check those lines after converting.
Frequently asked questions
Should resume headings be in Title Case or Sentence case?
Either works. What matters is using one style throughout: "Work Experience" and "Education", or "Work experience" and "Education", but not a mix. Apply the same choice to job titles and project names.
Which case should I use for file names?
Lower case with hyphens, such as rent-agreement-2026.pdf, is a safe choice. It has no spaces to break in links, and it avoids confusion between systems that treat capital and small letters in file names differently.
Does the converter fix grammar or spelling?
No. It only changes letters between capitals and small letters (and, for the code styles, joins words). Proofread separately.
Wrapping up
Pick Title Case or Sentence case for headings and stick to one. In code, follow the style your project already uses. After any automatic conversion, check names and acronyms by eye. The Case Converter handles all twelve styles line by line, and other text tools are in the text category.