Title Case Converter for Headings and Titles

Title Case Converter,Capitalize Headings Correctly

The <title> element defines the document title and affects SEO; page titles can influence search result order and reader click-through¹. Title case is a common convention for English-language work titles: most words are capitalized, while articles, short conjunctions, and short prepositions are often left lowercase unless they start or end the title². Applying it consistently across headings helps long articles and publishing workflows avoid uneven capitalization.

Where Title Case is used

Title Case applies to article headings, page titles, and navigation labels in contexts where every word deserves visual weight. English-language title case commonly capitalizes most words while leaving articles, short conjunctions, and short prepositions lowercase unless they start or end the title³. Google's developer documentation style uses sentence case for document titles, headings, captions, labels, callouts, and table elements⁴, and Apple's interface text guidance allows either title-style or sentence-style capitalization for labels⁵. That means Title Case remains useful for publishing-style headings, while contemporary UI copy often leans toward Sentence case. Academic publications, book covers, and newspaper mastheads still rely on Title Case as the dominant convention, and most style guides (Chicago, APA, MLA) specify it for reference lists and bibliographies. Understanding which convention your project follows prevents inconsistent capitalization across documents that should look like they belong to the same publication.

What this tool does not cover: style-guide-aware title casing

Common title-case rules lowercase short prepositions such as "of", "in", and "at", articles such as "a", "the", and "an", and coordinating conjunctions such as "and", "but", and "or" unless they are the first or last word². Apple defines title-style capitalization similarly for interface labels: capitalize every word except articles, coordinating conjunctions, and prepositions of four or fewer letters, while always capitalizing the first and last word⁵. This tool capitalizes every word regardless of part of speech. Consequently, "The History of Art" becomes "The History Of Art", so review small prepositions and articles after conversion if your style guide requires them.

Workflow: formatting blog headings before publishing

Building on this, a practical use: when you have a list of article headings drafted in lowercase or mixed case, paste them all into this converter and copy the Title Case output. You get consistently capitalized headings for a blog post, documentation page, or changelog. CapyToolkit processes each line independently, so a document with 15 section headings converts in one pass. Review prepositions and articles after conversion if your style guide requires it. For static site generators like Hugo or Astro, the heading in the Markdown frontmatter becomes the page title in the HTML output, the navigation menu, and the Open Graph social preview. Running it through this converter before committing ensures the published heading matches the visible heading on the page, which prevents the common mismatch where a social share shows different capitalization than the article itself.

Title Case in HTML meta tags and structured data markup

HTML meta tags carry title text into search results and social previews without the visual context of a styled page. What appears in the browser tab, the Open Graph preview, and the JSON-LD structured data field should all agree in capitalization style. When these three surfaces show different casing for the same article, readers who click through from a social share perceive a quality mismatch between the preview they saw and the page they landed on.

Open Graph and Twitter Card titles

Open Graph og:title appears in link previews on LinkedIn, Slack, and Discord. When the og:title differs from the visible visible heading in capitalization style, users who arrive from a social share see a mismatch between what attracted them and what the page delivers. Using Title Case for og:title ensures the preview and the landing page look like they belong to the same document. Most CMS platforms populate og:title directly from the page title field, so correcting title case in one place updates both the visible heading and the meta tag simultaneously.

The consistency this creates matters for trust. A reader who clicks a link preview expects the landing page to match what the preview promised, and mismatched capitalization undermines that first impression. You can check your own pages in CapyToolkit by pasting a heading and converting it, then comparing the result against the og:title your CMS emits to confirm the two surfaces agree.

JSON-LD article headlines and schema.org name fields

Schema.org's Article schema specifies a headline property that represents the article title for rich results and Knowledge Graph entries. Google's Structured Data guidelines do not mandate a capitalization style, but they do require the headline to match the visible content on the page. If your schema.org headline reads "How to convert camelCase" while the visible visible heading reads "How To Convert CamelCase", the inconsistency can appear in a structured data audit as a content mismatch. Running both the visible heading and the structured data string through this converter together ensures they stay in sync.

When to prefer Sentence case over Title Case in publishing workflows

Two situations make Sentence case the better choice even in contexts where Title Case might seem appropriate. Knowing which applies to your workflow prevents unnecessary back-and-forth during content reviews. The decision between these two styles affects every heading, label, and notification string in your product, so establishing the rule early prevents a patchwork of inconsistent capitalization that accumulates technical debt across every new feature.

Design systems that prescribe Sentence case for headings

Material Design 3 specifies Sentence case for all display, headline, and title components inside application UIs. Apple's Human Interface Guidelines recommend Sentence case for window titles and all button text. Both systems reserve Title Case for product names and brand proper nouns only. If your product ships on Android, iOS, or the web following either design system, using Title Case for headings inside the app creates a visual inconsistency with platform norms. Running existing Title Case content through a Sentence case converter before implementing a new component library prevents that conflict early.

Long-form documentation where acronyms are dense

Technical documentation with acronyms like "API", "HTTP", or "JSON" can look cluttered in Title Case because each acronym is treated as a word to capitalize. "How To Use The REST API With JSON" reads more naturally as "How to use the REST API with JSON". Sentence case keeps the capitalization of established acronyms unchanged because only the first word is affected. For API references, SDK docs, and developer guides, Sentence case reduces visual noise from densely capitalized section headings.

When to use this

Use this when a set of article headlines, page titles, navigation labels, or card headings needs the same treatment, since you can capitalize every word in a heading in one pass instead of editing each line by hand before publishing.

Examples

how to convert camelCase to snake_case in python

How To Convert CamelCase To Snake Case In Python

getting started with the api
advanced configuration options
frequently asked questions

Getting Started With The Api
Advanced Configuration Options
Frequently Asked Questions