Case Converter
Instantly convert strings between camelCase, snake_case, kebab-case, and Title Case.
Transform identifiers, headlines, and multi-line text across programming, prose, and delimiter-based casing formats using deterministic browser-side rules.
Use Case Converter
Text or Identifiers
Converted Result
Built for the task, not the page view
- 14 casing formats including camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, dot.case, and path/case
- Algorithmic Title Case, Sentence case, UPPERCASE, and lowercase without claiming editorial style-guide compliance
- Per-line or entire-text conversion modes
- Optional number splitting and consecutive-uppercase handling for identifier boundaries
- Copy and text download for converted output
Raw TextMulti-line TextConverted TextUse it correctly
Identifier conversion & word splitting
The engine decomposes identifiers into semantic words by identifying boundary signals: camelCase transitions from lowercase to uppercase, separator delimiters (_, -, ., /), and optional numeric boundaries. It then formats the detected words into your selected target casing style.
Per-line batch mode vs. entire-text mode
In per-line mode, each line of text is processed independently while preserving leading indentation (spaces or tabs) and line breaks. This is purpose-built for lists of database columns, JSON keys, CSS class names, or code blocks. In entire-text mode, line breaks are treated as word delimiters and the entire input is converted as a single unified text block.
Acronyms and consecutive uppercase tokens
When "Preserve consecutive uppercase" is checked, tokens like "XMLHttp" or "HTTPRequest" are intelligently split into "XML Http" and "HTTP Request". Furthermore, all-caps acronyms retain capitalization in PascalCase, camelCase, and Title Case. When unchecked, each uppercase letter triggers an individual word split.
Title Case vs. AP & Chicago style rules
EveryTools Title Case applies algorithmic initial capitalization (Start Case) to all detected words. Unlike publication editorial style guides such as AP (Associated Press) or Chicago Manual of Style, it does not lowercase minor prepositions, articles, or conjunctions (such as "in", "of", "the", "and"). Writers adhering to formal publishing guidelines should manually review minor words.
Local processing & zero API transmission
All case conversion operations run in local browser memory using native ECMAScript string algorithms. Your text is processed entirely on your device and is never submitted to an EveryTools transformation API or logged by any remote server.
Casing Formats Comparison
EveryTools supports 14 distinct case conventions. The table below demonstrates how two representative inputs—a database identifier (user_first_name) and a multi-word phrase with numbers (api v2 request)—are transformed across each format.
| Format | Sample Output 1 | Sample Output 2 | Common Use Case |
|---|---|---|---|
camelCase | userFirstName | apiV2Request | JavaScript / TypeScript variable and property names, JSON fields |
PascalCase | UserFirstName | ApiV2Request | Class names, React components, C# / Java types, TypeScript interfaces |
snake_case | user_first_name | api_v2_request | Python variables, SQL column names, PostgreSQL tables, REST URL query params |
CONSTANT_CASE | USER_FIRST_NAME | API_V2_REQUEST | Global constants, environment variables, Redux action types, enum members |
kebab-case | user-first-name | api-v2-request | CSS class names, HTML attributes, package names, slugified URLs |
SCREAMING-KEBAB-CASE | USER-FIRST-NAME | API-V2-REQUEST | COBOL variables, legacy mainframe protocols, custom HTTP header keys |
Title Case | User First Name | Api V2 Request | Article headlines, page titles, button labels, navigation menus |
Sentence case | User first name | Api v2 request | User interface helper copy, form field labels, readable descriptions |
UPPERCASE | USER FIRST NAME | API V2 REQUEST | Urgent notifications, legal disclaimers, text emphasis, banner headlines |
lowercase | user first name | api v2 request | Prose normalization, search index tokens, standard body copy |
dot.case | user.first.name | api.v2.request | Java package hierarchies, dot-notated configuration properties, metric keys |
path/case | user/first/name | api/v2/request | File system paths, nested routing paths, cloud storage keys |
Train-Case | User-First-Name | Api-V2-Request | HTTP header naming conventions, MIME type headers, hyphenated title formats |
sPoNgEbOb | uSeR fIrSt NaMe | aPi V2 rEqUeSt | Alternating mocking casing for social media memes and informal banter |
Title Casing Rules & English Stop Words
Formal publishing style guides such as the Associated Press (AP) Stylebook and the Chicago Manual of Style (CMOS) maintain specific guidelines regarding which words should be capitalized in headlines and titles.
Under AP and Chicago rules, short grammatical articles (a, an, the), coordinating conjunctions (and, but, for, or, nor, so, yet), and short prepositions (at, by, for, in, of, on, to, up, via) remain lowercase unless they appear as the first or last word of the title.
Notice: EveryTools Title Case implements deterministic algorithmic capitalization (Start Case / Capitalized Words), capitalizing the initial letter of every semantic word boundary. It does not parse natural language parts of speech or maintain language dictionaries. If your editorial workflow requires strict AP or Chicago compliance, please review minor conjunctions and prepositions after converting.
Identifier Conversion & Word-Boundary Splitting
Programming identifiers frequently combine multiple words without whitespace. To convert between languages and formats, EveryTools uses a multi-stage splitting pipeline:
- Consecutive uppercase grouping: When enabled, patterns like
XMLHttpsplit intoXML HttpandHTTPRequestsplits intoHTTP Request, preserving coherent acronyms. - CamelCase boundary detection: Transitions from lowercase letters or numbers to uppercase letters (
userId,item10Key) are split into individual words. - Numeric boundary splitting: When "Split on numbers" is checked, transitions between letters and numbers (
v2Api→v 2 Api) are isolated. Unchecking this option keeps alphanumeric tokens intact (v2Api→v2 Api). - Delimiter normalization: Underscores, hyphens, slashes, and punctuation marks are parsed as word delimiters.
Per-Line Batch Processing
Developers often need to convert lists of identifiers, such as converting database column names from an SQL table schema into JavaScript object properties, or transforming snake_case JSON keys into camelCase TypeScript interfaces.
Per-line mode evaluates each line independently. Crucially, it preserves leading indentation (both spaces and tabs) and blank lines. If your input includes nested code or structured lists, the indentation remains perfectly intact in the converted output.
In contrast, Entire-text mode treats the entire input as a single continuous block of words. This is recommended when formatting single prose titles, paragraphs, or article headlines.
Unicode Support & Privacy Guarantee
The case conversion engine utilizes Unicode property escapes (\p{L} and \p{N}) to correctly identify letters and numbers across global writing systems, including Latin accented characters (e.g., café, naïve, über), Cyrillic, Greek, and other non-ASCII scripts.
Zero API Transmission: All transformations are executed locally in your browser’s JavaScript engine. No text, variable names, or documents are transmitted over the network to an EveryTools transformation API. Your confidential code and proprietary identifiers remain strictly inside this browser tab.
Frequently Asked Questions
What is the difference between Title Case and Capitalized Words?
In linguistic and publishing terminology, "Capitalized Words" (or Start Case) capitalizes the initial letter of every single word indiscriminately. "Title Case" in formal human publications (such as AP or Chicago style) lowercases short minor words like "in", "of", "and", and "the". EveryTools applies uniform algorithmic word-initial capitalization to prevent misinterpreting context-dependent words.
How does per-line mode preserve indentation in source code?
Per-line mode inspects each line with a leading whitespace regular expression (/^(\s*)/). The detected indentation prefix is extracted and re-applied untouched to the beginning of the transformed line, guaranteeing that tab-indented or space-indented code blocks retain their structure.
How are numbers handled in variables like "apiV2Response"?
When "Split on numbers" is enabled, numeric transitions are treated as word boundaries, splitting apiV2Response into api, v, 2, and response (converting to api_v_2_response in snake_case). When "Split on numbers" is disabled, v2 remains a single word token, resulting in api_v2_response.
Is any text sent to an external server or logged?
No text content is sent to an EveryTools transformation API or analytics service. The case conversion runs in your browser memory; product analytics record only fixed interface events such as tool views and button actions, never the text you enter or the converted output.