A case converter cheat sheet is a one-page reference listing every capitalisation and naming style — UPPERCASE, lowercase, Title Case, Sentence case, camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE and aLtErNaTiNg — with the rule, a sample shape and the typical context for each, so the right format is obvious without retyping or guessing. The cheat sheet works because these styles fall into two clean groups: writing styles, where capital letters are cosmetic (Title Case for headlines and article titles, Sentence case for body copy and UI labels, UPPERCASE for emphasis and lowercase for de-emphasis), and naming styles, where capital letters are syntactic (camelCase, snake_case, kebab-case, PascalCase, CONSTANT_CASE) and a single wrong letter breaks the program. The Case Converter produces all ten variants from a single paste, so the cheat sheet becomes a copy-paste lookup: paste your text, scan the row matching the style you need, click Copy. Everything runs locally in your browser, nothing is uploaded, and the same output is produced every time because the rules are deterministic.
The Cheat Sheet: Ten Case Styles at a Glance
A useful case converter cheat sheet gets its value from putting every variant on the same row labels so the pattern jumps out immediately. The table below groups all ten outputs the Case Converter produces, the exact rule behind each, the canonical sample shape, and the typical context where each style is the right choice. Treat the sample shapes as visual fingerprints: if your output matches the shape on the row you picked, the conversion is correct.
| Style | Output shape | Rule | Where it's used |
|---|---|---|---|
| UPPERCASE | HELLO WORLD | Every letter A–Z becomes upper. | Emphasis, legal disclaimers, shouty headlines. |
| lowercase | hello world | Every letter A–Z becomes lower. | De-emphasis, constant display, casual copy. |
| Title Case | Hello World | First letter of every word is capitalised. | Article titles, page headings, slide titles. |
| Sentence case | Hello world. The rest is lower. | Only the first letter of each sentence is capitalised; the rest is lower. | Body copy, UI labels, support documentation. |
| camelCase | helloWorld | First word lower, each later word Title-cased, no separators. | JavaScript and Java variables, methods, properties. |
| PascalCase | HelloWorld | Every word Title-cased, no separators. | Class names, React components, TypeScript types. |
| snake_case | hello_world | All lowercase, words joined by underscores. | Python variables, SQL column and table names. |
| kebab-case | hello-world | All lowercase, words joined by hyphens. | URL slugs, CSS classes and IDs, file names on disk. |
| CONSTANT_CASE | HELLO_WORLD | All uppercase, words joined by underscores. | Environment variables, compile-time constants, enums. |
| aLtErNaTiNg | hElLo WoRlD | Letters alternate caps/lower position by position, non-letters skipped. | Decorative copy, social posts, signature flourishes. |
Reading across the table makes the two groups obvious. The first four rows (UPPERCASE, lowercase, Title Case, Sentence case) keep the spaces between words and only change which letters are capital — they are written for humans. The next five rows (camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE) drop or replace the spaces and use capitalisation as part of the syntax — they are written for compilers and tools. The last row, aLtErNaTiNg, is purely cosmetic and flips letter case position by position so the visual zig-zag lands only on letters.
Writing Styles vs Naming Styles: What the Cheat Sheet Splits Apart
The split in the cheat sheet mirrors a real-world split: capitalisation in prose is decorative, while capitalisation in source code is syntactic. That difference is the reason a case converter cheat sheet belongs on the wall of every developer-writer who works in both modes.
In writing styles, capital letters shape how the eye reads a sentence. UPPERCASE shouts. Title Case dresses the headline for a serious publication. Sentence case matches how the rest of the body text actually reads. A missing capital in body copy is a style mistake; an extra capital is rarely a problem. Editors care about consistency here because readers notice it.
In naming styles, capitalisation shapes whether the code compiles or the URL loads. The JavaScript engine treats firstName and FirstName as two different identifiers. Python treats user_id and User_Id differently even though they look almost identical. A SQL parser rejects CONSTANT_CASE in a column name if the table expected snake_case. One slipped letter is one broken deployment. The cheat sheet makes those choices auditable: every row is a different rule with a different sample shape, so the mismatch is visible immediately.
How to Convert Any Text Using the Cheat Sheet
Follow these steps to turn any block of text into every row of the cheat sheet:
- Open the Case Converter and click or tap the input box at the top of the page.
- Type or paste your text — a sentence, a heading, a variable name, or a whole list — into the field.
- Watch the ten variants appear below the input as you type, with each row matching a row on the cheat sheet above.
- Locate the row whose style you need, then click the Copy button on the right side of that row.
- Paste the copied version into your editor, code file, spreadsheet cell, URL field or word processor.
- Repeat the copy for additional styles — switching between rows is one click each, with no reload and no waiting.
Everything is computed locally in your browser, so the same input always produces the same ten outputs and the converter works offline once the page is loaded. Large pastes and long lists process without a round trip to a server, and no signup or account is required.
Reading the Cheat Sheet: One Input, Ten Variants
The fastest way to learn the cheat sheet is to pick a single input and read all ten rows. Take the four-word phrase hello world example test:
- UPPERCASE → HELLO WORLD EXAMPLE TEST
- lowercase → hello world example test
- Title Case → Hello World Example Test
- Sentence case → Hello world example test
- camelCase → helloWorldExampleTest
- PascalCase → HelloWorldExampleTest
- snake_case → hello_world_example_test
- kebab-case → hello-world-example-test
- CONSTANT_CASE → HELLO_WORLD_EXAMPLE_TEST
- aLtErNaTiNg → hElLo WoRlD eXaMpLe TeSt
The first four rows keep the four original spaces; the next five glue or replace the spaces with underscores, hyphens, or no separator while changing which letters are capital; the final row flips case on every letter and ignores the spaces. For exact output on your own text, paste the source into the Case Converter and compare the row you need against the others — the order of rows is fixed, so the row index is identical for every paste.
Mixed-style inputs follow the same pattern once the converter has re-tokenised them. The phrase fooBar_baz-qux arrives as four words (foo, Bar, baz, qux) and produces fooBarBazQux in camelCase, foo_bar_baz_qux in snake_case, and FooBarBazQux in PascalCase, regardless of how the input was originally capitalised. With this single input the cheat sheet predicts the eight style-dependent rows; the two remaining rows (UPPERCASE, lowercase) are style-agnostic and identical for any text that lacks alphabetic variation.
Tokenization Rules Behind Every Row in the Cheat Sheet
The reliability of the cheat sheet comes from one decision: every conversion re-tokenises the input first, then re-joins the words in the target style. The tokeniser does not just swap spaces for underscores.
It splits on whitespace, underscores, hyphens, and common punctuation, and it recognises camelCase and PascalCase boundaries as well. So fooBar_baz-qux, foo bar-baz_qux, and FOO_BAR-BAZQUX all collapse to the same four words. That is why the same paste produces consistent camelCase, snake_case, and kebab-case outputs — the cheat sheet's rows are derived from a single canonical list of words.
Digits stay attached to their word, so order66 is treated as one token rather than being split on the boundary between letters and numerals. Mixed-case tokens still surface their boundaries: the identifier HTMLParser becomes two words (HTML and Parser) at the acronym boundary, so it converts cleanly to htmlParser in camelCase or html_parser in snake_case. A shouting SNAKE_CASE constant pasted in becomes clean camelCase rather than a broken hybrid because every naming row normalises words to a single canonical form before re-joining.
The alternating style is the exception to the tokeniser rule. It does not split into words at all; instead it flips letter case position by position and skips any non-letter (space, hyphen, underscore, punctuation, digit). The visual zig-zag lands only on letters, so the rhythm of the original spacing is preserved while every letter toggles.
Because the rules are explicit and deterministic, the same input always produces the same output on every row. That determinism matters most when the cheat sheet is used for scripting: reformatting a column of API field names between camelCase and snake_case, turning a title into a URL slug, or normalising a list of environment variable names to CONSTANT_CASE all need byte-stable results.
Choosing the Right Row: Quick Decision Guide
Use the questions below to pick the right row from the cheat sheet on the first try:
- Is the destination a published headline, article title, slide title, or book chapter? Use Title Case.
- Is the destination a sentence of body copy, a UI label, or support documentation? Use Sentence case.
- Did the text arrive accidentally in CAPS or stuck on a caps-lock key? Run it through UPPERCASE or lowercase first.
- Is the destination a JavaScript or Java variable, method, or property? Use camelCase.
- Is the destination a React component, a class name, or a TypeScript type? Use PascalCase.
- Is the destination a Python source file, a SQL table column, or a database identifier? Use snake_case.
- Is the destination a URL path, a CSS class, or a file name on disk? Use kebab-case.
- Is the destination an environment variable, a compile-time constant, or an enum value? Use CONSTANT_CASE.
- Do you just want a stylised version for a social bio or comment? Try aLtErNaTiNg.
The answers map one-to-one to the ten rows in the cheat sheet above, and the Case Converter exposes every row on a single paste so the mapping is always visible. For multi-language projects, keep a copy of this cheat sheet open in a side tab; the cost of a wrong letter in code is high enough to make a brief lookup worth the click.