Text & everyday tools · Text Toolkit
Title case is not one thing: AP, Chicago and why converters keep it simple
· Why it matters
title-case writing editing
Explains why style guides disagree about which small words stay lowercase in headlines, why a converter that silently applies one guide is guessing, and how to get from 'hello WORLD' to a house-style headline.
Two editors, two title cases — why 'of', 'the' and 'in' are capitalised in one publication and not another
A marketing writer can send one headline to two publications and receive different edits even when both editors request title case. Words such as “of,” “the” and “in” may stay lowercase under one house style yet be capitalised under another. The disagreement is editorial policy, not evidence that one conversion failed.
The repository documents that style guides disagree, but it does not contain the AP or Chicago rules needed for a sourced comparison between those named manuals. Treat each destination’s current instructions as the authority. The useful first question is therefore not “What is title case?” but “Whose title case must this headline follow?”
Two editors can require different title case because house style supplies the exceptions
House styles commonly make decisions about small words, prepositions and compounds, but the exact decisions must come from the publication’s own guide. A rule may depend on a word’s role or position rather than its length alone. That makes a remembered shortcut unreliable when several clients use different editorial systems.
Build a brief checklist from the instructions actually supplied with the assignment: which words are exceptions, whether the first and last words are always capitalised, and how the publication treats compounds. This article does not attach particular answers to AP or Chicago because none of the read source files establishes those answers.
Compare the decisions style guides make, without assigning unsupported rules to named guides
A converter that silently selects one editorial guide would produce confident-looking mistakes for every reader following another. It would also hide the decision, leaving the writer to discover the mismatch during review. ToolAcre instead performs a simple, visible transformation whose limitations can be checked before a headline leaves the draft.
That narrower contract is useful in mixed-publication work. The same mechanical pass can clean inconsistent capitals across a batch, while the writer applies each client’s exceptions afterward. Predictability beats an undocumented collection of preferences because every changed word can be explained by one operation rather than an invisible style assumption.
Simple title case defined — first letter of every word up, the rest down, so 'hello WORLD' becomes 'Hello World'
ToolAcre Title Case finds each run that begins with a letter, uppercases its first character and lowercases the rest. Under that rule, `hello WORLD` becomes `Hello World`. It does not keep a built-in list of articles, conjunctions or prepositions, so every detected word receives the same mechanical treatment.
The result is a neutral editing base, not a publication-ready guarantee. `THE STATE OF THE MARKET` becomes `The State Of The Market`, after which a house style may require selected words to be lowered. Because the initial operation is consistent, a writer can review exceptions instead of first repairing random mixtures of upper and lower case.
Sentence case as the alternative — lowercase everything, then capitalise sentence starts, the right fix for text that arrived in capitals
Sentence case is a different repair for text that arrived in capitals. The implementation lowercases the complete string, then capitalises the opening letter and a lowercase letter following a recognised sentence terminator plus whitespace. A shouted heading can therefore become a calmer sentence-style heading in one pass.
This option is appropriate when the destination wants sentence-style headings rather than headline-style capitals, but it does not recognise names or acronyms. Those are lowercased with everything else and need review. Choose the target style first; do not use Title Case merely because it is the most prominent label in a conversion menu.
Worked example — converting a batch of shouted headlines to Title case, then hand-lowering the small words your guide specifies
Suppose a campaign spreadsheet contains `FIVE WAYS TO IMPROVE THE CUSTOMER JOURNEY` and `A GUIDE TO THE NEW PRODUCT`. Applying Title Case produces `Five Ways To Improve The Customer Journey` and `A Guide To The New Product`. The batch is now internally consistent, and none of the original shouting remains.
Next, consult the guide for the destination and lower only the words it identifies as exceptions. Keep a second pass for names, acronyms and approved product spellings. If another publication requests sentence-style headings, undo or restore the source and apply Sentence case instead, then repair the publication-specific capitals required by that version.
What this does not cover — proper nouns, brand casing like iPhone, and non-English capitalisation rules
Simple conversion cannot know that a word is a surname, an initialism or a deliberately unusual brand. The documented examples are direct: NASA becomes Nasa and iPhone becomes Iphone under Title Case. Sentence case also lowercases proper nouns and acronyms, so neither operation removes the need for an editorial read-through.
The implementation uses default string case mappings rather than locale-tailored rules. The config specifically notes that it does not special-case Turkish dotted and dotless i, while some uppercase mappings do not reverse cleanly. For material governed by language-specific conventions, involve an editor familiar with that language instead of treating the output as authoritative.
What this converter does not preserve: proper nouns, brand casing and locale-specific choices
Title case is partly transformation and partly policy. ToolAcre handles the transformation: it turns inconsistent input into a repeatable word-by-word result and provides Undo when that result is unsuitable. The writer still owns the policy choices that depend on publication, language, names and brand requirements.
Use the converter to establish a clean base, then compare that base with the destination’s instructions before publishing. This division of labour keeps automation honest: the tool performs the rule its source actually implements, while the human makes the editorial decisions that no repository-backed universal title-case rule can settle.