DevSnap Open the toolbox
  1. Home
  2. Tools
  3. Case Converter

Convert an identifier into every case style at once

Naming is a small, constant annoyance: a value arrives in snake_case and the framework wants camelCase, or the opposite. This converts between all the common styles and shows every variant side by side so you can pick the right one.

Styles
10
Input
Any text
Bulk
One per line
Case Converter Every style at once, one value or a whole list
Variants

Measured on Apple M4 Max: 18 ms convert to camelcase (1.0 MB of text) See the benchmarks

How to use it

  1. Paste the identifier One value, or a list with one per line. A whole list of column names converts at once.
  2. Read the variants Every style is shown at the same time, so you can see which one your codebase uses before you commit to it.
  3. Copy the one you want Each variant has its own copy button.

Reference

One input, every style

StyleResult
`camelCase``userAccountId`
`PascalCase``UserAccountId`
`snake_case``user_account_id`
`kebab-case``user-account-id`
`CONSTANT_CASE``USER_ACCOUNT_ID`
`dot.case``user.account.id`
`Title Case``User Account Id`

Questions people ask

How does it split words in an acronym?

A run of capitals is treated as one word, so `HTTPServer` becomes `http_server` and `parseURL` becomes `parse_url`. This is the convention used by most style guides, and the alternative is rarely what people want.

Can it convert a whole list?

Yes. Put one value per line and each line is converted independently.

What is the difference between snake_case and CONSTANT_CASE?

Only the casing. `CONSTANT_CASE` is the convention for constants and environment variables, so it is the same words in upper case with underscores.

Does it handle spaces?

Yes, spaces are treated as word boundaries, so `user account id` converts cleanly.

Will it break my identifiers?

It only changes casing and separators. Digits and the letters themselves are untouched, so a value like `user2FA` keeps its digits.

Is there a style I am missing?

The ten shown cover the conventions in common use. A style that does not appear can be built from any of them, and the words are the same either way.

Where this earns its keep

Migrating a database column

A column called `created_at` becomes `createdAt` in an ORM, or `CreatedAt` in a class, and picking the wrong one is a silent mismatch between your model and your schema.

Writing an API payload

Different APIs use different conventions, and the one you need depends on the service you are calling.

Cleaning up a batch of names

A list of field names from a spreadsheet converts to the style your codebase uses in one pass.

Details that catch people out

The words are detected, not the characters

The splitter looks for boundaries between lowercase and uppercase, between letters and digits, and between letters and underscores. That means `userID` becomes `user_id` and `HTTPServer` becomes `http_server`, which is usually what you want.

Acronyms are the hard case

`parseURL` could split as `parse_url` or `parse_u_r_l`, and there is no way to know which without a dictionary. The tool assumes a run of capitals is one word, which is the common convention.

This is the most-repeated five seconds in a codebase

Every developer converts identifiers dozens of times a day, usually with a regular expression they half-remember. Getting the edge cases right once, in a tool that is open in a tab, is worth more than it sounds.

  • All ten styles at once, so you do not have to know the name of the one you want.
  • A list converts in bulk, one value per line.
  • Runs locally — an identifier is rarely a secret, but the list might be a schema.
  • Each variant copies with one click.

Last reviewed 2026-10-16. Every tool on DevSnap runs entirely in your browser, so whatever you paste here never reaches a server.