Match code conventions
Convert field names quickly when frontend and backend layers use different naming styles.
Case Converter
브라우저 내부 처리
Convert camelCase, snake_case, kebab-case and PascalCase.
Text case conversion workflow
Convert API fields, environment variables, filenames, and document titles into camelCase, snake_case, kebab-case, PascalCase, and related formats.
Clean URLs and filenames
Turn titles into slugs or kebab-case values for document paths, image names, and anchor links.
Review before bulk edits
Inspect how acronyms, numbers, and spacing are split before applying the result broadly.
Errors you will hit
Acronyms split in odd places
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.
Digit boundaries
Tools disagree on whether the digits in user2Name form a word boundary. Verify before using the result somewhere irreversible, like a database column name.
Things to check
Acronyms are team-specific
Terms like URL, ID, and API can be written as url, Url, or URL depending on convention. Adjust after conversion.
Meaning can shift
Combining words can change readability or meaning, so public URLs and API field names deserve a final review.
Acronyms break the rules
Converting HTTPServer to camelCase yields different results per language and linter. Names containing API, ID or URL need a manual check rather than trusting automatic conversion.
Digit boundaries differ
Converting user2FA to snake_case can give user_2_fa, user2_fa or user_2fa. Avoid digits in names that are hard to change later, such as database columns.
kebab-case is unusable in many places
A hyphen is a subtraction operator in most languages, so it cannot appear in a variable name. Reserve kebab-case for CSS classes, URL paths and filenames. Using it as a JavaScript object key requires quotes and bracket access.
More: step-by-step usage and worked examples
How to use it
- Enter the text or identifier list you want to convert.
- Choose the output case and review the converted value.
- Manually check values containing acronyms, numbers, hyphens, or underscores.
- Before pasting into code, compare the result with the existing naming convention.
Real input and output
One input, every convention
Input
user profile imageOutput
camelCase userProfileImage
PascalCase UserProfileImage
snake_case user_profile_image
kebab-case user-profile-image
CONSTANT USER_PROFILE_IMAGEConverting an existing identifier
Input
getHTTPResponseCodeOutput
snake_case get_http_response_code
kebab-case get-http-response-codeConsecutive uppercase acronyms are where implementations disagree most.
Tools that pair well
- Regex Tester
- Text Diff — Spotting what changed between two similar texts — config files, API responses — is something the eye always mi
- Markdown — The awkward part of writing a README, release note or issue template is not seeing the result until you commit
- Text Cleaner — Text copied from the web or a PDF carries invisible whitespace and zero-width characters.
- Character Counter — Application essays and reports usually come with a character limit, and organisations differ on whether spaces