UUID Shortener

UUIDs are globally unique but lengthy—36 characters including hyphens. When you need to share identifiers in URLs, display them in user interfaces, or keep them compact in logs, UUIDs become unwieldy. This tool 压缩es UUIDs to 22-character base62 strings through lossless conversion, allowing you to reference the same UUID in a much shorter form while retaining the ability to expand it back to the full UUID.

Base62 encoding

Base62 uses digits (0-9), uppercase letters (A-Z), and lowercase letters (a-z)—62 characters total. This is much more efficient than hexadecimal (base16) for representing the same value. A 128-bit UUID (the maximum value that can be represented by 16 bytes) 转换s to a 22-character base62 string, reducing the character count by more than 39% while remaining fully reversible.

Lossless 压缩ion

Unlike lossy 压缩ion, this conversion is completely reversible with no data loss. You can shorten a UUID and later expand it back to get the exact same UUID. The mathematical relationship is deterministic: a given UUID always produces the same short ID, and that short ID always expands to the original UUID.

When to use short UUIDs

Display identifiers in user interfaces where space is limited. 创建 shorter URLs for sharing resources (e.g., example.com/files/a1b2c3d4e5f6g7h8 instead of example.com/files/550e8400-e29b-41d4-a716-446655440000). Include identifiers in user-facing codes or reference numbers. Store in databases where compact representation saves storage and improves query performance.

Bidirectional conversion

The tool works in both directions. Shorten UUIDs for user-facing scenarios, then expand them back when you need to reference the original. Since conversion is deterministic, you never lose in格式化ion—just space on the screen or in storage.

URL safety

Base62 uses only alphanumeric characters, making short IDs safe for URLs, email, SMS, and other text-based contexts where special characters might cause encoding issues. No percent-encoding required.