Skip to main content
QuantLab Logo

Text Case Converter

Paste any text and get it in UPPER, lower, Title, Sentence, camelCase, PascalCase, snake_case, kebab-case, and CONSTANT_CASE — all at once. Live as you type, completely free, and entirely in your browser.

In-browser, nothing uploaded
Nine cases at once
Live, one-click copy
Input

UPPER CASE

Every letter capitalized

Output appears here.

lower case

Every letter lowercased

Output appears here.

Title Case

First letter of each word

Output appears here.

Sentence case

First letter of each sentence

Output appears here.

camelCase

JS/Java variables & properties

Output appears here.

PascalCase

Classes & React components

Output appears here.

snake_case

Python & SQL identifiers

Output appears here.

kebab-case

URLs, CSS & file names

Output appears here.

CONSTANT_CASE

Env vars & constants

Output appears here.

What this tool does, and which case to pick

Naming conventions are a quiet but constant source of friction. Paste a phrase, a column name, or a heading and this tool renders it in nine conventions simultaneously, recomputing the instant you type. Copy whichever one fits where it is going — no manual retyping, no slips.

The choice of case is rarely arbitrary; it signals intent. camelCase is the JavaScript, Type­ Script, and Java convention for variables and properties, while PascalCase marks classes, types, and React components. snake_case is home ground for Python identifiers and SQL columns. kebab-case belongs to URL slugs, CSS classes, and file names. And CONSTANT_CASE flags environment variables and compile-time constants. For prose, Title Case suits headings while Sentence case reads more naturally in UI copy.

Under the hood, the converter tokenizes your input intelligently: it splits on punctuation and spaces, on lowercase-to-uppercase boundaries (so camelCase separates correctly), and on acronym edges (so HTMLParser becomes HTML + Parser). That means you can feed it text in any style and convert cleanly to any other. Consistent naming is one of the cheapest ways to keep a codebase readable, and it is the kind of discipline we hold to across the systems we build — explore our custom software work.

Everything runs locally with plain string operations — no requests, nothing stored — so you can safely transform internal field names, snippets, or draft copy without sending anything to a server.

How to use it

Type or paste your text into the input box. Every case variant updates live below, each labeled with where it is typically used. Click the copy button on any card to grab that version. The character and word counts confirm the tool tokenized your input the way you expected. Nothing is stored, so a refresh clears everything.

FAQs

Which case should I use for code?

It depends on the language and the kind of identifier. JavaScript, TypeScript, and Java use camelCase for variables, functions, and object properties, and PascalCase for classes, types, and React components. Python and Ruby favor snake_case for variables and functions, with PascalCase for classes. SQL columns are commonly snake_case. CSS classes, URL slugs, and file names lean on kebab-case. Environment variables and compile-time constants are CONSTANT_CASE. Matching the convention of the surrounding code is what keeps a codebase readable.

How does the converter detect word boundaries?

It tokenizes your text into words using three signals: runs of spaces or punctuation become separators, a lowercase-to-uppercase transition splits camelCase and PascalCase into separate words, and an acronym followed by a capitalized word — like HTMLParser — splits into HTML and Parser. Those words are then recombined into whichever target convention you copy. That means you can paste in any style and convert cleanly to any other, rather than only working from plain spaced text.

What is the difference between Title Case and Sentence case?

Title Case capitalizes the first letter of every word, which suits headings and button labels. Sentence case capitalizes only the first letter of each sentence and leaves the rest lowercase, which reads more naturally in body copy and is increasingly preferred in user interfaces. Note that strict editorial title case also lowercases short conjunctions and prepositions like 'and' or 'of'; this tool applies the simpler every-word rule, which is the right default for code-adjacent and UI text.

Is my text sent to a server?

No. All transformations run in your browser with plain JavaScript string operations — nothing is uploaded, logged, or stored, and there are zero network requests, which you can verify in your browser's network tab. That makes it safe to convert internal field names, code snippets, or draft copy you would not want to paste into a remote service. A page refresh clears everything.

Does it handle numbers and accented characters?

Numbers are preserved and treated as part of the adjacent word, so 'version2Beta' tokenizes sensibly. The word-splitting logic is tuned for ASCII letters and digits, which covers the overwhelming majority of identifiers and slugs. Accented or non-Latin characters are passed through by the upper and lower transforms but may not trigger a word boundary, so for heavily accented prose the spaced cases (UPPER, lower, Title, Sentence) are the most reliable.

Inconsistent naming slowing your team down?

A clean, consistent codebase is faster to read, safer to change, and easier to onboard into. We build software with disciplined conventions, typed interfaces, and tooling that enforces them. Talk to us about a new build or untangling a legacy project.

Or reach us directly: beltz@quantlabusa.dev