Overview
Rewrites text between ten casing conventions in one pass: UPPERCASE, lowercase, Title Case, Sentence case, camelCase, PascalCase, snake_case, CONSTANT_CASE, kebab-case and a url-slug mode. It is the quick fix when text arrives in the wrong shape for where it is going.
How It Works
Paste text, pick a mode, and the result updates immediately. UPPERCASE and lowercase are direct. Title Case follows AP-style rules (small words such as a, of and the stay lowercase mid-title) and Sentence case capitalises the start of each sentence; acronyms such as NASA and brands such as iPhone keep their casing in both. camelCase joins words with each subsequent word capitalised and no separators. kebab-case lowercases and joins with hyphens, the form used by URL slugs, CSS class names and most file names. PascalCase, snake_case and CONSTANT_CASE split the same way and join with capitals, underscores and capitalised underscores, and url-slug also strips accents so Café Menü becomes cafe-menu.
Step-by-Step Usage Guide
- Paste the text you need reshaped.
- Choose the target case.
- Copy the result. With a mode still active, further edits to the input re-convert automatically, so successive tweaks stay in sync.
Technical Specifications & Standards
Casing looks trivial until it meets real data. Identifier conventions differ by ecosystem, with camelCase for JavaScript variables, kebab-case for CSS custom properties and URLs, and snake_case for SQL columns and Python. Mismatches between them are a steady source of silent mapping failures when a payload written in one convention is deserialised in another. Converting mechanically in bulk is faster and less error-prone than retyping. For the programmer cases, words are split on any run of characters that is not a letter, digit or combining mark and on camelCase and acronym boundaries (parseHTTPResponse becomes parse, HTTP, Response), with accented and non-ASCII letters kept intact. Each word is then lowercased or capitalised, so an acronym does not survive those modes (HTTP becomes Http in camelCase), whereas Title Case and Sentence case leave acronyms and mixed-case brands alone.
Targeted Use Cases
- Converting a column or field list from one naming convention to the one your code expects.
- Turning a headline into a kebab-case URL slug.
- Normalising shouted text pasted from a spreadsheet into readable sentence case.
- Reformatting a list of labels into consistent Title Case for UI copy.
Notes & Gotchas
- Title Case follows AP-style rules: short articles and prepositions stay lowercase mid-title and acronyms are kept, but other editorial styles differ, so review output headed for published copy.
- Acronyms survive Title Case and Sentence case but not the programmer cases: API becomes api under kebab-case and snake_case, Api under PascalCase and API under CONSTANT_CASE.
- Locale matters for a few letters, Turkish dotless i being the best-known case, so verify results on non-English text.
- camelCase, PascalCase, snake_case, CONSTANT_CASE, kebab-case and url-slug collapse separators, so punctuation inside the input is dropped rather than preserved.
Frequently Asked Questions
Which cases are supported?
UPPERCASE, lowercase, Title Case, Sentence case, camelCase, PascalCase, snake_case, CONSTANT_CASE, kebab-case and url-slug, which also strips accents to plain ASCII.
Can it handle a long document?
Yes. It works on whatever you paste, as a single pass over the string in the browser.
Is my text stored?
No. The conversion happens locally and nothing is transmitted.
Why did my acronym change?
The programmer cases (camelCase, PascalCase, snake_case, CONSTANT_CASE, kebab-case and url-slug) split text into words and recase each one, so ID, API and URL are treated as ordinary words there. Title Case and Sentence case keep acronyms in capitals.