UUID Studio

UUID Studio

UUID Converter

Convert any UUID representation to every other format - client-side.

  • đź”’ 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

  • UUID (RFC 4122) 
    550e8400-e29b-41d4-a716-446655440000
  • URN 
    urn:uuid:550e8400-e29b-41d4-a716-446655440000
  • Braced GUID 
    {550e8400-e29b-41d4-a716-446655440000}
  • 32-char hex 
    550e8400e29b41d4a716446655440000
  • Base64 (standard MIME) 
    VQ6EAOKbQdSnFkRmVUQAAA==
  • Base64 (URL-safe) 
    VQ6EAOKbQdSnFkRmVUQAAA
  • Uint128 (decimal) 
    113059749145936325402354257176981405696
  • JSON byte array 
    [85,14,132,0,226,155,65,212,167,22,68,102,85,68,0,0]
  • MongoDB $binary (subtype 04) 
    { "$binary": { "base64": "VQ6EAOKbQdSnFkRmVUQAAA==", "subType": "04" } }

About UUID Converter

UUIDs are 128-bit identifiers, but every system seems to write them differently — hyphenated lowercase here, braces there, a MongoDB driver wrapping Base64 in $binary, a C API expecting raw bytes. Translating between those forms by hand is exactly the kind of fiddly work a converter should handle for you.

Paste a UUID, hex string, standard or URL-safe Base64, a decimal uint128, a byte array, or MongoDB Extended JSON, and every common representation comes back at once - no guessing which one your framework or driver actually wants.

Conversion happens entirely with your browser's Web Crypto and JavaScript APIs; nothing you paste is ever sent to a server, which matters when the UUID in question is tied to a real user or a production incident.

FAQ

Does byte order change the UUID string?
MongoDB and some databases store UUIDs with a different endian layout in BSON. This tool shows standard RFC string forms from the parsed bytes; use the MongoDB tool if you need Extended JSON $binary.
Is my data uploaded?
No. Conversion happens entirely in your browser tab.
What formats are supported?
Plain UUID, URN, braces/parentheses, hex, standard and URL-safe Base64, uint128 decimal, JSON byte arrays, and MongoDB Extended JSON.