List Diff Checker
Compare two text lists to find shared and unmatched entries, duplicates, and differences with case and whitespace normalization.
Share
The inputted text is too long to include in a share link.
Case Converter
Convert text between uppercase, lowercase, title case, sentence case, camelCase, PascalCase, snake_case, kebab-case, and more.
Text to convert
Converted text
Choose a case
How to use this case converter
Use this tool when the words are right but the capitalization, separators, or identifier style need to change.
- Paste or type text into the input box.
- Choose the output format you need.
- Review the converted text, especially if the input includes acronyms or proper names.
- Copy the converted text from the result box.
Case Converter features
- Convert text to uppercase or lowercase.
- Convert prose to sentence case, title case, or capitalized case.
- Convert labels and phrases to camelCase or PascalCase.
- Convert identifiers to snake_case, kebab-case, or CONSTANT_CASE.
- Copy the converted text with one click.
- Run all conversions locally in your browser.
What case conversion is useful for
Use this case converter when moving text between documents, spreadsheets, code, URLs, filenames, headings, labels, and content tools. It is especially useful when the same words need different capitalization or separator styles in different places.
A common workflow is taking a human-readable label and turning it into a technical identifier. For example, a product name might become a URL slug, a spreadsheet header might become a JSON key, or a heading might become a filename. The opposite can also happen: text copied from code or exports may need to become readable prose again.
Case conversion is mechanical, so it is best used as a fast first pass. Review names, acronyms, brand terms, and title capitalization rules when the output will be published or shown to customers.
Writing and publishing
- Clean up headings, titles, and copied text
- Normalize pasted spreadsheet values
- Prepare social posts, labels, and metadata
Technical formatting
- Create variable names and object keys
- Format URL slugs, filenames, and IDs
- Convert labels into code-friendly identifiers
How case conversion works
Prose-style conversions preserve the original spacing and punctuation while changing capitalization. Identifier-style conversions split text into word tokens, including common camelCase and PascalCase boundaries, then join those words with the separator or capitalization pattern for the selected format.
Sentence case lowers the text and capitalizes the first letter after sentence boundaries. Title case applies a practical set of small-word rules for common headings. Identifier formats remove punctuation separators, normalize words, and then join them as camelCase, PascalCase, snake_case, kebab-case, or CONSTANT_CASE.
The conversion runs locally in your browser. That matters for drafts, internal labels, copied spreadsheet columns, and code snippets that you want to reshape without sending the text to another service.
Case converter FAQ
Does this case converter upload my text?
No. The conversions run in your browser, so pasted text is not uploaded.
What is the difference between camelCase and PascalCase?
camelCase starts with a lowercase first word, while PascalCase capitalizes the first word too.
Can I use this for filenames or URL parts?
Yes. snake_case and kebab-case are useful for filenames, slugs, IDs, and other text that should avoid spaces.
Will title case follow a specific editorial style guide?
No. It uses practical capitalization rules that work for many headings, but publisher-specific styles such as AP, Chicago, or house style may need a final human review.
Review case conversion as a language and naming decision
Uppercase and lowercase are not simple one-character substitutions for every writing system. A letter can map differently by language or context, and one character can become more than one character. The Unicode Standard defines character properties and casing data, but applications still need a locale and a purpose.
Title case is an editorial style, not just capitalization of every word. Articles, conjunctions, prepositions, hyphenated compounds, names, acronyms, and the first and last words can follow house rules. Use the generated version as a draft and apply the style guide required by the publication.
Sentence case also needs meaning. A converter can identify punctuation patterns, but abbreviations, initials, quotations, code, and brand names complicate sentence boundaries. Review each sentence and restore proper nouns such as people, places, products, and organizations. Do not force a brand into a different spelling solely for visual consistency.
Programming naming styles make assumptions about word boundaries. Camel case, Pascal case, snake case, and kebab case may split punctuation, spaces, digits, or existing capitals differently. Check acronyms such as HTTP and IDs, version numbers, leading digits, and non-Latin letters against the target language, framework, database, or API convention.
Changing identifier case can break software on a case-sensitive system. Filenames, URLs, environment variables, database identifiers, imports, and object keys may not refer to the same resource after conversion. Rename through version control or the platform's supported migration process, and update every reference.
Do not use visual case to infer identity or equality. Usernames and email addresses may have service-specific matching rules, while passwords and tokens are usually exact. Normalize only according to the system's contract. Keep the original input when conversion is for display rather than storage.
The page processes entered text for the displayed conversion, but private content still deserves restraint. Use a small sample for confidential documents and source code. Review copied output for secrets, personal data, smart punctuation, and invisible characters before putting it into a public repository or shared document.
After conversion, compare the output line by line. Restore names and acronyms, verify separators and digits, and test identifiers in the destination. For prose, read it aloud and apply the publication's style. For code, run formatting, linting, tests, and a case-sensitive build where possible.
Review checklist
- Choose locale, editorial style, or programming convention before selecting a conversion rather than treating casing as universal.
- Restore proper names, brands, acronyms, quotations, abbreviations, and language-specific forms after automatic conversion.
- Check word boundaries, separators, leading digits, punctuation, non-Latin text, and existing mixed-case identifiers.
- Use a supported rename or migration for case-sensitive files, URLs, imports, database names, and API fields.
- Run the destination's formatter, linter, tests, links, and case-sensitive build before accepting converted identifiers.
- Compare search, sorting, and equality behavior when converted text becomes a stored key rather than display-only copy.
- Review generated slugs and filenames for collisions that appear only after lowercasing or punctuation removal.
- Keep an explicit mapping for migrations so logs, redirects, imports, and integrations can resolve the old form.
Built and maintained by utilkit. Updated . Found an issue? Send corrections to contact@utilkit.com
Related Utilities
Collections featuring this utility
Content Cleanup
Content cleanup is the last mile before publishing, importing, or sending work. Catch messy text, mismatched lists, broken formatting, and file issues before they reach someone else.