Best 3 Case Converter Tools Compared

The database uses created_at, the API returns createdAt, the CSS class is created-at and the environment variable is CREATED_AT. Same field, four spellings, and a mapping layer somewhere translating between them.

Converting one name is trivial. Converting forty of them, pasted out of a schema, without introducing a typo into one — that is the job. The tools all do the same core conversion, so the differences that matter are how many formats they know, whether they handle a whole list at once, and whether your identifiers get sent anywhere.

How to judge a case converter

Which formats? camelCase, PascalCase, snake_case, kebab-case and SCREAMING_SNAKE cover most work. dot.case and path/case turn up in config files and routes.

Can it do a list? One string at a time is fine once. A column of forty from a schema dump is the actual use case.

Does it handle acronyms sensibly? parseHTTPResponse to snake_case is where converters differ — parse_h_t_t_p_response is a real and common failure.

Does the text stay local? Table and column names describe your data model. Not sensitive exactly, but no reason for them to leave.

The comparison

Facts checked August 2026; tools change their plans. Table covers only the 3 alternatives — our tool gets its own section below.

Toolk.site Case Converter

The most complete and the clearest about privacy. It offers 13 or more conversions — camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, Title Case, Sentence case, dot.case, path/case, UPPERCASE, lowercase, plus alternating and inverse case as novelties — and states it runs 100% in your browser with all processing in local JavaScript and your text never leaving the device.

path/case is the useful outlier: it turns up in routing and file paths and most converters skip it. No signup, no account. The two novelty cases are filler, but they cost nothing.

Coddy Case Converter

The broadest on the unusual formats. Alongside camelCase, PascalCase, snake_case, SCREAMING_SNAKE_CASE, kebab-case, Title Case and Sentence case, it includes Train-Case and flatcase — the latter being what you need when a system rejects separators entirely, which happens more than it should.

It is free and part of a wider set of developer utilities, though those sit inside a learn-to-code platform, so there is a certain amount of course promotion around the tool. The conversion itself asks nothing of you.

Convert Town

The quickest for one-off work. It converts between camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE and dot.case instantly in the browser, and auto-copies the result to your clipboard — which removes a step you would otherwise repeat forty times.

Six formats is fewer than the others, though it is six that cover the overwhelming majority of real use. The basic tool is free with a PRO subscription at $3 a month or $25 a year for an enhanced experience and desktop tools; the converter works without it.

Identifier Case Converter

Ours converts identifiers between camelCase, snake_case, kebab-case, PascalCase and SCREAMING_SNAKE in one pass, framed specifically around variable, column and file identifiers rather than text in general. “In one pass” is the operative part — the workflow is a list in, a list out, rather than converting one name and going back for the next.

What it does not do: dot.case, path/case or flatcase, or the novelty formats. If your target is a config file using dot notation, Toolk.site or Convert Town cover it and we do not. Which convention belongs where is genuinely conventional rather than technical — naming conventions differ by language community, and matching the surrounding code matters more than any argument about which is better.

Which one to pick

• dot.case or path/case — Toolk.site.
• flatcase or Train-Case — Coddy.
• One name, copied straight to the clipboard — Convert Town.
• A column of identifiers converted together — the tool below.

How to do it with Identifier Case Converter

1. Open the Identifier Case Converter and paste your identifiers, one per line.
2. Pick the target convention — match what surrounds the code, not your preference.
3. Check anything containing an acronym; that is where converters most often produce something odd.
4. Copy the converted list back in one go rather than name by name.

The walkthrough is in how to convert identifiers between naming styles. Other developer tools are in the tools directory.

You might also need

If the identifiers came from a database schema, the JSON to SQL Schema Generator covers the shape around them.

For turning a heading into a URL slug rather than an identifier, the Slug Generator applies the rules URLs actually need.

Frequently asked questions

Is there a free case converter that doesn’t send my text anywhere?

Yes. Toolk.site states 100% in-browser processing with text never leaving your device, Convert Town converts instantly in the browser, and ours runs locally. Worth preferring when the input is your database schema.

How should acronyms be handled in camelCase?

Convention varies. Many style guides now treat acronyms as ordinary words — parseHttpResponse rather than parseHTTPResponse — precisely because the second form converts badly to snake_case. Whichever you choose, check the converter’s output rather than assuming.

Which convention should I use?

The one already in use around your code. Python and SQL lean snake_case, JavaScript and Java lean camelCase, CSS and URLs lean kebab-case, constants use SCREAMING_SNAKE. Consistency with the surrounding code beats any abstract preference.

Final thought

Convert the whole list in one pass and eyeball the acronyms. Case conversion is not where bugs come from — the manual retyping of forty names, one of them slightly wrong, is.

Try the free Identifier Case Converter