Text Case Converter — camelCase, snake_case & 7 More, Round-Trip Correct

Convert identifiers and phrases between all nine developer cases at once: camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, Title Case, Sentence case, dot.case, slug. The part naive converters get wrong is the split: this one handles camelCase boundaries AND acronym runs correctly — parseHTMLParserOutput splits to parse html parser output, not parse h t m l.... Up to 200 texts per run, online, by API, or as an agent tool via Apify MCP.

Renaming API fields, generating code from schemas, migrating a codebase's naming convention, normalizing CSV headers — all reduce to reliable case round-trips at scale.

What you get

• All 9 cases per input (or just one via targetCase)
• Correct tokenization: camel boundaries, acronym runs (HTMLParser → HTML + Parser), mixed delimiters (user_profile-settings.page splits on all of them)
• Fail-soft honesty: an unknown targetCase is a guidance record listing the valid set — never a silent "here's everything instead"; tokenless input is {ok: false} — both never charged.

Input

{ "texts": ["user profile settings", "parseHTMLParserOutput"], "targetCase": "snake" }

Omit targetCase for all nine. Aliases accepted (kebab, dash, screaming-snake-case...).

Output (real run)

{
  "input": "parseHTMLParserOutput",
  "ok": true,
  "camelCase": "parseHtmlParserOutput",
  "PascalCase": "ParseHtmlParserOutput",
  "snake_case": "parse_html_parser_output",
  "kebabCase": "parse-html-parser-output",
  "CONSTANT_CASE": "PARSE_HTML_PARSER_OUTPUT",
  "titleCase": "Parse Html Parser Output",
  "sentenceCase": "Parse html parser output",
  "dotCase": "parse.html.parser.output",
  "slug": "parse-html-parser-output"
}

Every one of those values is asserted exactly by our release test.

Pricing

$0.0004 per text converted — all nine cases included. Tokenless inputs and unknown target cases are never charged.

No direct paid case-converter incumbent was found on the store (2026-08-07 search — results are file/OCR converters). Pricing is the cost-plus floor of our ladder, stated plainly.

Honest limits

• ASCII-oriented tokenization (letters/digits); accented identifiers work but aren't transliterated — for URL slugs from natural-language titles with diacritics, use our sibling Slug Generator, which owns transliteration + collision dedupe. This tool owns identifier casing round-trips.
• Acronym recomposition follows the standard convention: HTML becomes Html in camel/Pascal (parseHtmlParserOutput) — the same choice most style guides and code generators make.
• Title Case is simple capitalization (no small-word rules like "of"/"the" lowercase — those are editorial style, not identifier casing).

FAQ

What's the difference from the Slug Generator? Different problems: this converts BETWEEN developer cases with round-trip-correct splitting; the slug tool produces URL-safe slugs from natural language with Unicode transliteration. slug here is a convenience field for ASCII identifiers.

How are acronyms handled? HTMLParser splits as HTML + Parser (the consecutive-capitals rule); recomposed camel is htmlParser. Asserted in the release test.

Can I batch a whole schema's field names? Yes — up to 200 per run, one record each; pass targetCase to get exactly the field you're migrating to.

What inputs does it split on? Spaces, underscores, hyphens, dots, any punctuation, plus camel boundaries — mixed-delimiter inputs like user_profile-settings.page normalize cleanly.

Why did some rows come back ok: false? No convertible words (symbols only), or you asked for a case that doesn't exist (the error lists the valid nine). Never charged.

Use from code or AI agents

curl -s "https://api.apify.com/v2/acts/EliAI~text-case-converter/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -X POST -H 'Content-Type: application/json' \
  -d '{"texts": ["first_name", "lastName", "EMAIL_ADDRESS"], "targetCase": "camel"}'

Agents: connect Apify MCP and call the EliAI/text-case-converter tool.

• Capability: round-trip case conversion between 9 developer cases with correct camel/acronym splitting
• Required input: text (string) or texts (array); optional targetCase
• Returns: one record per text with all (or the one requested) case forms
• Bounded: 200 texts per run; failures isolate per text
• Side effects: none