Paste text and switch it to any case in one click — UPPER, lower, Title, Sentence, camelCase, snake_case, kebab-case. Converted in your browser; client lists never leave your device.
Converted entirely in your browser — nothing is uploaded.
What this free tool is great for: a quick, one-off job with no signup — it runs entirely in your browser, so nothing leaves your device and there's nothing to manage.
Its honest limit: it produces a one-off output — it won't store, track, brand or manage them at scale, and it can't tell you what happens after you share it.
Every writer, marketer and developer hits the same tiny wall several times a week: a headline arrives IN FULL CAPS from a client, a CSV export needs lowercase emails, a list of product names needs Title Case for the site, a spec wants variable names in camelCase. Retyping is error-prone drudgery, and doing it by hand across fifty lines is how typos enter systems. A case converter removes the drudgery in one click — and because this one runs entirely in your browser, the customer lists and draft copy you paste never leave your machine. The sections below go past the buttons: which case belongs where, and the edge cases that trip people up.
UPPERCASE shouts — reserve it for short labels, legal headers and the rare genuine emphasis; sustained caps text reads as aggression and is measurably harder to scan, because words lose their distinctive shapes. lowercase is the neutral workhorse and the safe normalisation target for data: emails, usernames and tags should almost always be lowercased before storage, since "Anna@Example.com" and "anna@example.com" are the same human but different database rows. Sentence case — capital at the start of each sentence, everything else down — is standard for body copy and, increasingly, for headlines and UI text: it reads friendlier and skips the which-words-do-I-capitalise debate entirely.
Title Case Capitalises the Significant Words and lowercases the small ones (a, an, the, of, in…) — and which words count as "small" differs per style guide, which is why two colleagues can both be "right" and still disagree. AP, Chicago and APA each draw the line slightly differently; this tool follows the common convention of lowering short function words unless they open the title. The deeper decision is whether to use Title Case at all: it signals formality and tradition (news headlines, book titles), while sentence case signals modern and conversational (most tech brands switched years ago). Pick one per channel and stay consistent — mixed casing across a site reads as carelessness faster than either choice reads as wrong.
The programming cases exist because code can't abide spaces. camelCase glues words with internal capitals and dominates JavaScript and Java variable naming. snake_case joins with underscores — Python's house style, and common for database columns and API fields. kebab-case joins with hyphens and lives in URLs, CSS classes and file names (it's the only one of the three that's URL-friendly without escaping, which is exactly why our slug generator produces it). Converting between them mechanically matters more than it looks: a JSON API in snake_case consumed by a JavaScript app in camelCase is a daily translation chore, and a converter beats hand-renaming every time the shape changes.
Case conversion looks trivial until real text arrives. Acronyms: naive Title Case turns "NASA" into "Nasa" and "iPhone" into "Iphone" — scan the output for brand and acronym casualties before shipping it. Non-English letters: ß, accented capitals and Turkish's dotless-i have genuinely special casing rules that surprise even seasoned developers. Names: "van der Berg" and "McDonald" follow family convention, not grammar, and no algorithm knows which. The honest workflow: convert mechanically, then give the result the ten-second human scan that catches what rules can't. The converter does the ninety-five percent; the proofread protects the five that carries your credibility.
Beyond copy, case conversion is quiet data hygiene. Duplicate detection breaks when "Acme BV", "ACME BV" and "acme bv" coexist; email deduplication and tag systems only work on a normalised case; spreadsheet lookups fail silently across case variants. The rule that saves hours downstream: normalise text data to one case at the point of entry (lowercase for identifiers, a display-case rendered later where humans read it). When you inherit a messy list, a lowercase pass followed by dedupe is the two-minute repair that fixes what looks like a data disaster — and this tool handles the lists that are too sensitive to paste into a random website.
The aLtErNaTiNg CaSe button is included with a smile: it's the typographical marker of sarcasm in meme culture ("wElL aCtUaLlY"), useless in business copy and beloved everywhere else. Its serious cousin is worth knowing though — deliberately odd casing gets flagged by spam filters and reads as unprofessional in outreach, which makes the converter's boring buttons the safe ones for anything commercial. Know the dialects, use them where they belong, and keep the sarcasm case for the group chat where it lives its best life.
Zoom out from single conversions and case becomes a brand system decision. Button labels, menu items, email subject lines, error messages — each category deserves one documented casing rule, because users subconsciously register inconsistency as sloppiness long before they can name it. The practical artifact is three lines in your style guide: headlines sentence case, buttons sentence case, product names as trademarked. New writers stop guessing, reviews stop nitpicking, and the converter becomes the enforcement tool for legacy copy that predates the rules. Companies with mature brands sweat this detail not from pedantry but because typography consistency is the cheapest form of polish that customers actually perceive — and the only one a free tool fully automates.
Case is the last coat of polish; the harder question is whether the words underneath earn their place — whether the headline matches what people search, whether the content covers what the ranking pages cover. That's where Frase does more: it researches what actually ranks for your topic, surfaces the questions and terms the best pages answer, and helps you write content that competes — after which the case converter dresses it correctly. Polish here, substance there; readers and rankings need both, but they forgive imperfect casing far sooner than they forgive content that wasn't worth reading.
House style decides: Title Case reads formal/traditional (news, books), Sentence case reads modern/conversational (most tech brands). Pick one per channel and stay consistent — inconsistency reads worse than either choice.
Mechanical Title Case can't know NASA from Nasa or iPhone from Iphone. Convert first, then give the output a ten-second scan for brands, acronyms and names — the human five percent.
All replace spaces for technical contexts: camelCase (internal capitals) rules JavaScript, snake_case (underscores) rules Python and databases, kebab-case (hyphens) rules URLs and CSS — it's the only URL-safe one.
No — conversion is a few lines of JavaScript running in your own browser. Nothing you paste is transmitted or stored.
Blogger, teacher or toolmaker? Put this calculator on your own page — free forever, no strings. Copy the snippet below (the credit link is appreciated and keeps the tool free):
This tool is free and runs entirely in your browser. The link above is an affiliate link: we may earn a commission if you sign up, at no extra cost to you, and it never changes our honest take.