What case styles can this tool convert between?

camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE (SCREAMING_SNAKE), dot.case, path/case, Title Case, and plain lowercase/UPPERCASE — from any of them to any other.

How does the converter detect word boundaries?

It splits on existing delimiters (_ - . /), on lower-to-upper transitions (camelCase → camel + Case), and on letter-digit boundaries, then reassembles in the target style — so userID2Value converts cleanly.

Which case style should I use where?

Common conventions: camelCase for JavaScript/Java variables, PascalCase for classes and React components, snake_case for Python and SQL, kebab-case for URLs, CSS classes and file names, CONSTANT_CASE for constants and env variables.

Can I convert many identifiers at once?

Yes — paste a list, one per line, and every line converts to the target style, preserving order. Ideal for migrating a config file or renaming a schema.

How are acronyms handled?

Sequences like APIKey or parseHTMLString split sensibly (API + Key, parse + HTML + String), so snake_case output is api_key, not a_p_i_key.

Case Style Converter — camelCase, snake

Remove Ads

Share on Social Media:

Case Style Converter — Every Naming Convention, One Tool

The same concept is userAccountId in JavaScript, user_account_id in the database, UserAccountId as a C# property, user-account-id in the URL, and USER_ACCOUNT_ID in the environment file. Crossing those boundaries by hand invites typos that only surface at runtime. This free converter transforms identifiers between all major case styles — singly or as whole lists — with smart word-boundary and acronym detection. Instant, in-browser, no signup.

Convention Map

Style	Example	Home turf
camelCase	userAccountId	JS/Java variables, JSON keys
PascalCase	UserAccountId	Classes, React components, C# members
snake_case	user_account_id	Python, Ruby, SQL columns
kebab-case	user-account-id	URLs, CSS classes, CLI flags, filenames
CONSTANT_CASE	USER_ACCOUNT_ID	Constants, env variables
dot.case	user.account.id	Config keys, i18n paths

Why Boundary Detection Is the Hard Part

Splitting parseHTMLToJSON2 correctly requires knowing that HTML is one word, To starts another, and the digit belongs with JSON2's boundary — naive uppercase-splitting yields p_a_r_s_e nonsense. The converter's boundary logic handles consecutive capitals (acronyms), digit transitions, and mixed existing delimiters, which is what makes batch conversion of a real codebase's identifiers trustworthy.

Batch Migration Workflow

Migrating an API from snake_case to camelCase responses? Paste the column list from your schema, convert to camelCase, and you have the field-mapping table for your serializer in seconds. The same trick works for CSS-class renames, env-file generation from config keys, and documentation tables that must show names in multiple conventions.

Free and Instant

Unlimited conversions, all local — schema names and internal identifiers stay on your machine.

Case Style Converter

Result