We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Quickly convert between snake_case and camelCase naming, supports batch processing and common edge cases.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
Paste one name or a multiline list, then choose an output mode: camelCase, PascalCase, snake_case, or CONSTANT_CASE. The converter applies the selected text rule to each nonblank line and returns the lines in the same order. For example, user_profile can become userProfile, UserProfile, or USER_PROFILE, depending on the selected mode.
Case styles are naming conventions: camelCase starts the first word in lowercase and capitalizes later words; PascalCase capitalizes the first letter of each word; snake_case separates words with underscores in lowercase; CONSTANT_CASE uses uppercase words separated by underscores. The tool also supports the reverse direction from camel-style names to underscore output. It handles text, not programming-language syntax.
For camelCase and PascalCase output, underscores and hyphens mark word boundaries, and an uppercase letter after a lowercase or digit starts a new word. For snake_case output, lower-to-upper boundaries and acronym-to-word boundaries are separated, spaces and hyphens become underscores, repeated underscores are collapsed, and the result is lowercased. CONSTANT_CASE uses that underscore result in uppercase.
These practical rules cannot infer every intended acronym or preserve every language-specific identifier rule. Treat the result as a naming suggestion to inspect, especially when the input includes initialisms, punctuation, Unicode, or digits.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Paste one identifier per line. The example shows the expected line-by-line format; blank lines are retained, while whitespace-only lines are left as entered.
Select the direction that matches your source and target styles. The mode names identify the conversion direction and output case.
Review the output line by line, then use the output copy control. Check acronyms, punctuation, and any names where capitalization carries meaning.
Use cases
See how the tool fits into real work and everyday tasks.
A developer can convert a batch of field labels between snake_case and camelCase before mapping them in application code, then update references with an IDE-aware refactoring workflow.
A team can turn a list of lower camel names into uppercase underscore names as a draft for constants or environment-variable keys, then confirm its own style guide.
An analyst or technical writer can normalize a pasted list for a document or data dictionary without editing each name individually.
Q&A
Find concise answers to common questions and confusing cases.
Yes. Put each name on its own line; the selected conversion is applied independently to each line and output order is preserved.
No. It converts text strings only. It does not parse source files, find references, or account for scope, strings, comments, or language-specific syntax.
Not in every case. Capital boundaries are interpreted using general text rules, so review initialisms and mixed-case names manually before adopting the output.
Notes
Review scope, result limitations, and important precautions before use.
Case conversion does not verify that a name is legal or conventional in a particular programming language, framework, schema, or team style guide. It does not modify files or update references. Check punctuation, reserved words, acronym meaning, and downstream compatibility before applying converted names to a codebase.
Related
Discover related tools, collections, and available API capabilities.