How it works
The converter splits the input into words, lowercases them, then rejoins using the separator and capitalisation of the chosen convention. Title and sentence case work on the original text rather than the lowercased words.
- Case changes are deterministic string transforms; acronyms and numbers stay where they are.
Why it matters
Renaming a field across an API, a database and a front end is a routine task that breaks when acronyms, numbers or accented letters are handled inconsistently. Seeing the same words in every convention makes the mapping obvious before code changes.
A worked example
The words user profile image become userProfileImage, user_profile_image, user-profile-image and UserProfileImage. Acronyms are lowercased first, so identifiers relying on ID need a manual check.
Common mistakes
- Converting acronyms blindly and losing meaning.
- Expecting language-specific casing such as Turkish dotted i.
- Renaming public API fields without a migration plan.
Practical tips
Decide the convention by destination, not taste: JSON APIs usually camelCase, SQL columns snake_case, URLs kebab-case. Keep old and new field names during a migration window instead of switching in one deploy.
How to use it
- Open the tool. Everything runs in your browser tab.
- Paste or type your input, then choose the action you need.
- Check the result and copy it with one click.
Common questions
Does camelCase handle acronyms correctly?
Words are lowercased before joining, so acronyms become normal words. Check identifiers that rely on capitalisation.
Why did accented letters change?
Case mapping is language-independent. Turkish dotted i, for example, may need manual correction.
Can I convert only part of the text?
Yes. Paste only the selection you want to transform.
Is this tool really free?
Yes. There is no account, no paywall and no usage limit. Tools App is funded by aumenso, the studio behind it.
Is anything I enter uploaded?
No. The tool runs in your browser tab; what you enter is never sent to us and never stored.