Case Converter
Convert text between upper, lower, title, and sentence case
Case Converter rewrites pasted text into twelve output styles, from plain UPPERCASE to code-friendly `camelCase`, `snake_case`, `dot.case`, and `path/case`. Paste text, choose the target style, then copy or download the converted version. Everything runs locally in your browser.
Content reviewed: August 27, 2026
Encrypted with HTTPSProcessed in your browser
All processing runs locally in your browser. Your files and text are not sent to Tool-web's server.
Actions:
How to Use
- Paste or type your text
- Click the desired case option (UPPER, lower, Title, Sentence)
- The converted text appears instantly
- Copy the result
Features
- UPPERCASE conversion
- lowercase conversion
- Title Case conversion
- Sentence case conversion
- Invert Case toggle
Tips for getting Case Converter right
- Apply sentence case after pasting text that arrived SHOUTING — then fix names manually
- camelCase and snake_case are for identifiers; don't apply them to prose you plan to publish
- Title Case keeps minor words lowercase; check house style guides for exceptions like brand names
- Use `path/case` and `dot.case` only when you actually need slash- or period-separated tokens
What each case style is for
| Style | Example | Typical use |
|---|---|---|
| UPPERCASE | SHIPPING NOTICE | Headlines, warnings, acronyms |
| lowercase | shipping notice | Casual copy, URLs, email addresses |
| Title Case | Shipping Notice for August | Article titles, book titles |
| Sentence case | Shipping notice for August | Body text, most modern UI labels |
| tOGGLE cASE | sHIPPING nOTICE | Quick reversal when copied text has inverted emphasis |
| camelCase | shippingNoticeForAugust | JavaScript/Java variable names |
| PascalCase | ShippingNoticeForAugust | Class and component names |
| snake_case | shipping_notice_for_august | Python variables, database columns |
| kebab-case | shipping-notice-for-august | URL slugs, CSS class names |
| CONSTANT_CASE | SHIPPING_NOTICE_FOR_AUGUST | Constants and env-style keys |
| dot.case | shipping.notice.for.august | Namespaced keys and config identifiers |
| path/case | shipping/notice/for/august | Path-like labels or nested key patterns |
A worked example
Start with: "the quarterly SHIPPING report is ready". Different targets solve different problems, so the useful output depends on where the text is going next.
- UPPERCASE → THE QUARTERLY SHIPPING REPORT IS READY
- Sentence case → The quarterly shipping report is ready
- Title Case → The Quarterly Shipping Report Is Ready
- kebab-case → the-quarterly-shipping-report-is-ready
- camelCase → theQuarterlyShippingReportIsReady
- CONSTANT_CASE → THE_QUARTERLY_SHIPPING_REPORT_IS_READY
What the developer-style buttons actually do
The code-oriented modes strip punctuation more aggressively than the prose-oriented ones because they are built for identifiers and path-like strings. That is helpful for variable names and slugs, but it means they are not faithful text-preservation tools.
- `camelCase` and `PascalCase` remove separators and capitalize word boundaries
- `snake_case`, `kebab-case`, `dot.case`, and `path/case` keep separators but standardize them
- `CONSTANT_CASE` uppercases the whole token stream after replacing spaces with underscores
Real-World Use Cases
- Normalizing shouty customer notes into sentence case before replying
- Turning feature names into `camelCase`, `PascalCase`, or `CONSTANT_CASE` identifiers
- Generating URL slugs or CSS-friendly `kebab-case` labels from draft headings
- Cleaning mixed-case text copied from PDFs before it goes back into a document
- Preparing filenames, keys, and labels that need consistent casing across a project
Best Practices
- Choose the target casing based on where the text will be used: prose, code, URL, or file path
- Keep a copy of the original when converting long passages with names, acronyms, or product terms
- Use sentence case for paragraphs and UI labels unless a style guide says otherwise
- Use `kebab-case`, `snake_case`, and `camelCase` only after deciding how punctuation should be handled
- Copy the converted result into its final destination and do a quick visual scan before publishing
Common Mistakes to Avoid
- Using Title Case for body copy when sentence case is the intended editorial style
- Assuming the converter fixes spelling, punctuation, or grammar errors in the source text
- Applying identifier styles like `snake_case` to prose that should keep spaces
- Forgetting to review acronyms and brand names after automatic case changes
- Expecting punctuation-heavy strings to survive every developer-style conversion unchanged
Troubleshooting
- If acronyms like NASA become lowercase, correct those terms manually after conversion
- If developer-style output drops punctuation, remove the punctuation in the source or re-add separators after conversion
- If the result looks unchanged, confirm you clicked a conversion button after pasting the text
- If line structure matters, review multi-line input after conversion because some styles collapse spacing
- If you need counts as well as conversion, run the result through Character Counter afterward
Frequently Asked Questions
What case options are available?
The tool supports UPPERCASE, lowercase, Title Case, Sentence case, and inverted case.
Does it preserve punctuation?
Yes. Only the letter casing is changed. Punctuation, spaces, and other characters remain intact.
Can I convert a large block of text?
Yes. The tool handles text of any length.
Privacy & Security
Conversion happens entirely in your browser. Your text is never sent to any server.
Tips & Best Practices
- Apply sentence case after pasting text that arrived SHOUTING — then fix names manually
- camelCase and snake_case are for identifiers; don't apply them to prose you plan to publish
- Title Case keeps minor words lowercase; check house style guides for exceptions like brand names
- Use `path/case` and `dot.case` only when you actually need slash- or period-separated tokens
Comments
0/1000
Explore more Text Tools
Browse all tools in the Text Tools collection.