UUID Studio

UUID Studio

Case Converter

Convert identifiers between camelCase, snake_case, kebab-case, and more.

  • đź”’ No data stored or uploaded
  • ⚡ 100% client-side
  • 🆓 Free, no account
Click Convert when ready

Override only when Auto cannot parse your paste. Changing this loads a matching sample into Input — click Convert to run. Use Load sample to cycle every format example.

All conversions

Read-only representations of the same 16 bytes. Every textual form is listed here, not in “Prefer format”.

Paste two values: if both sides are valid JSON, a structural diff appears; otherwise UUID / bytes are compared when both decode to the same format.

A
B

Create or edit JSON here (syntax colors), then format, validate, or convert - same as MongoDB $binary UUID blobs on the Convert tab once detected.

New document

Hash, HMAC, AES-GCM/CBC + RSA-OAEP, codecs, JWT decoding, UUID v4, and secure random - all client-side. JWTs use Base64URL (three segments), not a single MIME Base64 block - use Decode JWT below, not raw Base64 decode.

Examples

  • snake_case input 
    user_first_name
  • Title input 
    Convert This Sentence

About Case Converter

Every language and file format seems to insist on a different naming convention - JavaScript wants camelCase, Python and databases want snake_case, URLs and CSS want kebab-case, classes want PascalCase - and translating a variable name by hand between them is tedious and error-prone.

Paste any identifier or short phrase, in any of those conventions, and get every common case variant back at once: camelCase, PascalCase, snake_case, kebab-case (also handy as a URL slug), CONSTANT_CASE, Title Case, and Sentence case.

Word boundaries are detected from capitalization changes, underscores, hyphens, and spaces, so mixed input like `some_example-Text here` still splits into sensible words before reassembling.

FAQ

Does it handle acronyms like 'userID' correctly?
Consecutive capitals are treated as a single word boundary (so 'userID' splits into 'user' and 'id'), which matches how most style guides treat acronyms - though very unusual mixed-case input may need a manual tweak.