Case converter
Change text between sentence case, title case, camelCase, snake_case and the rest, including the ones programmers need and most converters get wrong.
- Title case that knows which small words stay lowercase
- camelCase, PascalCase, snake_case, kebab-case and CONSTANT_CASE for code
- Converts between any two, not just from plain text
- Nothing is uploaded, paste a config file or a customer list safely
0 characters · 0 words · 0 lines
Title case is the one everybody gets wrong
Title case is not "capitalise every word". Articles, short prepositions and conjunctions stay lowercase unless they start or end the title: The Old Man and the Sea, not The Old Man And The Sea. That rule is why a naive converter produces titles that look subtly amateur.
The list of small words here is the usual one: a, an, and, as, at, but, by, for, in, nor, of, on, or, per, so, the, to, up, via, yet. And the first and last word are always capitalised regardless. Style guides disagree at the margins about words of four letters and prepositions like "over", and no converter can settle that for you.
The programming cases, and when each is right
camelCase for variables and functions in JavaScript, Java and Swift. PascalCase for types, classes and components almost everywhere. snake_case for Python, Ruby and SQL columns. kebab-case for URLs, CSS classes and file names, because a hyphen survives a URL and an underscore is hidden by the underline in a link. CONSTANT_CASE for environment variables and things that never change.
The awkward part is converting between them, not into them from prose: going
from parseHTTPResponse to snake_case has to decide whether HTTP is one word
or four, and the answer that produces readable code is parse_http_response.
Sentence case, and the proper nouns it cannot know
Sentence case lowercases everything and capitalises the first letter of each sentence. It cannot know that "london" and "tuesday" should stay capitalised, because that needs a dictionary of names rather than a rule. Use it on headings you have written in ALL CAPS and then read the result. It will be right except for the names.
Why this is worth a tool at all
Because doing it by hand on more than a line of text is both slow and error-prone, and because the alternative, pasting a column of customer names or a config file into a website, means handing that text to somebody else's server. Nothing here leaves the tab, which is the difference that matters when the text is not yours to share.
Questions
Is my text uploaded?
No. It is converted in this tab and nothing is sent anywhere.
Why did title case leave some words lowercase?
Because that is what title case is. Articles and short prepositions stay lowercase unless they are the first or last word.
Which case should I use for a URL?
kebab-case. Hyphens survive URLs cleanly, and underscores disappear under the underline of a link.
Can it convert from camelCase back to a sentence?
Yes. It splits on the case boundaries first, so you can go from any case to any other, not just from plain text.
What happens to acronyms?
Runs of capitals are treated as one word, so parseHTTPResponse becomes parse_http_response rather than parse_h_t_t_p_response.
Does sentence case fix names?
No. It cannot know "london" is a place. Read the result and put the proper nouns back.
Is there a length limit?
No. Nothing is uploaded, so there is nothing to cap.