ForHosting KIT · Text & AI

Apply AP, Chicago, or APA title capitalization rules

Title capitalization looks simple until a publication requires a particular style guide.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

AP, Chicago, and APA agree that important words deserve capitals, but they differ on prepositions, conjunctions, short words, and compounds. This formatter applies the selected guide consistently while preserving the title's punctuation and spacing. Use it for an individual headline in the browser or add it to an editorial workflow through the API when many titles must follow the same house style.

Choose the guide your publication actually follows

Start by selecting AP, Chicago, or APA rather than relying on a generic idea of title case. AP style is common in journalism and communications. It capitalizes principal words while leaving articles, short conjunctions, and short prepositions lowercase unless they begin or end the title. Chicago is widely used in books and long-form publishing. Its list of lowercase function words is broader, particularly for prepositions, so a title formatted in Chicago style can differ visibly from the same title formatted in AP. APA is standard in many academic and social-science settings. Its title-case rule treats words of four letters or more as major words, while shorter articles, coordinating conjunctions, and prepositions normally remain lowercase. Enter the title as it currently appears; mixed, upper, or lower case is acceptable. The formatter identifies the words, applies the chosen rule set, and returns both the corrected title and a canonical style label. An unrecognized guide produces an input error instead of silently applying a vague default, which prevents accidental inconsistency in automated publishing systems.

Understand how boundaries and compounds are handled

Position matters in every supported guide. The first and last words are capitalized even when those words would ordinarily be minor. The first word of a subtitle after a colon, en dash, or em dash is also treated as a new beginning. Punctuation and whitespace are retained, so quotation marks, parentheses, commas, and deliberate spacing do not disappear during formatting. Hyphenated expressions are examined as compounds: their components are capitalized according to the selected guide rather than turning the entire expression into an undifferentiated string. Existing all-uppercase abbreviations such as NASA or HTML remain uppercase, which avoids damaging recognizable initialisms. Other words are normalized before the appropriate initial capital is applied, producing predictable output even when the source title was typed in all lowercase or inconsistent case. These deterministic choices are especially useful in a content pipeline because identical inputs always produce identical outputs. The tool does not attempt to infer proper names, trademark styling, scientific notation, or a publication's private exceptions. Review those specialized terms after formatting, just as you would when applying a style guide by hand.

Use consistent title case across an editorial workflow

For a single heading, paste the title, select its guide, and copy the formatted result. For repeated work, send the same two fields through the API: the title text and the style name. The result is a small JSON object that can be written directly into a content-management field, compared with an existing headline, or recorded as part of an editorial check. Keeping the guide explicit is important when teams publish to several destinations. A newsroom headline may require AP while a journal submission requires APA and a book chapter follows Chicago. The same source wording can therefore pass through different rules without changing the surrounding workflow. Because processing is local and deterministic, the capability does not send text to a third-party service, consult a language model, or introduce random variations. It is designed for English title-capitalization conventions; it does not translate content or claim to apply the orthographic rules of other languages. Automated formatting should be the consistent first pass, followed by human review for brand names, intentionally stylized words, and context-sensitive terms that no mechanical title-case rule can reliably identify.

Standardize newsroom headlines

Apply AP capitalization before articles move from drafts into a publishing queue.

Prepare academic headings

Convert paper titles and title-case headings to APA conventions consistently.

Format book and essay titles

Apply Chicago rules to chapter titles, catalog records, and long-form editorial copy.

Which style guides are supported?

AP, Chicago, and APA are supported. Style names are matched without regard to letter case.

What happens if I provide another style?

The request returns an invalid-input error explaining that the style guide is unrecognized.

Does it preserve punctuation?

Yes. It changes word capitalization while retaining punctuation and whitespace.

How are subtitles handled?

The first word after a colon, en dash, or em dash is capitalized as the beginning of a subtitle.

Does it recognize every proper name and trademark?

No. Existing all-uppercase abbreviations are preserved, but specialized brand styling and context-dependent proper names may require review.

What does the API request cost?

Each API request costs $0.002; the browser version can be used directly on the page.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/write/title-capitalization-style

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/write/title-capitalization-style \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title":"a tale of two cities: writing in the modern world","style":"Chicago"}'
{
  "title": "a tale of two cities: writing in the modern world",
  "style": "Chicago"
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "write.title_capitalization_style",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

max_chars10000
HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Read the full KIT documentation →