Key takeaways
- Case conversion changes the current text in place, so keep an original copy before trying several styles.
- Title Case follows a small-word rule but cannot recognise acronyms, brands or proper-name preferences.
- Programmer cases remove separators and can lose information; they are best checked as individual names.
A case converter changes capitalisation or turns a short phrase into a naming style such as camelCase or snake_case. Use it to repair a heading typed with Caps Lock, standardise draft labels or prepare a candidate field name, while reviewing the result for acronyms and meaning that an automatic rule cannot infer.
Before you start
Keep the original text in an editor or another saved location. CrizaTools converts the text in the same box rather than showing a separate permanent source and result. If you want to compare three naming styles, start each one from the original phrase rather than repeatedly transforming an already modified result.
Decide whether the text is prose or an identifier. A visiting-card heading benefits from readable spaces and punctuation; a short configuration key may need joined words. Applying a programmer style to a whole paragraph removes the structure that made it readable, so select the intended phrase instead of pasting a complete document for that task.
Inputs stay in the browser during conversion; CrizaTools does not upload the text. There is no need to include customer records, access tokens or confidential source code merely to standardise a label. Keep your saved original available, especially when the text will be pasted into a system where spelling and case affect how a name is interpreted.
Step by step with CrizaTools
- Open the case converter and paste the source into Your text. Conversion choices are enabled once there is text in the box.
- For ordinary writing, select UPPERCASE, lowercase, Sentence case, Title Case or Capitalize Each Word. The selected transformation immediately replaces the current text; there is no separate preview approval step.
- For a short identifier, select camelCase, PascalCase, snake_case, kebab-case or CONSTANT_CASE. These choices split the phrase into word-like pieces, remove separators and join the pieces using the selected convention.
- Use aLtErNaTiNg or iNVERSE cASE only when you specifically need those effects. Alternating case follows character positions, including spaces, rather than restarting a pattern at each word.
- Inspect the changed text and the character count. Restore acronyms and preferred spellings manually in the text box, and compare punctuation or word boundaries with the original where they matter.
- Select Copy result and paste it into the intended destination. Clear empties the text and resets the highlighted choice; it does not recover the source, so save what you need first.
Two worked examples
Example 1: repairing a heading with an Indian acronym. Paste exactly a GUIDE to UPI in INDIA. Selecting Title Case produces:
A Guide to Upi in India
The small words to and in stay lowercase, while the first word becomes capitalised. The rule lowercases the input before rebuilding the heading, so it cannot know that UPI should remain an acronym. Edit the result manually to A Guide to UPI in India when that is the intended final heading.
Starting again from the original and selecting Sentence case produces A guide to upi in india. Capitalize Each Word instead produces A Guide To Upi In India. These are different transformations, not competing guesses about your style guide. Choose the closest starting layout, then restore names and acronyms deliberately rather than assuming automatic capitalisation also performs editorial review.
Example 2: converting one field name into several styles. Start with examFormStatus 2026. Re-paste that original before each choice. The exact outputs are:
| Choice | Result |
|---|---|
| camelCase | examFormStatus2026 |
| PascalCase | ExamFormStatus2026 |
| snake_case | exam_form_status_2026 |
| kebab-case | exam-form-status-2026 |
| CONSTANT_CASE | EXAM_FORM_STATUS_2026 |
The tool detects the lowercase-to-uppercase transitions before Form and Status and treats the year as another piece. Spaces disappear from all five results. It does not check whether your receiving application permits the resulting name or whether another field already uses it.
Order matters when experimenting. If you first apply lowercase, the source becomes examformstatus 2026, losing the capital transitions that separated Form and Status. Converting that changed text to snake_case produces examformstatus_2026, not the snake_case result in the table. Return to the original when comparing alternatives.
Limits and what to watch for
Title Case uses a fixed list of short English words to keep lowercase after the beginning of the text. It does not implement every publisher’s title style, and it does not recognise company names, Indian place-name preferences or acronyms such as GST and UPI. A final human review remains necessary for public copy.
Sentence case lowercases the text and capitalises the beginning and letters following a full stop, exclamation mark or question mark plus whitespace. It is not a sentence parser and does not apply the same boundary rule to every script’s punctuation. A decimal, abbreviation or unusual punctuation pattern may need manual attention.
Programmer cases split on characters that are not letters or numbers, after a simple Latin lowercase-or-digit to uppercase boundary check. Existing all-capital acronym runs are not intelligently separated into their intended words. These transformations also remove punctuation and line breaks, so do not apply them blindly to addresses, URLs, passwords or full configuration documents.
Multilingual text deserves particular care. The programmer-case splitter does not retain combining marks as part of its word pieces, so it can fragment Indic text; for example, snake_case changes नमस्ते into नमस_त. Use prose case choices for ordinary multilingual labels and inspect the output rather than treating an identifier conversion as language-aware transliteration.
Some transformations can change the character count as well as the case. There is no undo button, file upload or batch-renaming workflow, and this component does not publish a fixed input-size limit. For large documents or many identifiers, preserve the original and work on a manageable selected portion.
Common mistakes
- Trying several styles on successive results: re-paste the original when a previous conversion removed useful boundaries.
- Expecting acronyms to survive Title Case: restore UPI, GST and other intentional capitals manually.
- Converting an entire configuration file: select the intended name, since surrounding keys and values may be case-sensitive.
- Using programmer cases for prose: choose a text case when spaces and punctuation should remain readable.
- Assuming Indic text is transliterated: the tool changes case and separators, not language or script.
- Clearing before saving: copy the final result and retain the original before emptying the box.
Questions and answers
How do I change all-capital text to sentence case?
Paste the text into CrizaTools and select Sentence case. Review names and acronyms afterwards because the rule starts by lowercasing the input and cannot infer their preferred spelling.
What is the difference between Title Case and Capitalize Each Word?
Title Case keeps selected small English words lowercase after the start of the text. Capitalize Each Word capitalises letters at the beginning of whitespace-separated words without applying that small-word list.
Why did UPI become Upi after conversion?
The converter treats the letters using its general capitalisation rule, rather than recognising UPI as an acronym. Edit it back to UPI in the text box and review the rest of the heading for similar changes.
Can I convert camelCase to snake_case?
Yes, the tool detects simple lowercase-or-digit to uppercase transitions and can produce underscore-separated lowercase output. Check acronym runs and unusual scripts carefully, because the splitting rule does not identify every intended word boundary.
Does case conversion keep line breaks?
The ordinary prose case options retain the text’s line-break structure while changing capitalisation. Programmer cases join the detected pieces and remove the original separators, so use them for short names rather than paragraphs.
Choose the appropriate style with the case converter, then verify the final length using the word counter.
Free tools for this
PDF & image
Case Converter
Convert text to UPPERCASE, lowercase, Sentence case, Title Case, camelCase, snake_case, kebab-case and more in one click, then copy.
PDF & image
Word Counter
Count words, characters with and without spaces, sentences and paragraphs as you type, with reading and speaking time.
PDF & image
JSON Formatter
Format, validate and minify JSON in your browser. Shows the line and column of any error, sorts keys and copies or downloads the result.