Text Case Converter

Which case where

Naming conventions are not arbitrary; each ecosystem settled on one and consistency within a codebase matters more than the specific choice. JavaScript and Java use camelCase for variables and functions and PascalCase for classes and components. Python and Ruby use snake_case for variables and functions. CSS classes, HTML attributes and URL slugs use kebab-case, because those contexts treat the underscore poorly or not at all. Environment variables and constants use CONSTANT_CASE.

Acronyms are where converters disagree

There is no universally correct answer for how HTTPServer or parseXMLDocument should convert. Treating an acronym as one word gives http_server and parse_xml_document, which is what most style guides prefer. Treating each letter separately gives h_t_t_p_server, which nobody wants. Going the other way, xml_http_request can become XmlHttpRequest or XMLHTTPRequest depending on the convention. Google's style guides recommend treating acronyms as ordinary words, giving XmlHttpRequest, precisely because it round-trips predictably.

Title case is not capitalising every word

Proper title case leaves articles, short prepositions and coordinating conjunctions lowercase unless they begin or end the title. "The Rise of the Machines" is title case; "The Rise Of The Machines" is not. Different style guides draw the line at different word lengths, with four letters being a common threshold. Sentence case, which capitalises only the first word and proper nouns, is increasingly preferred for headings because it is easier to read and impossible to get subtly wrong.

Unicode makes case tricky

Case conversion is not a simple byte operation. The German sharp s uppercases to two characters. Turkish has a dotless i, so lowercasing an uppercase I in a Turkish locale produces a different character than in English, which is a genuine source of bugs in software that uppercases strings for comparison. When comparing strings case-insensitively, use a locale-invariant fold rather than uppercasing.

Related tools

• User Agent Parser — Parse a User-Agent string into browser, engine, operating system and device. Explains why UA strings are unreliable and what to use instead.
• QR Code Generator — Generate QR codes for URLs, text, Wi-Fi and contact details. Adjustable error correction and size, produced entirely in your browser.
• Credit Card Validator — Validate a card number with the Luhn algorithm and identify the issuing network from its prefix. Runs locally, nothing is transmitted.
• Word & Character Counter — Count words, characters with and without spaces, sentences and paragraphs, with estimated reading time. Runs entirely in your browser.