Case / Naming Convert

camelCase/snake_case/kebab-case.

Runs locally in your browser by default; no upload.

ToolHub ProRemove ads and unlock one-click file export on text-output tools below (image tool keeps its own download).

Input
camelCase

helloWorldExampleText

snake_case

hello_world_example_text

kebab-case

hello-world-example-text

You may also need

About

Convert identifiers between camelCase, snake_case, and kebab-case. Useful for API field naming, code refactors, and normalizing user inputs. Runs locally in your browser.

Use cases

  • Convert backend snake_case fields into frontend camelCase props.
  • Generate kebab-case slugs for URLs from mixed inputs.
  • Normalize a mixed naming style before refactoring code.

Common pitfalls

  • Acronyms (API, URL, ID) may not match your team’s preferred casing automatically.
  • If your identifier contains meaningful separators (e.g. version numbers), review output manually.

Examples

Input

helloWorld_example-text

Output

camel/snake/kebab forms

FAQ

Does it handle mixed inputs?

Yes. It splits the input into tokens and then generates each naming style.

Are numbers preserved?

Yes. Numbers are kept as part of tokens.

How are separators handled?

Underscores, dashes, and spaces are treated as boundaries between tokens.

Will it change the meaning of my identifier?

It only changes formatting. Still, review results for acronyms and domain-specific naming conventions.

Limitations

  • Acronyms can be ambiguous (e.g. APIKey vs ApiKey) and may require manual tweaks.
  • Non-Latin scripts may not split into words as expected.

Recommended

Affiliate slots. Configure real links via environment variables.

No recommendations configured.