Renaming a public identifier without checking consumers
Field names, environment variables, selectors, and routes can be external contracts. Compare references and tests before replacing an existing name.
Case Converter for camelCase, snake_case, and 8 More Styles
TextRuns in Your Browser (No Uploads)
Convert each line of pasted text into 10 reviewable case styles: UPPERCASE, lowercase, mechanical Title Case, camelCase, PascalCase, snake_case, SCREAMING_SNAKE_CASE, kebab-case, dot.case, and path/case. Each line is tokenized independently, source line endings are retained, and review notices expose acronym splitting, Unicode case expansion, numeric-leading identifiers, and mechanical title casing instead of claiming language-aware rewriting.
What to do next
Continue with a related workflow or open the next tool that usually follows this task.
Workflow guide
Rename identifiers safely across code, data, and routes
Use a case converter to draft names, then treat every rename as a contract change: inventory consumers, define acronym rules, review invalid identifiers, compare a diff, and verify the destination.
OpenRelated toolDiff Checker for Text, Code, and Unified Patches
Compare bounded text locally with exact line hunks, code-point highlights, and unified patch export.
OpenRelated toolSlug Generator | Create Unicode or ASCII URL Slugs
Create bounded Unicode or ASCII URL slug candidates locally with explicit review controls.
OpenRelated toolFind and Replace Text | Literal and Regex Replacement
Replace literal or regex matches with Unicode boundaries, capture tokens, exact counts, and Worker limits.
OpenHow to Use This Tool
Paste one label, mixed identifier, CSV header list, or other text block into the input.
Run the converter manually, or keep live mode on for a short input that should update after typing stops.
Check the source-line and identifier-word counts before trusting a batch result.
Read warnings for punctuation-only lines, digit-leading identifiers, acronyms, and Unicode mappings that change length.
Compare the punctuation-and-spacing-preserving UPPERCASE/lowercase results with the eight word-normalizing identifier variants.
Copy only the required result, then validate references, reserved words, filesystem rules, or style-guide requirements in the destination.
When to Use This Tool
Draft variables, functions, types, and components
Turn labels such as User Display Name into camelCase or PascalCase, then verify reserved words and references in the target language.
Prepare database and import field names
Convert copied column headings line by line into snake_case while keeping row order and one result line per received input line.
Review path and file naming options
Compare kebab-case, dot.case, and path/case candidates before creating a route, package key, configuration path, or filename.
Plan a naming-convention migration
Inspect how legacy names split at camel and acronym boundaries before planning a rename across code, tests, documentation, and clients.
Start a heading copy-edit
Create a mechanical capitalization candidate for headings, then apply the publication's actual small-word, acronym, brand, and language rules.
Common Mistakes
Assuming acronym capitalization is project-aware
XMLHttp becomes xmlHttp and APIResponse becomes apiResponse. Projects that require XML, API, ID, or OAuth in a particular form need a manual acronym pass.
Using a digit-leading result directly in code
A name such as 2026 release becomes 2026Release, which is not a valid identifier in many languages even though the conversion itself is deterministic.
Treating mechanical Title Case as an editorial style guide
The Title Case result capitalizes every detected word mechanically. It does not implement AP, Chicago, sentence-case, brand, or language-specific editorial rules.
Expecting punctuation to survive every variant
Word-based variants remove or replace spaces and punctuation. UPPERCASE and lowercase preserve them, so choose the result whose normalization behavior matches the destination.
Examples
Convert mixed identifier syntax
The acronym boundary before Http and the separators before request and id become four identifier words. Acronyms are normalized instead of preserved specially.
Input
XMLHttp request-idOutput
camelCase: xmlHttpRequestId | snake_case: xml_http_request_id | Title Case: Xml Http Request IdConvert a batch without joining its lines
Each textarea line is converted independently. Browser textarea input normalizes CRLF and CR to LF, so this example preserves line order rather than original file-byte endings.
Input
First Name
APIResponse
Output
camelCase: firstName
apiResponse
| snake_case: first_name
api_response
How Unicode word boundaries become 10 case variants
The tokenizer recognizes Unicode letters, combining marks, and numbers. It inserts a boundary from a lowercase letter or number to an uppercase letter and before the final capital of an acronym when a lowercase word follows, so XMLHttp becomes XML plus Http.
UPPERCASE and lowercase call the Unicode default casing operations on the original line and preserve its punctuation and spacing. Those two results can expand in length when Unicode defines a multi-character mapping.
The other eight results lowercase each detected word, then join or capitalize the words according to the selected convention. Characters outside letters, marks, and numbers act as boundaries and are not copied literally into those variants.
The engine recognizes CRLF, LF, CR, LINE SEPARATOR U+2028, and PARAGRAPH SEPARATOR U+2029 and retains separators present in the received string. Direct browser textarea input normalizes CRLF and CR to LF before conversion, so retained separators do not prove the original file bytes.
Mechanical Title Case capitalizes each detected word after lowercasing it. This predictable transform is useful for review, but it is intentionally not advertised as sentence case or as an AP, Chicago, brand, or language-aware headline algorithm.
The exact limits are 2 MiB of UTF-8 input and 100,000 logical lines. Processing is local and non-mutating; the limit bounds the memory cost of holding 10 complete results at once.
Frequently Asked Questions
Which case styles does this converter produce?
There are exactly 10: UPPERCASE, lowercase, mechanical Title Case, camelCase, PascalCase, snake_case, SCREAMING_SNAKE_CASE, kebab-case, dot.case, and path/case.
Are multiple lines converted independently?
Yes. Every received logical line is tokenized separately, and a terminal line ending in that received string is retained. The engine can preserve CRLF, LF, CR, U+2028, and U+2029, but direct textarea input follows browser normalization that changes CRLF and CR to LF; this is not a byte-level line-ending inspector.
What happens to spaces, hyphens, emoji, and punctuation?
UPPERCASE and lowercase preserve spacing and punctuation. The other eight styles keep Unicode letters, combining marks, and numbers as words while normalizing other separators to spaces, underscores, hyphens, periods, slashes, or no separator.
How are camelCase input and acronyms split?
Camel and acronym boundaries are detected, but acronym policy is not guessed. XMLHttpRequest becomes xmlHttpRequest, so review terms such as API, URL, ID, OAuth, and product names against your project rules.
How does Unicode casing work?
The converter uses JavaScript's Unicode default upper- and lowercase mapping, not a language-specific editorial locale. Uncased scripts remain unchanged, combining marks stay attached, and some mappings such as ß to SS can change length.
Are generated values guaranteed to be valid code identifiers?
Not automatically. A leading number, reserved word, empty normalized line, or destination-specific restriction can still make a result invalid. The tool flags digit-leading lines but cannot validate every programming language.
Is the pasted text uploaded or included in analytics?
Conversion runs in your browser. Aggregate analytics can record byte count, line count, token count, variant count, and warning flags, but not the pasted text or copied result.
How This Tool Was Verified
Maintained and tested by SimpleWebUtilsReviewed
Method: In Case Converter for camelCase, snake_case, and 8 More Styles, the “Review automatic candidates before a migration” fixture was run without repairing or simplifying its input. We verified the transition from “Write the destination naming policy” to “Review tokenization and warnings”, compared the final artifact or values, and reviewed “Changing an API or database key without a migration” plus “Accepting every acronym conversion” as non-success paths.
Expected result: The converter proposed xmlHttpRequestId and 2026Release, while the review output kept the XMLHttp acronym decision and invalid leading-digit risk visible for manual approval.
Open the tested workflowRelated workflow guides
Use these focused guides when you need a practical workflow before opening the tool.
Workflow guide
Rename identifiers safely across code, data, and routes
Use a case converter to draft names, then treat every rename as a contract change: inventory consumers, define acronym rules, review invalid identifiers, compare a diff, and verify the destination.
Workflow guideDeduplicate lines from lists and logs without losing order
A practical workflow for turning repeated one-item-per-line data into an auditable unique list while preserving the first useful occurrence.
Workflow guideSort unique lines naturally before an import
A review-first workflow for producing a unique, naturally ordered list of IDs, names, URLs, tags, or labels without confusing sorting with normalization.
Workflow guideCreate URL slugs and preserve existing links
A slug generator can produce a consistent path-segment candidate, but it cannot own the route or protect a published address. This workflow records the target platform and current URLs, chooses an explicit Unicode or ASCII convention, reviews transliteration and encoded length, checks duplicates and reserved names in the real namespace, and treats redirects, canonical metadata, internal references, sitemap updates, monitoring, and rollback as required parts of any live URL change.
Workflow guideClean lists, logs, and copied text with a repeatable pipeline
Text cleanup is safest when it is treated as a sequence of explicit, reversible transformations. Preserve the source, identify line and delimiter boundaries, make one structural change at a time, promote only reviewed output to the next step, and compare the final text with the destination contract before publishing, importing, or sharing it.
Related Tools
Continue with another maintained workflow
Diff Checker for Text, Code, and Unified Patches
Compare bounded text locally with exact line hunks, code-point highlights, and unified patch export.
Text
Slug Generator | Create Unicode or ASCII URL Slugs
Create bounded Unicode or ASCII URL slug candidates locally with explicit review controls.
Text
Find and Replace Text | Literal and Regex Replacement
Replace literal or regex matches with Unicode boundaries, capture tokens, exact counts, and Worker limits.
Text
Unicode Normalizer | Compare NFC, NFD, NFKC and NFKD
Normalize Unicode with code-point evidence and explicit compatibility-loss warnings.
Encoding
Word Counter | Words, Graphemes, Code Points and UTF-8 Bytes
Count word-like segments, graphemes, code points, UTF-16 units, UTF-8 bytes, lines and reading time locally.
Text