Case Converter — 9 Formats
Convert text between 9 case formats — UPPERCASE, lowercase, Title Case, Sentence case, camelCase, PascalCase, snake_case, CONSTANT_CASE, kebab-case.
工具代码会在浏览器中处理所选文件和输入内容，不会将其提交给 TOOLGRID 的处理接口。 TOOLGRID 只衡量工具使用情况，不记录你输入的内容。
- 不上传工具输入至 TOOLGRID
- 不登录
- 复制前先检查
Loading tool…
这个工具能做什么
Change text casing across nine common formats in one paste. Useful for renaming variables across coding conventions and reformatting headings.
Paste text into the input. The tool generates all nine common casing variants simultaneously — no need to pick one in advance. Copy whichever fits the context you're writing for.
Nine outputs in one pass: UPPERCASE (shout), lowercase (default), Title Case (headings), Sentence case (prose), camelCase (JavaScript), PascalCase (C#/Go types), snake_case (Python, SQL), CONSTANT_CASE (env vars, constants), and kebab-case (URLs, CSS classes, file names).
Especially useful when renaming a variable across coding conventions — type the variable name once, and you get every style instantly. No more mental gymnastics translating user_id to userId, UserId, USER_ID, and user-id by hand.
All conversion happens in your browser. Tool code does not submit entered text to a TOOLGRID processing endpoint; assess browser extensions, device security, and shared sessions before using any web tool with sensitive material. Pair with our Slug Generator when you need a URL-safe version, or Word Counter for sentence-level stats on the same input.
这个工具适合解决什么问题
Have a name in user_id but need it as userId for JavaScript, UserId for a C# class, and USER_ID for an env variable? Paste once and copy each style. Faster than hand-translating between four conventions.
A heading reads differently in Title Case (article headlines), Sentence case (UI copy), and UPPERCASE (badges, alerts). Try all three from one paste and pick what fits the surface.
kebab-case output is URL-safe, CSS-safe, and HTML-id-safe. Paste a feature name or article title to get a clean slug. For pure URLs with diacritic stripping, use the dedicated Slug Generator instead.
依赖结果前需要检查什么
- Performance and maximum practical input size depend on browser memory, device speed, and the structure of the input.
- Review the generated result before replacing or publishing an original file.
如果还需要校验、转换或复用结果，可以继续打开相近的浏览器本地工具。
如何使用
01使用场景
Have a name in user_id but need it as userId for JavaScript, UserId for a C# class, and USER_ID for an env variable? Paste once and copy each style. Faster than hand-translating between four conventions.
A heading reads differently in Title Case (article headlines), Sentence case (UI copy), and UPPERCASE (badges, alerts). Try all three from one paste and pick what fits the surface.
kebab-case output is URL-safe, CSS-safe, and HTML-id-safe. Paste a feature name or article title to get a clean slug. For pure URLs with diacritic stripping, use the dedicated Slug Generator instead.
Headings copied from CMSes often arrive in inconsistent capitalization. Paste them in and pick the canonical case (usually Sentence case for body content, Title Case for section headers).
Some projects use camelCase for variables but snake_case for DB columns and kebab-case for HTTP routes. One paste generates all three styles consistently — no manual rewriting between layers.
使用技巧
- 01Title Case vs Sentence case
Title Case capitalizes "important" words (most non-articles, non-conjunctions). Sentence case capitalizes only the first letter of the sentence and proper nouns. For UI strings, Sentence case is the modern convention. For article titles, Title Case still rules in English.
- 02camelCase vs PascalCase
Both join words by capitalizing internal letters. camelCase keeps the first letter lowercase (variables, methods); PascalCase capitalizes the first letter too (classes, types, constructors). Picking the right one is a code-style convention, not a meaning difference.
- 03kebab-case for URLs, snake_case for code, CONSTANT_CASE for env
URL slugs and CSS class names use kebab-case (hyphens are safe in URLs but not in identifiers). Python variables, SQL columns, and many configs use snake_case. Environment variables and global constants use CONSTANT_CASE in nearly every language.
- 04Acronyms confuse case converters
URLs vs Urls vs urls — there's no consensus on how acronyms should appear in camelCase/PascalCase. The tool follows Microsoft's PascalCase guideline (capitalize first letter only of multi-letter acronyms beyond 2 chars). If your project uses a different convention, you may need to manually adjust acronyms in the output.
常见问题
02Which case formats does this tool support?
Nine formats: UPPERCASE, lowercase, Title Case, Sentence case, camelCase, PascalCase, snake_case, CONSTANT_CASE, and kebab-case. All nine are generated at once from a single input paste — no need to select one in advance.
Does it support camelCase, PascalCase, and snake_case?
Yes — all three, plus six other common casing styles. Paste your input and copy whichever output variant you need. This is the main use case for the tool: translating an identifier between coding conventions instantly.
Can I convert multiple lines or paragraphs at once?
Yes. Paste any amount of text — sentences, paragraphs, lists, or code snippets. Every casing variant is regenerated as you type. Each variant treats the whole input as one logical "phrase" being recased.
How does it handle existing capitalization in the input?
The input's capitalization is ignored — each output applies its own casing rules from scratch. So "hello_world", "HelloWorld", and "hello world" all produce the same outputs across the nine variants.
Does it handle non-English characters?
It uses JavaScript's Unicode-aware toUpperCase()/toLowerCase() — so accented letters and most scripts case-fold correctly. For specialized linguistic rules (Turkish dotted/dotless I, German ß ↔ SS), results may vary; verify before using on non-English content.
Is my input sent to a server?
Case conversion runs in your browser. Tool code does not submit entered text to a TOOLGRID processing endpoint; review your browser, extensions, and device security before using any web tool with sensitive material.