Case converter
Every case at once, including title case done properly. Short words stay lower unless they are first or last — "The Lord of the Rings", not "The Lord Of The Rings" — and deliberate capitals like NASA and iPhone survive untouched.
Ten conversions, all shown together so you can recognise the one you want rather than guess at a dropdown.
- Sentence caseFirst letter of each sentence, and nothing else touched.
- Title CaseProper title case — short words stay lower unless first or last.
- UPPER CASEEverything capitalised.
- lower caseEverything lowered.
- camelCaseFor JavaScript variables and JSON keys.
- PascalCaseFor class and component names.
- snake_caseFor Python, and for most SQL columns.
- kebab-caseFor URLs, CSS classes and file names.
- CONSTANT_CASEFor environment variables.
- aLtErNaTiNgFor expressing derision on the internet.
Nothing is uploaded. Converted in this tab. No request carries it.
The thing every other converter gets wrong
Title case is not "capitalise every word". English style guides — Chicago, AP, Oxford — all keep articles, coordinating conjunctions and short prepositions in lower case, unless they fall first or last.
| Input | Most converters | Proper title case |
|---|---|---|
| the lord of the rings | The Lord Of The Rings | The Lord of the Rings |
| what to look for | What To Look For | What to Look For |
| a day at the races | A Day At The Races | A Day at the Races |
| the end | The End | The End |
Note the last row: "the" is capitalised there because it is the first word. That first-and-last exception is the part that makes this a rule rather than a word list, and the part that gets left out.
Capitalising every word is a real convention — it is called start case, and it is what many CMS headline fields do — but it is not what a publisher or a style guide means by title case.
Capitals that are not mistakes
NASA, PDF, iPhone, macOS, eBay. Those capitals carry meaning, and a converter that lowercases them has damaged the text rather than reformatted it. Anything with a capital after its first letter is left exactly as written, in every mode except the two that explicitly mean "change every letter".
Sentence case has the same problem in reverse, plus one of its own: text that is entirely capitals. SHOUTING looks like an initialism by every rule above, so a naive "leave initialisms alone" implementation hands shouting straight back. When the whole passage is capitals there are no initialisms to protect, so it is lowered and the sentence starts are raised.
Reading an identifier, whatever shape it is in
The programmer cases all convert between each other. The interesting part is splitting a run of capitals:
parseHTMLString is three words, not eleven, so it becomes parse_html_string rather
than parse_h_t_m_l_string. PDFReader becomes pdf-reader.
| Case | Looks like | Used for |
|---|---|---|
| camelCase | theQuickBrownFox | JavaScript variables, JSON keys |
| PascalCase | TheQuickBrownFox | Classes, React components |
| snake_case | the_quick_brown_fox | Python, SQL columns |
| kebab-case | the-quick-brown-fox | URLs, CSS classes, file names |
| CONSTANT_CASE | THE_QUICK_BROWN_FOX | Environment variables |
Which to use matters far less than being consistent inside one codebase. If a project already snake_cases its database columns, the next one is snake_case too, whatever you would have chosen from scratch.
Questions
How do I change text to title case?
Paste it in and every case is shown at once, title case among them. This one keeps short words lower — "The Lord of the Rings", not "The Lord Of The Rings" — which is what style guides actually specify and what most converters get wrong.
What is proper title case?
Capitalise the first and last word, and every word in between except articles ("a", "an", "the"), coordinating conjunctions ("and", "but", "or") and short prepositions ("of", "in", "to", "at"). So: "What to Look For", "A Day at the Races", "The Lord of the Rings". Capitalising everything is a different convention called start case, and it is not what a publisher means by title case.
Why did it leave NASA and iPhone alone?
Because those capitals are deliberate. Anything with a capital letter after its first — NASA, PDF, iPhone, macOS — is left as written, in every mode except UPPER and lower. A converter that helpfully "fixes" NASA into Nasa has damaged the text rather than reformatted it.
Can it convert an identifier from one style to another?
Yes, in any direction. It reads camelCase, PascalCase, snake_case, kebab-case and CONSTANT_CASE as input and gives all of them as output, so parseHTMLString becomes parse_html_string rather than parse_h_t_m_l_string — runs of capitals are treated as one word.
Which case should I use for what?
camelCase for JavaScript variables and JSON keys. PascalCase for classes and React components. snake_case for Python and most SQL columns. kebab-case for URLs, CSS classes and file names. CONSTANT_CASE for environment variables. The important thing is consistency within one codebase rather than which convention you picked.
Is my text uploaded?
No. It is transformed in this tab by a few string operations, and no request carries it — which is worth knowing given how often the thing being reformatted is a column name, an internal API field or an unreleased headline.
What BriskFile will not do to you
-
Your files never leave your device
Every conversion runs in your browser. Open DevTools, watch the Network tab, and you will see no upload — because there is not one.
-
No account, no email, no watermark
Nothing to sign up for and nothing stamped on your images. There is no step between choosing a file and getting it back.
-
No limits at the download button
No daily cap, no file counter, no "upgrade to download". If the tool starts a job, it finishes it.
-
Checkable, not just claimed
Open the Network tab and convert something — nothing goes out. Or load the page, disconnect, and watch it keep working: the tool is already on your machine, and your file never leaves it.