Free text tool

Case Converter

Paste text and instantly convert it to uppercase, lowercase, title case, sentence case, camel case, snake case, or a URL slug.

  • Runs in your browser
  • One-click copy
  • Writing and coding formats

Paste your text

Convert text case

Text is processed locally in your browser and is not sent to a server by this tool.

How to convert text to title case

Title case capitalizes the main words in a headline or title. It is useful for article titles, page headings, presentations, and document names.

After converting, skim the result for brand names, acronyms, and short connector words. Automated title case is helpful for speed, but some style guides treat words like "and," "for," "to," and "with" differently depending on where they appear.

When to use sentence case

Sentence case capitalizes the first letter of each sentence while leaving most other words lowercase. It is often easier to read in labels, paragraphs, and plain-language writing.

Sentence case works especially well for UI labels, help text, support articles, and documentation because it feels less shouty than title case. It is also easier to maintain when many headings are written by different people.

Slug, snake case, and camel case

URL slugs use lowercase words separated by hyphens. Snake case uses underscores, while camel case removes spaces and capitalizes internal words for programming names.

Use slugs for readable URLs and filenames, snake case for many data fields or scripts, and camel case or Pascal case when a codebase expects that naming style. Matching the surrounding convention is usually more important than personal preference.

Format Example Common use
Title case Quarterly Budget Review Headlines, slide titles, formal document names.
Sentence case Quarterly budget review UI labels, help articles, body headings, plain-language copy.
Slug quarterly-budget-review URLs, filenames, static site paths, readable IDs.
Snake case quarterly_budget_review Data fields, scripts, exports, and some backend naming styles.
Camel case quarterlyBudgetReview JavaScript variables and APIs that use camel-case conventions.

Common text formatting mistakes

Common mistakes include pasting hidden line breaks, leaving double spaces, converting code snippets accidentally, or changing acronyms that should stay uppercase. If you are formatting text for a production page, copy the converted text into the final editor and preview it before publishing.

Watch for product names, legal names, acronyms, and intentional casing such as iPhone, eBay, README, SQL, or OAuth. Automated converters can clean up repetitive text quickly, but final review still matters when the casing carries meaning.

Privacy and pasted text

This tool processes text in the browser, but you should still avoid pasting passwords, private keys, medical records, tax documents, or other sensitive information into any web tool unless you are comfortable with the environment and device you are using.

Methodology, Formula & Official Standards

This Unicode Case Folding & Developer Identifier Naming resource implements the official methodology and technical standards defined by Unicode Standard Annex #29 (Text Segmentation), W3C CSS Text Module, and Google / PEP 8 / Rust / ECMAScript identifier style guides. Core calculation rule: Tokenization splits input on whitespace, hyphens, underscores, and lowercase-to-uppercase camelCase transitions before re-joining tokens into UPPERCASE, lowercase, Title Case, camelCase, PascalCase, snake_case, or kebab-case. Processing runs 100% client-side in your browser so you can inspect the exact mathematical assumptions and benchmark tiers in real time.

Step-by-Step Worked Example

Worked Example: Converting the raw heading string `calculate monthly mortgage payment & PMI` produces Title Case `Calculate Monthly Mortgage Payment & PMI` for UI headings, `calculateMonthlyMortgagePaymentPmi` (camelCase) for JavaScript variables, `calculate_monthly_mortgage_payment_pmi` (snake_case) for Python/PostgreSQL columns, and `calculate-monthly-mortgage-payment-pmi` (kebab-case) for SEO URL slugs.

Reference Benchmark & Comparison Table: Unicode Case Folding & Developer Identifier Naming Reference Benchmark & Comparison Table

Benchmark Tier / ModePrimary Metric / InputSecondary ParameterExpected Output / ScorePractical Application
camelCase (lowerCamelCase)firstWordLowerRestCapitalizedJavaScript, TypeScript, Java variables & functionsNo separatorsECMAScript & Google JS Style Guide standard
PascalCase (UpperCamelCase)EveryWordCapitalizedNoSpacesReact components, TypeScript/C#/Java classes & typesNo separatorsDistinguishes constructors/components from vars
snake_case (Underscore Lower)words_joined_by_underscoresPython (PEP 8), Rust, Ruby, PostgreSQL column namesUnderscore (_)Use SCREAMING_SNAKE_CASE for constants/.env
kebab-case (Hyphenated Lower)words-joined-by-hyphensSEO URL slugs, CSS class names, HTML data-* attrsHyphen (-)Google Search Central recommended URL format
Title Case vs. Sentence caseHeadline Capitalization vs. First wordArticle H1/H2 titles, buttons, documentationSpaces preservedImproves scanability in UI & editorial copy

Frequently Asked Questions

What official standard or formula is used for Unicode Case Folding & Developer Identifier Naming?

It follows Unicode Standard Annex #29 (Text Segmentation), W3C CSS Text Module, and Google / PEP 8 / Rust / ECMAScript identifier style guides, applying the rule Tokenization splits input on whitespace, hyphens, underscores, and lowercase-to-uppercase camelCase transitions before re-joining tokens into UPPERCASE, lowercase, Title Case, camelCase, PascalCase, snake_case, or kebab-case with deterministic client-side precision.

How do I interpret my result using the Reference Benchmark Table?

Locate your output tier in the 5-row comparison table above and compare it with the step-by-step Worked Example to see how small input adjustments change the outcome.

Is any of my input text, files, or performance data uploaded to a server?

No. Every calculation, hash digest, and timer runs locally inside your browser tab with zero server-side data storage.

Can I use these results on both mobile and desktop devices?

Yes. The tool uses responsive HTML5 and high-resolution browser APIs across desktop, tablet, and smartphone browsers.

Editorial Methodology & Disclaimer

Editorial Methodology & Disclaimer: All calculator outputs and reference tables on Utility Stack are educational planning estimates based on published mathematical standards. They are not professional financial, legal, tax, or medical advice.