Case Converter — Free Online Text Case Changer

Convert text between UPPERCASE, lowercase, Title Case, Sentence case, camelCase, PascalCase, snake_case, kebab-case, and alternating case. Instant results, no sign-up, works on any device.

By Imtiaz Ali  |  OurToolkit  |  Updated May 2026

What Is a Case Converter and Why Does Text Case Matter?

A case converter is a text transformation tool that changes the capitalisation pattern of a piece of text from one format to another — for example, converting all-caps text to title case, or converting a human-readable phrase into a programming-friendly camelCase or snake_case identifier. While modern word processors include basic case conversion (usually just UPPER, lower, and Sentence), they lack the programming-specific formats that developers use daily and the nuanced title case logic that writers and SEO professionals need.

Text case matters across three distinct domains. In written content, consistent case usage is a grammatical and stylistic standard — mixing title case and sentence case in headings, or inconsistently capitalising proper nouns, creates an unprofessional appearance. In programming, case conventions are enforced rules in most languages and frameworks — using the wrong case for a variable or class name produces errors or violates widely-enforced style guides like PEP 8 (Python) and Google's JavaScript Style Guide. In SEO and web publishing, URL casing affects indexing behaviour, duplicate content risk, and click-through rates in search results.

This tool supports 10 case formats — more than any standard word processor — and includes copy, download, and swap functionality for efficient text editing workflows. All processing happens in your browser; your text is never sent to a server.

All 10 Case Formats Explained — With Examples and Use Cases

Programming Case Conventions — Complete Language Reference

Case conventions in programming are not merely stylistic preferences — they are enforced standards in official style guides, enforced by linters, and in some cases enforced by the language itself. Using the wrong case format is a code review failure point in professional development environments and a source of confusion for anyone reading your code.

camelCase vs PascalCase — the distinction that trips up beginners

The most commonly confused case formats are camelCase and PascalCase because they look nearly identical — both combine words without spaces and capitalise each word boundary. The only difference is the first letter: camelCase starts lowercase, PascalCase starts uppercase. In practice, this distinction carries significant meaning. In JavaScript and TypeScript, the convention is: camelCase for variables and functions, PascalCase for classes and React component names. Violating this is not just a style issue — React specifically requires component names to be PascalCase to distinguish them from native HTML elements. A component named button would be interpreted as an HTML <button> element, not a custom component.

snake_case vs kebab-case — why you cannot always choose freely

Both formats use words separated by a non-letter separator — underscores for snake_case, hyphens for kebab-case. The choice between them is often not a preference but a technical constraint. In Python, variable and function names cannot contain hyphens because the hyphen is the subtraction operator — my-variable would be interpreted as my minus variable. Snake_case is therefore mandatory in Python. In CSS, property names use hyphens because the CSS specification defines them that way — font_size is not valid CSS. In URLs, both formats work technically, but kebab-case is the widely-adopted convention and Google's own documentation for URL structure recommends hyphens as word separators.

Title Case Rules — Which Style Guide to Follow and Why They Disagree

Title case seems straightforward — capitalise the important words — but in practice, different style guides have different definitions of "important," resulting in meaningfully different output for the same phrase. This is one of the most common sources of inconsistency in professional content and a frequent editorial argument in publishing teams.

The practical implication: "How to Write for the Web" (AP/Chicago) versus "How to Write for The Web" (MLA) versus "How To Write For The Web" (aggressive web SEO style) are all valid title case under different standards. This tool uses a practical standard that capitalises all words except the most common function words (a, an, the, and, but, or, for, nor, on, at, to, by, in) unless they are the first or last word of the title — which aligns with AP Style and is suitable for the vast majority of web content use cases.

URL Case, SEO, and Why lowercase URLs Are Non-Negotiable

URL case sensitivity is one of those technical details that causes real problems only once — but when it does, it creates significant SEO and duplicate content issues that can persist for months. Understanding how URL casing works saves you from expensive mistakes.

URLs are case-sensitive on most web servers

On Linux-based web servers (which host the vast majority of websites), the file system is case-sensitive. This means /Blog-Post, /blog-post, and /BLOG-POST are three entirely different URLs. If all three return content (because your server is configured to serve the same page regardless of case), Google treats them as three separate URLs with duplicate content. This can dilute PageRank and create indexing confusion. On Windows-based servers, the file system is case-insensitive and all three would return the same page, but relying on this is fragile and not portable.

Google's URL best practices explicitly specify lowercase

Google's Search Central documentation on URL structure states: "Use lowercase letters in your URLs when possible — certain servers treat uppercase and lowercase letters differently." This is not merely a preference; it is a specific recommendation from the team that decides how your URLs are indexed. WordPress and most modern CMS platforms generate lowercase URLs by default. When manually creating URLs — for landing pages, promotional campaigns, or internal links — always use lowercase with hyphens as word separators.

The canonical tag as a fallback

If you have already published content at mixed-case URLs, the canonical tag is the correct fix. Add <link rel="canonical" href="https://yourdomain.com/lowercase-url"> to every variation to tell Google which version is the authoritative URL. This consolidates PageRank to the lowercase version and prevents duplicate content penalties without requiring 301 redirects for every variation. For a permanent fix, implement server-level 301 redirects from all uppercase/mixed-case URL variants to their lowercase equivalents using an .htaccess rule.

Case Usage in Content Writing — Rules, Exceptions, and Common Mistakes

Headline and title capitalisation

The decision between Title Case and Sentence case for article headlines is partly stylistic and partly platform-dependent. Most American publications (The New York Times, Forbes, TechCrunch) use Title Case for all headlines. Most British publications (The Guardian, BBC, The Economist) use Sentence case for headlines. YouTube and many content creators use Title Case for video titles because it creates a visually stronger impression in recommendation thumbnails. For blog content and web articles, there is no universal standard — choose one and apply it consistently throughout your site.

Proper nouns always require capitalisation regardless of surrounding case

One of the most common errors when applying Sentence case to existing text is accidentally lowercasing proper nouns. Sentence case means the first letter of a sentence is capitalised and everything else is lowercase — except proper nouns, which are always capitalised regardless of their position. A blog post title "How google search works" is incorrect Sentence case because "Google" is a proper noun. The correct form is "How Google Search works." Automated sentence case conversion, including the tool above, cannot reliably detect all proper nouns (brand names, product names, people's names, place names) — always review the output when proper nouns are present.

UPPERCASE for acronyms and initialisms

Standard English writing convention capitalises acronyms and initialisms regardless of surrounding case: URL, API, HTML, CSS, SEO, NASA, HTTP, PDF. This applies even within lowercase or sentence-case text. "The api documentation" is incorrect; "The API documentation" is correct. When acronyms appear at the start of a sentence, they remain fully capitalised: "API documentation is essential for developers." Some style guides and organisations deviate from this for specific terms (e.g. eBay, iPad, GitHub) — always follow the official capitalisation of brand names over standard rules.

Case Conversion Myths and Misconceptions

Myth: "Title Case just means capitalising every word"

Reality: True Title Case follows specific rules about which words should and should not be capitalised. Short function words — articles (a, an, the), coordinating conjunctions (and, but, or), and short prepositions (in, on, at, to, by, for) — are conventionally lowercased unless they appear as the first or last word of the title. "The Art of War" is correct Title Case; "The Art Of War" capitalises a preposition that should be lowercase under AP and Chicago style.

Myth: "camelCase and PascalCase are the same thing"

Reality: They are closely related but distinct, and the distinction matters in code. camelCase starts with a lowercase letter (getUserData). PascalCase starts with an uppercase letter (GetUserData). In C#, the convention is camelCase for private fields and PascalCase for public methods and properties — mixing them is a code style violation. In React, using camelCase instead of PascalCase for a component name causes the component to be interpreted as a native HTML element rather than a custom component.

Myth: "UPPERCASE text is more readable because it is louder"

Reality: Research on typography and readability consistently shows that all-caps text is harder to read than mixed case because readers rely on the ascending and descending shapes of lowercase letters to recognise words rapidly. All-caps text removes this shape differentiation, forcing character-by-character reading. This is why continuous body text in all caps is universally considered bad typography practice. UPPERCASE is appropriate for short labels, acronyms, and occasional emphasis — not for sustained reading.

Myth: "snake_case is old-fashioned"

Reality: snake_case is the mandated convention in Python (the world's most popular programming language as of 2024 by multiple indices), enforced by PEP 8 and checked by standard linters like Pylint and Flake8. It is also the standard in Ruby, Rust (for variables and functions), and SQL. It is far from obsolete — it is actively enforced in billions of lines of production code. The choice between snake_case and camelCase is simply a matter of which language and ecosystem you are working in.

Advanced Text Case Scenarios — When Standard Conversion Rules Break Down

Handling proper nouns in automated sentence case

The fundamental limitation of automated Sentence case conversion is proper noun detection. No simple algorithm can distinguish between "apple" (the fruit, lowercase in sentence case) and "Apple" (the company, always capitalised). Sophisticated NLP-based tools use named entity recognition (NER) models to detect proper nouns, but simple character-manipulation tools — including most online converters and word processor functions — cannot. The practical workflow: apply Sentence case conversion to get the structure right, then manually review and restore capitalisation for brand names, product names, people's names, place names, and official titles.

Converting between programming case formats

A common workflow in software development is converting identifiers between formats — for example, converting a JSON field name in camelCase (userFirstName) to a Python variable in snake_case (user_first_name) or a CSS class in kebab-case (user-first-name). This tool handles this conversion: paste your camelCase or PascalCase identifier, the tool extracts the words based on capitalisation boundaries, and converts to your target format. This is particularly useful when working across language boundaries — such as a JavaScript frontend sending data to a Python backend, where naming conventions differ by language standard.

Abbreviations and initialisms at word boundaries

Converting text containing initialisms to camelCase or PascalCase requires a decision about how to handle multi-letter abbreviations. "Get HTML content" can become either getHTMLContent (all letters of the abbreviation capitalised) or getHtmlContent (only first letter capitalised). Both are used in practice. Google's Java style guide recommends treating abbreviations as words: getHtmlContent. Microsoft's C# naming guide recommends capitalising two-letter abbreviations fully (IOStream) but treating longer ones as words (HtmlContent). Check your team's style guide or codebase conventions for consistency.

How to Use This Case Converter — Step by Step

1. Paste or type your text in the input box at the top of the page.
2. Click any case button — UPPERCASE, lowercase, Title Case, Sentence case, camelCase, PascalCase, snake_case, kebab-case, alternating case, or inverse case. The converted text appears instantly in the output box.
3. Switch between formats freely — each click converts the original input text, so you can compare multiple formats without re-pasting.
4. Copy the result by clicking the Copy button, or download it as a .txt file for larger text blocks.
5. Swap input and output using the Swap button — useful when you want to apply a second case conversion to already-converted text.
6. Check the stats bar below the output for character count, word count, sentence count, and line count of your text.

Related Tools

• Character Counter — Count characters, words, sentences, and reading time
• Word Counter — Detailed word count and text analysis
• URL Encoder / Decoder — Encode and decode URL-safe strings
• JSON Formatter — Format and validate JSON data
• Random Text Generator — Generate Lorem Ipsum and placeholder text
• Meta Tag Generator — Generate SEO title tags and meta descriptions
• What Is an XML Sitemap and How It Helps Google Index Faster
• Best Free Online Tools for Daily Use in 2026

Frequently Asked Questions