Overview
Text wears different uniforms in different places. Code wants camelCase and snake_case, headlines want Title Case, legal documents shout in UPPERCASE, and URLs insist on kebab-case. Retyping the same words into each uniform is slow, and it introduces typos exactly where they are hardest to spot — inside identifiers, headings and links. A mechanical transformation eliminates both the tedium and the error risk in one motion.
This converter applies thirteen transformations in a single click: the everyday cases (upper, lower, sentence, title), the programmer's set (camel, pascal, snake, kebab, constant), the playful ones (alternating, inverse), and two clean-up operations that collapse extra whitespace or strip line breaks entirely. The result appears instantly in a second box with its own word and character counts, ready to copy or download.
Why do programmers care so much about case?
Because in most programming languages, case is part of identity: myVariable and myvariable are two different things. Conventions grew up to make code readable at a glance — camelCase for variables in JavaScript, snake_case in Python and Ruby, PascalCase for classes and components, SCREAMING_SNAKE_CASE for constants, kebab-case for URLs, CSS classes and HTML attributes. Using the wrong one will not always break code, but it will confuse every human who reads it, and automated linters will flag it.
The converter knows the mechanical rules behind each style: where word boundaries fall, which words get capitalised, which separator joins them. Title case follows headline conventions, keeping small words like “and” and “the” lowercase unless they open the title. Sentence case capitalises only sentence starts. The clean-up modes handle the messy reality of pasted text — tabs, double spaces, stray line breaks from PDFs and spreadsheets — repairing the whitespace without touching the words.
Features
- Thirteen formats: UPPER, lower, Sentence, Title, camel, Pascal, snake, kebab, CONSTANT, aLtErNaTiNg, iNVERSE, plus whitespace collapse and line-break removal.
- Instant conversion — the result appears the moment you pick a format.
- Live input/output counts showing words and characters on both sides.
- Copy and download buttons for moving the result wherever it goes next.
- Chainable: convert, then convert the result again without re-pasting.
- Clear button for a fresh start.
- Fully private: your text never leaves the page.
Benefits
- Kill retyping. One click replaces minutes of careful recasing.
- Match every convention. Code, headlines, URLs and documents each get their uniform.
- Clean pasted text. Collapse the whitespace chaos in one pass.
- Zero typos. Mechanical transformation beats manual editing.
Who can use it
Developers renaming variables and formatting identifiers across languages, writers fixing headline capitalisation to house style, data cleaners normalising messy spreadsheet exports, students formatting essay titles and headings, marketers preparing ad copy in the required case for each platform, and SEO specialists tidying URL slugs. Anyone who has ever retyped a list just to change its case — and then found the typo — will use this weekly.
How to use
- Paste or type your text into the input box.
- Click any of the thirteen format buttons.
- Read the converted result in the output box.
- Copy it, or download it as a text file.
- Chain another conversion on the result if needed, or Clear to restart.
Frequently asked questions
What is the difference between camelCase and PascalCase?
Only the first letter: camelCase starts lowercase (myVariableName) while PascalCase starts uppercase (MyVariableName). JavaScript convention uses camelCase for variables and functions and PascalCase for classes and React-style components. The converter handles the boundary detection — spaces, underscores and hyphens all become word breaks — so switching between the two is one click either way.
When should I use snake_case vs kebab-case?
snake_case (my_variable) is the convention in Python, Ruby and database columns; kebab-case (my-variable) belongs to URLs, CSS classes and HTML attributes, where underscores can be ambiguous or awkward. CONSTANT_CASE is snake_case shouted — reserved by convention for values that never change. Pick the one your ecosystem expects and the converter applies it mechanically, separators and all.
Does Title Case handle small words correctly?
Yes — articles, short prepositions and conjunctions (a, an, the, and, of, in, on, for) stay lowercase unless they open the title, following standard headline style. It is a mechanical rule rather than a style-guide debate, so for publication work, check the result against your specific guide — Chicago, AP and MLA differ on edge cases like hyphenated compounds.
What do the two clean-up modes do?
Collapse whitespace turns every run of spaces, tabs and line breaks into a single space — perfect for text pasted from PDFs, web pages or spreadsheets where formatting exploded. Remove line breaks joins everything into one flowing paragraph. Both repair the invisible structure of pasted text rather than changing its case, and both are one click.
Is my text uploaded anywhere?
No. The transformation is pure string manipulation running in JavaScript in your browser. Nothing is sent to any server, nothing is stored, and nothing is remembered when you leave. Confidential documents and proprietary code are safe to convert here.
Conclusion
Case is a uniform, and uniforms should be issued, not sewn by hand. Paste once, click once, and wear the right one everywhere — in code, in headlines, and in every document in between.