Text input
Paste identifiers, headings, API fields, paths, or mixed separator text.
Convert words, identifiers, and text between common programming and writing case styles instantly.
Paste identifiers, headings, API fields, paths, or mixed separator text.
Read-only converted text. Input is treated as text only and never executed.
Converted output appears here as you type.
Load a sample or paste text to generate every supported case style.
Copy any converted value directly, or select a card to make it the main output.
Use string case conversion when the same words need to move between code identifiers, file names, API fields, headings, and documentation.
camelCase starts with a lowercase token and capitalizes following tokens. PascalCase capitalizes every token, which is common for classes, components, and types.
snake_case joins lowercase tokens with underscores and is common in data fields. kebab-case joins tokens with dashes and is often used for URLs, CSS classes, and file names.
Identifier cases remove spaces and use separators or capitalization. Heading cases keep spaces and make text easier to read for labels, titles, changelog sections, and documentation.
With acronym preservation enabled, all-caps tokens such as API, HTTP, and ID stay uppercase in readable and Pascal-style output. Numbers are split from adjacent letters for predictable token counts.
Spaces, dashes, underscores, dots, slashes, punctuation, and case boundaries can all be treated as token breaks. This keeps messy copied identifiers predictable without interpreting the text as code.
Convert database columns to TypeScript properties, API fields to environment keys, headings to file names, constants to labels, and copied logs to clean comparison-friendly identifiers.
No. Tokenization, conversion, copy actions, and downloads run locally in your browser.
By default it splits on spaces, punctuation, dashes, underscores, dots, slashes, numbers, and camelCase or PascalCase boundaries.
Yes. The preserve acronyms option keeps all-caps tokens uppercase in Title Case, Sentence case, PascalCase, Train-Case, and later camelCase tokens.
No. The default behavior uses predictable developer-friendly casing instead of locale-specific title casing rules.
No. Input is handled as plain text only. The tool does not evaluate JavaScript, templates, shell syntax, or expressions.