Case Converter
One-click conversion between UPPER, lower, Title, camelCase, snake_case and kebab-case — stop retyping field names.
>_ USAGE GUIDE
Paste your text and convert it in one click to UPPER CASE, lower case, or Title Case, plus the three naming conventions developers reach for daily: camelCase, snake_case, and kebab-case. Turning user_name fields into userName, converting a design spec's CSS classes into variable names, or normalizing config keys becomes a paste-and-copy job instead of manual retyping.
- Paste your text: a single identifier, a list of field names, or CSS class names
- Pick the target format: UPPER, lower, Title, camelCase, snake_case, or kebab-case
- Copy the result: grab the converted text and drop it straight into your code
Consecutive capitals are treated as acronyms and split at word boundaries: HTTPServer becomes http_server, not h_t_t_p_server. That single rule handles most real-world identifiers correctly, including abbreviated names such as parseHTMLDocument or userID.
The highest-frequency moments for this tool are API naming reviews and cross-language handoffs: an API spec written in snake_case feeding a JavaScript frontend that expects camelCase, or a design handoff where CSS classes must become JS constants. One paste, one click, one copy — instead of retyping every name by hand and silently introducing typos. Conversion runs locally and instantly, with nothing uploaded and nothing stored.
>_ FAQ
Q1 · Where is each naming convention used?
Common conventions: Java and JavaScript variables and methods use camelCase (userName); class names, components, and C# methods use PascalCase (UserService); Python variables and database fields use snake_case (user_name); CSS classes and URL paths use kebab-case (user-name). Following each community's convention beats personal preference — this tool converts between them losslessly.
Q2 · How are consecutive capitals like HTTPServer converted to snake_case?
They are treated as an acronym and kept whole: HTTPServer becomes http_server, never h_t_t_p_server. Converting back, http_server restores to HttpServer; a few acronym boundaries may differ from the original naming, so give the result a quick scan when acronyms are involved.
Q3 · What happens to digits and non-Latin characters?
Chinese and other non-cased scripts pass through unchanged, since upper/lower case does not apply to them. Digits are treated as ordinary characters and kept as part of a word — user2name stays connected rather than being split at the digit.
Q4 · Can I batch-rename dozens of keys inside a JSON document?
Yes. Paste the names one per line — with two or more lines the tool automatically switches to line-by-line batch mode: results are aligned by line number, a failing line is flagged without affecting the others, and up to 5000 lines are processed. To rename keys across a whole JSON document, copy the key list out with the JSON Formatter first, paste the lines here, convert, and paste them back.
Q5 · Is this case converter free and private?
Completely. There is no login, no limit, and no upload — every conversion runs locally in your browser, and the page works offline once loaded. Paste proprietary config keys or internal field names without worry.