How to Convert Text Case: Title, Camel, Snake, and More

Case Converter on DevOkk.com applies the usual styles with a live preview. No account. This page is which style you actually want, and the ways a converter will confidently mangle a proper noun.

Case is a contract with the next reader

Writers care about Title Case versus sentence case because a CMS, a slide, and a newspaper all disagree. Developers care about camelCase, PascalCase, snake_case, and kebab-case because languages and ecosystems already picked. Mixing them in one API is how you get user_id in the database, userId in JSON, and UserID in a Go struct - which is survivable, but only if each layer is consistent.

A converter will not pick the contract. You do. The tool’s job is to apply one rule to a block so you are not sitting on Caps Lock for forty headings.

People show up here after Word changed “iPhone” to “Iphone,” or after a Slack thread of thirty identifiers that need to become kebab-case for CSS. Desktop apps and “free online converters” both work. The reason to prefer a browser-local one is the paste: a launch headline, a client’s product name, an internal route list.

If you already know the target style, open the tool. If you keep picking the wrong one, stay for the map.

The styles, without a lecture

UPPERCASE / lowercase. Useful for shouting, for constants in some languages, and for normalizing before a compare. Bad as a substitute for heading styles in a document you will send to a client.

Sentence case. First letter up, the rest a normal sentence. Right for most UI strings and many blog titles, depending on the house.

Title Case. Most words capitalized. Small words are a style-guide problem (and, or, the, of). A mechanical converter will get some of those wrong. Read the line.

camelCase. invoiceTotal. Common for JavaScript variables and JSON keys in many codebases.

PascalCase. InvoiceTotal. Types, components, some public methods.

snake_case. invoice_total. Python, many databases, some APIs.

kebab-case. invoice-total. URLs, CSS classes, some CLI flags.

There are more (train-case, alternating case as a joke). If you need a joke, you do not need this article.

Identifiers should not contain spaces. Headlines should. Do not run a headline through camelCase unless you are naming a function after it on purpose.

Convert a block, then read it like a diff

Open Case Converter. Paste only the lines you want changed - not a whole email with a signature. Pick the style. Copy the output.

Then read it. GitHub becomes Github or git_hub. iOS becomes Ios. PDF becomes Pdf. Acronyms and brand marks are where converters fail, because they are applying English-ish word splits, not a trademark list.

If you are renaming symbols in a repo, convert a sample, apply the change in the editor, and look at the git diff. A tab is a scratch pad. It is not a refactoring tool that updates imports.

For HTML you are about to turn into Markdown, get the words right first, then convert structure in HTML Markdown Converter. Case and markup are different jobs. Doing both at once is how you “fix” a heading and break an href.

Headlines versus identifiers

A headline can stay human: “How to convert text case.” An identifier cannot. If you need both, keep two strings. Do not publish a URL slug with spaces, and do not put kebab-case in a sentence as if it were English.

When the input is a list of mixed styles (UserName, user-name, user_name), normalize to one style in a single pass, then stop. Repeated conversions (camel → snake → camel) will not restore the original word boundaries. XMLParser may come back as xml_parser and then xmlParser, which is fine, or as x_m_l_parser, which is not.

If the job is “replace every fooBar that sits inside quotes,” that is a pattern. Use Regex Testing on a fixture string before you run a project-wide replace.

What converters get wrong

They do not know locale. Turkish dotted and dotless I, German ß, and names with particles (von, de) will not follow your English house style. They do not know that ID at the end of userID is a unit. They do not know your linter’s exception list.

They also do not encrypt. Changing case is not obfuscation. Pasting a production secret into a converter to “make it lowercase” is still pasting a production secret.

Very large pastes can get unwieldy in a text area. Convert in chunks if the browser complains. If you are transforming a generated dump of 50,000 keys, use a script you can review, not a web form.

Pick a style and apply it once

When the output matches the contract - house title style, or the identifier convention in the file you are editing - copy it and move on. Open Case Converter and keep the unpublished paragraph in the tab instead of in a stranger’s logs. If the next step is testing a rename pattern, switch to regex testing rather than inventing a case style that is really a search.