Text Case Converter

Switch between UPPERCASE, lowercase, Title Case, Sentence case, camelCase, PascalCase, snake_case, kebab-case, SCREAMING_SNAKE_CASE and dot.case. Useful for anyone renaming variables to match a style guide, or cleaning up a dataset where the casing is inconsistent across rows.

Case conventions actually mean something

• camelCase — JavaScript variables and functions, Java methods, JSON keys in most JS-adjacent ecosystems
• PascalCase — classes and components: UserService, React components, basically everything in C#
• snake_case — Python (PEP 8 is explicit about this), Ruby, SQL column names
• kebab-case — CSS class names, HTML attributes, URL slugs
• SCREAMING_SNAKE_CASE — constants, across pretty much every C-family language

Why it's not just a style preference

These conventions exist so that, at a glance, you know what kind of thing you're looking at without reading the surrounding code. See PascalCase in a JS file and you already know it's a class or a component before reading further. See SCREAMING_SNAKE_CASE and you know not to reassign it. Break convention and you lose that instant signal — which is a small cost per instance but adds up across a codebase multiple people touch, especially when a linter isn't enforcing it and everyone's just eyeballing consistency.

The annoying part

Mixed-convention codebases usually aren't sloppiness — they're the result of gluing together a Python backend (snake_case) and a JavaScript frontend (camelCase) with a JSON API in between, and someone has to decide where the conversion happens. Some teams convert at the API boundary so each side stays idiomatic; others just pick one convention and force it through both layers. Neither is wrong, but pick one on purpose rather than ending up there by accident.