Match code conventions
Convert field names quickly when frontend and backend layers use different naming styles.
🔒 Browser-side processing
Convert camelCase, snake_case, kebab-case and PascalCase.
Guide
Convert API fields, environment variables, filenames, and document titles into camelCase, snake_case, kebab-case, PascalCase, and related formats.
Convert field names quickly when frontend and backend layers use different naming styles.
Turn titles into slugs or kebab-case values for document paths, image names, and anchor links.
Inspect how acronyms, numbers, and spacing are split before applying the result broadly.
Workflow
Examples
Input
user profile image
Output
camelCase userProfileImage
PascalCase UserProfileImage
snake_case user_profile_image
kebab-case user-profile-image
CONSTANT USER_PROFILE_IMAGE
Input
getHTTPResponseCode
Output
snake_case get_http_response_code
kebab-case get-http-response-code
Consecutive uppercase acronyms are where implementations disagree most.
Troubleshooting
Runs of capitals like HTTP, ID, or URL are hard to segment. Some tools turn getHTTPResponse into get_h_t_t_p_response. Check acronyms by eye after converting.
Tools disagree on whether the digits in user2Name form a word boundary. Verify before using the result somewhere irreversible, like a database column name.
Review
Terms like URL, ID, and API can be written as url, Url, or URL depending on convention. Adjust after conversion.
Combining words can change readability or meaning, so public URLs and API field names deserve a final review.
Related