</>tooledge.dev

Case Converter

Convert text to camelCase, snake_case, kebab-case and 9 more conventions. All 12 results update as you type. Works in your browser — no server roundtrip.

Input
1 line·11 chars

All 12 case styles

  • camelCase
    getUserName
  • PascalCase
    GetUserName
  • snake_case
    get_user_name
  • CONSTANT_CASE
    GET_USER_NAME
  • kebab-case
    get-user-name
  • TRAIN-CASE
    GET-USER-NAME
  • dot.case
    get.user.name
  • path/case
    get/user/name
  • Title Case
    Get User Name
  • Sentence case
    Get user name
  • UPPERCASE
    GET USER NAME
  • lowercase
    get user name
Detected tokens (first line): getUserName

Programming languages and configuration formats disagree on identifier case. JavaScript and JSON use `camelCase`. Python uses `snake_case`. URLs and CSS use `kebab-case`. Environment variables use `SCREAMING_SNAKE_CASE`. Constants in C use `UPPER_CASE`. The ToolEdge Case Converter takes any string and converts it to all 12 common conventions at once, so you can copy whichever you need without writing yet another regex.

The conversion is smart about boundaries: it correctly splits `getHTTPResponse` into `get`, `HTTP`, `Response` (recognising the acronym), and it handles inputs that are already in any of the supported cases. The tool runs entirely in your browser — paste a single identifier or a whole list, copy any output with one click.

Common use cases

  • Renaming a JSON API field to match Python's `snake_case` conventions when wiring up a backend integration.
  • Generating URL slugs from titles (kebab-case is the SEO-friendly URL standard).
  • Converting React component names (PascalCase) to file names (kebab-case) and CSS classes (kebab-case).
  • Bulk-renaming database columns when migrating from one ORM to another with different case conventions.
  • Converting `.env` variable names (SCREAMING_SNAKE) to YAML keys (kebab or camel) when refactoring config.

Frequently asked questions

The tokenizer recognises four boundary types: (1) explicit separators (_, -, ., space); (2) lowercase→uppercase transitions (fooBar → foo, Bar); (3) consecutive uppercase followed by lowercase (HTTPServer → HTTP, Server); (4) letter↔digit transitions (v2User → v2, User). This handles most real-world identifiers correctly without configuration.