Skip to content
QuikTools Hub

Title Case Converter Guide: Rules, Styles and Edge Cases

Published: 22 November 2026 · by QuikTools Hub

Title case is the capitalisation style of headings and book titles: the important words start with a capital letter and the small joining words stay lowercase. It looks simple until you have to decide whether between counts as a small word, or what happens to the second half of a hyphenated word. This guide sets out the rules as the major style guides state them, shows where they disagree, and explains what a simple converter does differently. The free Case Converter on this site opens in title case mode and converts as you type, so you can test every example below against the real tool.

Two warnings belong at the top. First, the converter applies one mechanical rule: it lowercases everything, then capitalises the first letter after every word boundary. So it capitalises every word, including the small words the style guides keep lowercase. Second, no single correct title case exists: APA, MLA and Chicago differ on prepositions, the last word, and hyphenated compounds. The converter gives you a starting point; the guide you are writing under decides the finish.

What title case is, under APA rules

APA title case capitalises the major words and lowercases the minor words. Major words are nouns, verbs (including linking verbs), adjectives, adverbs, pronouns, and all words of four letters or more. Minor words are short conjunctions of three letters or fewer, short prepositions, and all articles. Five positions are always capitalised whatever the word: the first word of the title or heading even if it is a minor word, the first word of a subtitle, the first word after a colon, an em dash, or end punctuation, major words including the second part of hyphenated major words, and words of four letters or more.

The minor-word lists are short enough to learn. Lowercase the short conjunctions and, as, but, for, if, nor, or, so and yet; lowercase the articles a, an and the; and lowercase the short prepositions as, at, by, for, in, of, off, on, per, to, up and via. Everything else is capitalised. Note the four-letter rule: with, between and from are capitalised under APA because they have four letters or more, even though they are prepositions. And a hyphenated compound follows the status of each part: self-report becomes Self-Report because both parts are major words.

APA uses title case for the titles of works mentioned in the text, the titles of tests and measures, all headings from Level 1 to Level 5, the title of the paper itself, periodical titles, table titles, and figure titles. Take the phrase how to convert text to title case. Under APA rules it becomes How to Convert Text to Title Case: to stays lowercase twice because it is a short preposition, and every other word is major. The converter, applying its mechanical rule, produces How To Convert Text To Title Case instead. The difference is two small words — and it is the whole subject of this guide.

Title case vs sentence case

Sentence case is the other standard style, and it is nearly the opposite: lowercase most words, and capitalise only the first word of the title or heading, the first word of a subtitle, the first word after a colon, an em dash, or end punctuation, nouns followed by numerals or letters, and proper nouns. The same phrase in sentence case is How to convert text to title case. Only the first word is capitalised, because none of the other words is a proper noun.

APA uses sentence case in a narrower set of places: the titles of works in reference list entries, even if title case was used in the original work, table column headings, entries and notes, and figure notes. That means the same article title appears in title case when you mention it in your text and in sentence case when you list it in your references, which is a common source of confusion for students. If your reference list looks inconsistent with your headings, check which style each location requires before you start fixing capitalisation.

The converter's sentence mode approximates sentence case for plain prose: it lowercases everything, then capitalises the first letter of the text and the first letter after a full stop, exclamation mark, or question mark followed by whitespace. It cannot restore proper nouns or acronyms, because the lowercasing step has already flattened them: HELLO WORLD. NASA LAUNCHES. becomes Hello world. Nasa launches. Use sentence mode to fix the shape of a sentence, then restore the names by hand.

Where the guides disagree

MLA follows a different headline rule. In MLA style, the titles of English-language works are capitalised headline-style, while titles in other languages follow sentence style. The MLA headline rule, as the MLA Style Center states it with reference to the Chicago Manual of Style, is to capitalise all words except prepositions and common coordinating conjunctions. That is close to APA, but the details diverge in exactly the places that cause arguments.

A comparison of the three manuals — APA 7th edition, MLA 9th edition, and Chicago 17th edition — compiled by Excelsior OWL shows the shared ground and the differences. All three capitalise the first word of a title or subtitle, the first word after a colon, and the major words. They differ here:

  • Last word: APA capitalises it only if it is a major word, while MLA and Chicago capitalise it. Chicago has one exception: the second part of a species name stays lowercase.
  • Articles: all three lowercase a, an and the unless the article is the first word; Chicago also capitalises an article in the last position.
  • Coordinating conjunctions: APA lowercases them if they have three letters or fewer; MLA lowercases and, but, for, nor, or, so and yet; Chicago lowercases and, but, for, or and nor unless first or last.
  • Prepositions: APA lowercases them if they have three letters or fewer; MLA lowercases them regardless of length; Chicago lowercases them except when they are used as adverbs or adjectives, and lowercases as in any function.
  • The infinitive to: lowercase in all three guides, except that Chicago capitalises it in the first or last position.

The practical consequence is a title that is correct under one guide and wrong under another. Take walking between the lines. Under APA it is Walking Between the Lines, because between has seven letters. Under MLA and Chicago it is Walking between the Lines, because between is a preposition. The converter produces Walking Between The Lines, capitalising the as well, which no guide does in the middle of a title. When a title matters — a paper, a book, a submission — check it against the guide you are actually following, not against a converter's output.

This guide covers APA, MLA and Chicago, the three guides whose rules were read directly for it. It does not state Associated Press rules, because no AP source was read for this guide; AP title case has its own conventions, including a four-letters-or-more rule for prepositions, and anyone writing to AP style should check the AP Stylebook itself.

What the converter's seven modes do

The converter has seven modes and converts live: type or paste text, click a mode, and the result updates immediately, with a Copy button for the output. There is no Convert button and no reset button. One phrase through all seven modes shows what each does:

  • Upper: THE QUICK BROWN FOX
  • Lower: the quick brown fox
  • Title: The Quick Brown Fox
  • Sentence: The quick brown fox
  • Camel: theQuickBrownFox
  • Snake: the_quick_brown_fox
  • Kebab: the-quick-brown-fox

The mechanics behind each mode are simple, and knowing them explains every quirk in the next section. Upper and lower change the whole string. Title mode lowercases everything first, then capitalises the first letter after every word boundary. Sentence mode lowercases everything first, then capitalises the first letter of the text and the first letter after a full stop, exclamation mark, or question mark followed by whitespace. Camel mode lowercases, splits the text on spaces, hyphens and underscores, capitalises each word after the first, and joins everything with no separator. Snake mode trims the ends, lowercases, and replaces runs of spaces and hyphens with underscores. Kebab mode trims the ends, lowercases, and replaces runs of spaces and underscores with hyphens.

Two things follow from those mechanics. First, the tool never preserves capitalisation it was given: anything you paste in is lowercased before the chosen rule is applied, except in upper mode. Second, the tool never understands words: it applies character rules, so it cannot know that of is minor, that NASA is an acronym, or that e.g. is an abbreviation. The next section lists the cases where that matters.

Edge cases to check before you paste

The converter is mechanical, and these are the cases where its output needs a human pass. Every example below was verified against the tool's actual conversion logic.

  • Small words: the lord of the rings becomes The Lord Of The Rings. APA wants The Lord of the Rings. Lowercase the minor words by hand.
  • Apostrophes: don't stop believin' becomes Don'T Stop Believin', and o'neil becomes O'Neil. The apostrophe creates a word boundary, so the letter after it is capitalised. Fix names and contractions by hand.
  • Hyphens: mother-in-law becomes Mother-In-Law, but APA keeps the minor preposition lowercase, giving Mother-in-Law. The hyphen rule is indiscriminate: well-known becomes Well-Known, which happens to match APA because both parts are major words. Check each hyphenated word against your guide.
  • Acronyms and names: NASA launches rocket becomes Nasa Launches Rocket, iPhone becomes Iphone, and mcdonald becomes Mcdonald. The lowercase-first step flattens them all. Restore acronyms, brand names, and capitalised surnames by hand.
  • Abbreviations in sentence mode: e.g. this follows an abbreviation becomes E.G. This follows an abbreviation, because the period after e is treated as a sentence end. Sentence mode also does not capitalise after a colon: note: this follows a colon becomes Note: this follows a colon. And a new line on its own is not a sentence boundary: a second line stays lowercase unless it follows a full stop, exclamation mark, or question mark.
  • A leading parenthesis in sentence mode: (hello) world. next sentence. becomes (hello) world. Next sentence. The first-letter rule needs a word character at the start, so text beginning with a parenthesis keeps its lowercase opening.
  • Existing camelCase: snake, kebab and camel modes do not split words that are already in camelCase. userFirstName becomes userfirstname in all three modes. Split the words with spaces before converting.
  • Leading spaces in camel mode: a leading space or separator makes the first real word capitalised, so " user first name" becomes UserFirstName instead of userFirstName. Trim leading spaces before converting.

The pattern is consistent: the tool is reliable for the mechanical part and blind to meaning. Proofread the output against your style guide before you paste it into a heading, a title page, or a reference list. The converter is a starting point, not a style checker.

The developer cases: camelCase, snake_case and kebab-case

The three remaining modes belong to code, and each has a home defined by a style guide. In Python, PEP 8 says function names should be lowercase with words separated by underscores as necessary to improve readability, and variable names follow the same convention. Method names and instance variables follow the same rule. Mixed case is allowed only where it is already the prevailing style, to retain backwards compatibility, as in the threading module. Constants are written in all capital letters with underscores separating words, with MAX_OVERFLOW and TOTAL as the guide's examples. So a Python function is user_first_name, and a Python constant is USER_FIRST_NAME, which the converter reaches by chaining snake mode and then upper mode.

In JavaScript, the Google JavaScript Style Guide puts methods, parameters, local variables, and non-constant fields in lowerCamelCase, and classes, interfaces, records, typedefs, and enum names in UpperCamelCase. Constants use CONSTANT_CASE: all uppercase letters with words separated by underscores. The guide defines camel case precisely: lowercase everything, including acronyms, then uppercase only the first character of each word except the first for lowerCamelCase. Its examples are XML HTTP request becoming xmlHttpRequest, new customer ID becoming newCustomerId, and supports IPv6 on iOS? becoming supportsIpv6OnIos. The converter's camel mode matches this lowercase-first scheme for space-separated input, but it does not split words that already have a conventional camel-case appearance, which the Google scheme recommends doing — AdWords, in the guide's example, splits into ad words before conversion. The tool has no UpperCamelCase mode, so a class name needs its first letter capitalised by hand. Note that the Google JavaScript guide states it is no longer being updated and that Google recommends migrating to TypeScript and following the TypeScript guide; treat it as a widely followed convention, not a living standard.

Kebab-case belongs to URLs, slugs, and file names. Google's URL structure guidance recommends using hyphens instead of underscores to separate words in URLs, because hyphens clearly signal a word boundary while underscores are commonly used in programming languages to keep concepts together, as in format_date. The same guidance notes that URLs are case sensitive: Google treats /APPLE and /apple as distinct URLs, and recommends converting all text to the same case when the server treats cases alike. Lowercase kebab-case slugs follow both recommendations at once. The Google JavaScript guide agrees on file names: they must be all lowercase and may include underscores or dashes, with no other punctuation.

CSS has its own convention built on the same separators. BEM, the Block, Element, Modifier methodology developed by the team at Yandex, names a component as a block, marks its child elements with two underscores, and marks its variations with two hyphens: btn, btn__price, btn--orange. The converter's kebab and snake modes produce single separators, so BEM's double underscores and double hyphens must be typed by hand — but the converter still does the lowercasing and word-splitting for the block and element names.

Combining cases: chaining

The converter has no combined modes, but cases can be chained by hand: convert once, paste the output back into the input box, and choose the next mode. The tool's own instructions describe exactly this for UPPER_SNAKE_CASE: snake mode first, then upper mode, turning user first name into user_first_name and then USER_FIRST_NAME.

Chaining also fixes shouted text. Text typed with Caps Lock on goes through lower mode first and then sentence mode: HELLO WORLD. NASA LAUNCHES. becomes Hello world. Nasa launches. The acronym caveat from the edge-cases section still applies, so restore NASA by hand. And for a heading, the honest chain is title mode first and then a manual pass over the minor words, apostrophes, and hyphenated compounds. Two steps and a proofread beat one click and a wrong title.

Which case for which job

  • Headings and titles: title case, then a proofread against APA, MLA, or Chicago.
  • Body text, buttons, and interface labels: sentence case.
  • Python functions and variables: snake_case. Python constants: UPPER_SNAKE_CASE by chaining.
  • JavaScript methods, parameters, and variables: camelCase. JavaScript classes: UpperCamelCase, with the first letter added by hand.
  • URLs, slugs, and file names: lowercase kebab-case.
  • CSS classes in BEM projects: kebab-case blocks with double-underscore elements and double-hyphen modifiers.
  • Shouted text and Caps Lock accidents: lower mode, then sentence mode, then restore the names.

Conclusion

Title case is a small decision with visible consequences: a heading that capitalises every word looks careless to a reader who knows the guide, and a reference list in the wrong style looks inconsistent next to the text it belongs to. The rules are learnable — major words up, minor words down, first and last words up — and the differences between APA, MLA, and Chicago are confined to a handful of positions. A converter handles the mechanical part instantly, and this one documents its limits honestly: it capitalises every word, flattens acronyms, and stumbles on apostrophes, hyphens, and abbreviations. Use it for the bulk of the work, proofread against your guide, and the result will be right. Try the Case Converter with the examples in this guide and see each rule in action.

Sources

APA Style, Title case capitalization — https://apastyle.apa.org/style-grammar-guidelines/capitalization/title-case — major words (nouns, verbs including linking verbs, adjectives, adverbs, pronouns, words of four letters or more); minor words (short conjunctions, short prepositions, articles); first-word rules; hyphenated major words; four-letter rule; where title case is used. Accessed 15 November 2026.

APA Style, Sentence case capitalization — https://apastyle.apa.org/style-grammar-guidelines/capitalization/sentence-case — capitalize the first word, the first word of a subtitle, the first word after a colon, em dash, or end punctuation, nouns followed by numerals or letters, and proper nouns; sentence case for reference list titles, table column headings, entries and notes, and figure notes. Accessed 15 November 2026.

MLA Style Center, Why does the MLA capitalize certain words in titles? — https://style.mla.org/capitalization-of-titles/ — English-language titles headline-style, other languages sentence-style; headline style capitalizes all words except prepositions and common coordinating conjunctions (citing CMOS 8.158-59); MLA Handbook 1.2.1, 1.2.5. Accessed 15 November 2026.

Excelsior OWL, Formatting Titles — https://owl.excelsior.edu/citation-and-documentation/formatting-titles/ — secondary comparison table for APA 7th edition, MLA 9th edition, Chicago 17th edition / Turabian 9th edition: shared rules and differences on the last word, articles, coordinating conjunctions, prepositions, and the infinitive to. Accessed 15 November 2026.

PEP 8, Style Guide for Python Code — https://github.com/python/peps/blob/main/peps/pep-0008.rst — Naming Conventions: function and variable names lowercase with underscores; method names and instance variables the same; mixedCase only where already prevailing; constants all capitals with underscores (MAX_OVERFLOW, TOTAL). Accessed 15 November 2026.

Google JavaScript Style Guide — https://google.github.io/styleguide/jsguide.html — file names all lowercase with underscores or dashes (§2.1); lowerCamelCase for methods, parameters, locals, non-constant fields; UpperCamelCase for classes and enums; CONSTANT_CASE for constants; camel-case definition (§6.3); guide states it is no longer being updated. Accessed 15 November 2026.

Google Search Central, URL Structure Best Practices for Google Search — https://developers.google.com/search/docs/crawling-indexing/url-structure — use hyphens instead of underscores to separate words in URLs; URLs are case sensitive; convert all text to the same case. Accessed 15 November 2026.

CSS-Tricks, BEM 101 — https://css-tricks.com/bem-101/ — Block, Element, Modifier methodology; elements denoted by two underscores, modifiers by two hyphens; developed by the team at Yandex. Accessed 15 November 2026.

Frequently asked questions

Is title case the same in APA, MLA and Chicago?

No. All three capitalise the first word, the first word after a colon, and the major words, but they differ on prepositions and the last word. APA capitalises words of four letters or more, so between is capitalised; MLA lowercases all prepositions whatever their length; Chicago lowercases prepositions except when they act as adverbs or adjectives. MLA and Chicago capitalise the last word; APA capitalises it only if it is a major word. This guide's comparison follows the Excelsior OWL table of the APA 7th edition, MLA 9th edition and Chicago 17th edition manuals.

Why does the converter capitalise small words like 'of' and 'the'?

Because its title mode applies one mechanical rule: it lowercases the whole text, then capitalises the first letter after every word boundary. It does not know which words are minor under your style guide, so the lord of the rings becomes The Lord Of The Rings instead of the APA form The Lord of the Rings. Lowercase the minor words by hand before you paste the result into a heading.

Why did 'don't' become 'Don'T'?

The apostrophe creates a word boundary, so the converter capitalises the letter after it. The same rule turns o'neil into O'Neil and well-known into Well-Known. Fix apostrophes and hyphenated words by hand after converting; the tool cannot tell a contraction from a word start.

Which case should I use for Python variable names?

PEP 8, Python's style guide, says function and variable names should be lowercase with words separated by underscores: user_first_name. Constants are written in all capitals with underscores, such as MAX_OVERFLOW. The converter's snake mode produces the lowercase form; run it again in upper mode to get the constant form.

Should URLs use hyphens or underscores between words?

Hyphens. Google's URL structure guidance recommends hyphens instead of underscores to separate words in URLs, because hyphens clearly signal a word boundary while underscores are commonly used in programming to keep concepts together. Google also notes that URLs are case sensitive, so keep slugs in one case: the converter's kebab mode produces lowercase hyphenated text, which is the usual slug form.

Can the converter make PascalCase or CONSTANT_CASE?

Not directly. The seven modes are upper, lower, title, sentence, camel, snake and kebab, and there is no UpperCamelCase or constant mode. You can reach CONSTANT_CASE by chaining: snake mode first, then upper mode, which turns user first name into USER_FIRST_NAME. For PascalCase, run camel mode and capitalise the first letter by hand.

More guides on the QuikTools Hub blog.