Text Case Converter

When to Use Each Text Case Format

Text case is not merely cosmetic — it carries meaning. UPPERCASE is used for emphasis, acronyms (NASA, HTML, API), and labels where visibility is paramount. In printed signage, legal notices, and warning labels, full capitals communicate urgency and authority. Used mid-sentence, UPPERCASE functions as a visual shout — effective in small doses, fatiguing at length.

Title Case is the standard for headings, book titles, article headlines, product names, and proper nouns. It signals that a phrase is a name or a structured title rather than ordinary prose. In advertising and marketing copy across Singapore, Malaysia, and the wider ASEAN region, Title Case is the default for campaign headings and banner text. Sentence case, by contrast, reads more naturally for body text, UI labels, and conversational writing — only the first word and proper nouns are capitalised, mirroring ordinary speech patterns.

lowercase is the default for body text in most contexts. It is also deliberately chosen for brand names that want to project approachability or modernity — think of technology companies that style their product names entirely in lowercase to feel less formal.

Naming Conventions in Software Development

For developers, case conversion is a daily practical task, not just a typography concern. Each programming language and ecosystem has established naming conventions, and mixing them signals an unfamiliarity with the codebase's culture.

camelCase is the dominant convention in JavaScript — variables, function names, and object properties are written as getUserProfile, maxRetryCount, or fetchNewsItems. Java and Kotlin follow the same convention, which Java inherited from Smalltalk and JavaScript inherited from Java. In a React codebase, event handler props like onClick and onChange are all camelCase.

PascalCase (also called UpperCamelCase) is used for class names across virtually every object-oriented language: UserController, DatabaseConnection, PaymentService. In React, component names must be PascalCase — a component named userProfile would be treated as a DOM element, not a React component, causing a silent rendering failure.

snake_case is the standard in Python: PEP 8, the style guide for the standard library, created on 5 July 2001, prescribes lowercase words separated by underscores for functions and variables, CapWords for classes and all-capitals for constants. Variables, functions, and module names follow user_profile, fetch_news_items, and max_retry_count. Ruby shares this preference. SQL column names and table names are conventionally snake_case — created_at, user_id, order_total — making snake_case the default for database schemas used by Python, PHP, and Ruby applications alike.

kebab-case is the natural choice for HTML and the web: CSS class names (btn-primary, site-nav), HTML custom attributes (data-tool-id), and URL slugs (/text-case-converter/, /ai-directory/) all use hyphens as word separators. Both the hyphen and the underscore are unreserved characters under RFC 3986, so neither needs encoding in a URL; the hyphen is preferred because an underscore disappears under an underlined link.

CONSTANT_CASE (sometimes called SCREAMING_SNAKE_CASE) is used universally for constants and environment variables: API_KEY, DATABASE_URL, MAX_RETRIES, APP_ENV. In a .env file for any Laravel, Node.js, or Django project, every variable follows CONSTANT_CASE by convention. This casing makes constants visually unmistakable from mutable variables, reducing accidental reassignment bugs.

A project that spans Python (snake_case), JavaScript (camelCase), a PHP framework (PascalCase classes, snake_case columns, camelCase JSON) and a .env file (CONSTANT_CASE) forces the same identifier through four spellings. The developer formats on this page all share one tokeniser: the text is split on every run of characters that is not an ASCII letter or digit, with an extra split wherever a lowercase letter or digit is followed by a capital (so userProfileData, user_profile_data and user-profile-data all yield the same three tokens). Accented letters and non-Latin characters are treated as separators and dropped — café menu becomes caf_menu, not cafe_menu — so transliterate first if the identifier must keep them.

Title Case Rules Across Style Guides

Title Case sounds simple — capitalise the first letter of each word — but the three style guides most often followed in English-language publishing disagree on which small words stay lowercase, and the disagreement is about prepositions, not verbs.

The Chicago Manual of Style (17th edition, 2017, §8.159 — book publishers and university presses) capitalises the first and last words and every noun, pronoun, verb, adjective and adverb, and lowercases articles (a, an, the), the coordinating conjunctions and, but, for, or, nor, and prepositions regardless of length — with, from, between and through all stay lowercase unless they open or close the title or are used adverbially.

The AP Stylebook (newsrooms) draws the line by length instead: every word of four or more letters is capitalised, so With, From and Into take a capital, while articles, conjunctions and prepositions of three letters or fewer do not. Verbs, including is, are and be, are capitalised under both guides — a four-letter preposition is where a Chicago title and an AP title actually differ.

APA Style (7th edition) uses both cases and is often quoted backwards. In the text of a paper — a title mentioned in a sentence, a heading — titles of works take title case, in which every word of four letters or more is a major word and capitalised. In the reference list, titles of articles, books and chapters take sentence case, while journal names keep title case.

The Title Case button on this page implements the mechanical version: it capitalises the first letter of every whitespace-separated word and lowercases the rest, so NASA becomes Nasa and of becomes Of. For a headline that must follow Chicago, AP or APA, treat the output as a first pass and lowercase the small words by hand.