Overview
Capitalisation carries meaning far beyond emphasis. Programmers read structure in camelCase humps and snake_case underscores; editors enforce title case on headings and sentence case on body copy; data teams standardise column names before a single query runs. Getting the style wrong is a small error with an outsized power to annoy — and retyping to fix it invites brand-new typos.
This converter treats case as a mechanical transform, not a typing exercise. It first breaks your text into its underlying words — however they were separated — then rebuilds them in whichever convention you choose. Thirteen styles cover prose, programming and cleanup in one panel.
Why do so many case styles exist?
Because different communities needed different signals. Prose styles like sentence case and title case come from publishing tradition, where they tell readers what kind of text they are looking at. Programming styles exist because code cannot contain spaces: camelCase and PascalCase mark word boundaries with capital letters, snake_case and kebab-case with visible separators, and CONSTANT_CASE shouts that a value should never change.
The converter understands all of these as the same operation in different costumes: split into words, rejoin with new rules. That is why it can turn user_first-name into userFirstName and back — it sees the words underneath the punctuation, not just the surface characters.
Features
- Thirteen styles in one place, from basic UPPER and lower through title, sentence, camel, Pascal, snake, kebab and CONSTANT cases.
- True word detection that reads camelCase humps and mixed separators, so conversions work in every direction.
- Non-destructive — input and output live in separate boxes, so the original is never lost to an experiment.
- Chain conversions by feeding the result back in with one click and applying a second style.
- Cleanup transforms that collapse stray spaces and strip unwanted line breaks from pasted text.
- Live character and word counts on both boxes, showing exactly what each transform changed.
- Copy or download the result instantly as clipboard text or a .txt file.
Benefits
- Zero retyping. Converting cannot introduce the typos that retyping always risks.
- One convention everywhere. Normalise a whole file of mixed naming styles in seconds.
- Draft first, style later. Write naturally, then format headings and variables at the end.
- Rescue mangled pastes. PDF and spreadsheet debris cleans up with one click.
Who can use it
Developers renaming variables and columns, writers styling headings, students formatting titles and references, marketers preparing CMS copy, and office workers untangling text copied from PDFs. Anyone who has held shift and retyped a heading by hand will feel the time savings immediately.
How to use
- Paste or type your text into the left-hand box.
- Click the style you want; the result appears on the right.
- Compare styles freely — the original never changes.
- Copy the result, or download it as a text file.
- Chain another conversion with “use result as input” if needed.
Frequently asked questions
Will I lose my original text?
Never. Conversions write only to the output box; the input box keeps exactly what you typed. You can run all thirteen styles against the same original and compare them side by side before deciding.
How does it handle text that is already camelCase?
It splits on the capital-letter boundaries first, recovering the underlying words, then rebuilds them in the target style. That is what makes every-direction conversion possible — the tool understands structure, not just characters.
Title case vs sentence case — which should I use?
Follow your style guide: publishers and academia usually want sentence case for references and title case for headings. This tool's title case capitalises significant words while leaving short connectors small, matching mainstream convention.
What is CONSTANT_CASE actually for?
It is a programming convention signalling that a value is fixed — configuration keys, environment variables, enum members. The shouting capitals are a visual promise: do not reassign this.
Can it fix text pasted from a PDF?
The cleanup transforms handle the usual damage: collapsed whitespace, stray tabs, and line breaks in the middle of sentences. Run those first, then apply your case style to the cleaned text.
Does my text leave my browser?
No. Every conversion is local JavaScript. There is no upload, no queue and no trace once you close the tab.
Conclusion
Case is structure, not decoration — and structure should be applied by rule, not retyped by hand. Pick a style, click once, and let the words underneath do the rearranging.