Case Converter
Convert text to uppercase, lowercase, title case, camelCase, snake_case, or kebab-case instantly.
How to use this tool
- 1Type or paste your text into the top textarea.
- 2Click one of the six format buttons: UPPERCASE, lowercase, Title Case, camelCase, snake_case, or kebab-case.
- 3The converted result appears in the output textarea below.
- 4Click the Copy button in the top-right corner of the output to copy to clipboard.
About Case Converter
One phrase often needs to appear in several naming styles: Title Case for display, snake_case for SQL columns, kebab-case for CSS classes, camelCase for JavaScript keys, and UPPERCASE for constants. A case converter turns a single input string into any of those formats so you do not have to retype it by hand or introduce a typo that slips into production config.
Naming conventions matter because different systems enforce different rules. API gateways reject payloads when field names do not match the schema. ESLint fails builds on naming violations. Design tokens break when Figma exports use spaces but stylesheets expect hyphens. Content teams ship ALL CAPS headlines that look fine in a slide deck and harsh in a URL. Teams that span design, editorial, and engineering need reliable transforms between these formats.
Paste the source text, click a format button, and copy the result. UPPERCASE and lowercase use the runtime case fold. Title Case capitalizes each whitespace-separated word. camelCase lowercases the first segment, capitalizes later word starts, and drops separators. snake_case joins lowercase segments with underscores. kebab-case joins with hyphens.
Conversion stays on your device; nothing is sent to a formatting service. Digits stay digits, so ISO9001 will not auto-split. Punctuation can glue into illegal identifiers if you aimed at code symbols. Accented letters follow the browser toLowerCase and toUpperCase behavior, which usually helps Western European text and can surprise Turkish dotted I handling. Multi-line paste may become one long token if newlines are not treated as separators — spot-check a sample first.
Turn a product label into a GraphQL field in camelCase before editing the schema. Build a kebab-case git branch name from a ticket title without a shell alias. Normalize CSV headers to snake_case ahead of a Postgres load. Produce Title Case nav labels from an all-lowercase CMS dump. Soften a shouting changelog block to lowercase for release notes. Map spaced design tokens into kebab-case utility class names.
People searching convert text to camelCase, snake_case generator from words, title case converter online, or kebab case from string want exactly these six buttons. This is not a locale-perfect Unicode case mapper for every script, and it is not a codebase-wide rename codemod. It is for the string in the box.
Gotchas: camelCase on already-capitalized acronyms can yield awkward runs like xMLParser unless you normalize first. snake_case does not pluralize. Title Case capitalizes short words such as "of" and "the," so AP-style headlines still need a manual pass. Pasting URLs with slashes into kebab-case creates junk — strip punctuation for identifiers.
For NDA copy, convert, copy, clear, and close the tab. No server log retains your naming experiments. Teams that maintain public APIs should publish an identifier style guide and keep this converter bookmarked during schema reviews. When the guide already defines camelCase versus snake_case, the converter is a mechanical helper instead of a debate table.
For bulk CSV header cleanup, convert a few representative headers first and load them into a staging table before touching production. Encoding issues and blank column names surface early that way. Once the pattern is proven, apply the same casing pass across the full header row.
Frequently asked questions
Mixed separators confuse naive word splits because boundaries are inconsistent. Normalize to spaced words first, or convert in careful passes on a short sample. Unexpected glued tokens are a common bulk-rename scenario to catch early. Clean source text with clear separators always converts more reliably than half-migrated identifiers.
Empty input produces empty output without a hard failure state. That keeps the interface calm while you clear and repaste. If a format button appears to do nothing, confirm the source textarea actually received text. Clipboard delays on some browsers create a false failure scenario when the input never arrived.
This converter uses straightforward per-word capitalization rather than AP or Chicago small-word exceptions. Marketing headlines often need a second manual pass for those particles. Treat the output as a drafting aid, not a finished stylebook verdict. Knowing the rule prevents surprise when every word lights up.
Find-and-replace wins when the string already lives inside a large file and you need scoped edits with context. A case converter wins when you invent a new identifier from a human phrase and want one-click formats. Convert here, paste into the file, then let the editor handle neighbors. Neither replaces a project-wide symbol rename for references already scattered everywhere.
Typical camelCase output lowercases the first segment, matching JavaScript variables and many JSON keys. PascalCase uppercases that first letter and is common for React components and C# types. Capitalize the first character of the camelCase result when your styleguide demands PascalCase. Verifying the first character avoids schema mismatches.
Most Latin letters follow the JavaScript string methods in your browser. Some locales have special casing rules a generic converter will not apply. Test a representative sample of customer names before bulk work. Scenario failures often show up as incorrect dotted I behavior or unexpected ligature casing.
Punctuation can remain embedded and create illegal programming identifiers. URLs contain colons and slashes that do not belong in snake_case columns. Strip or replace punctuation before converting when the target is code. Display-only Title Case of a sentence with commas usually survives without harm. In practice, re-run Case Converter on a smaller sample after each change so you can see which input detail caused the mismatch. Keep the original nearby until you trust the export.
Web routes conventionally prefer kebab-case because underscores are easy to miss in links. snake_case remains dominant in SQL and Python modules. Use kebab-case for paths and CSS classes, snake_case for database fields. Matching platform norms beats inventing a third house style. In practice, re-run Case Converter on a smaller sample after each change so you can see which input detail caused the mismatch. Keep the original nearby until you trust the export.
The converter itself may still emit a string that starts with a digit or contains leftover punctuation. Downstream parsers then throw syntax errors when you paste it into code. Strip illegal characters before converting if the target is a symbol name. Treat those compile failures as a scenario that started with dirty input, not a casing bug.