Generate tracing IDs
Create a fresh UUID quickly when you need a request, session, or incident reference while debugging.
UUID Converter
브라우저 내부 처리
crypto.randomUUID() generation plus hex(binary16) round-trips.
Common reasons to use this UUID converter
Review database storage formats
Convert string UUIDs into hex(binary16) when comparing storage strategies for binary columns or compact transport formats.
Restore legacy values
Turn raw 32-character hex values back into standard UUID form so they are easier to inspect and compare.
Questions that come up in practice
Why use hex(binary16)?
It removes hyphens and can fit more naturally into compact binary storage strategies than a plain UUID string.
Should I use UUID v7 instead?
If you need time-sortable identifiers, pick UUID v7 in the generation mode above. Its first 48 bits are a millisecond timestamp, so values sort by creation order. Use v4 when you want pure randomness, or ULID when string readability matters.
Does this page upload UUIDs anywhere?
Generation and conversion happen in the browser. You should still account for browser extensions or your own security policies when handling sensitive identifiers.
Choosing an identifier
v7 exposes creation time
The first 48 bits of a UUID v7 are a millisecond timestamp, so the value reveals when it was created. If a user ID is v7 and appears in a public profile URL, that person's sign-up time is public. Keep a separate v4 for publicly exposed identifiers.
A UUID is not a secret
Even v4 is merely hard to guess, not confidential. A design where "anyone with the URL can view it" is weak regardless of version. Access control belongs elsewhere.
Storage form drives index size
CHAR(36) uses 36 bytes including hyphens; BINARY(16) uses 16. On a primary key that 20-byte gap multiplies across every secondary index — at the cost of no longer being readable in logs.
More: step-by-step usage and worked examples
The most practical order for using this page
1. Generate first when you need a fresh identifier
Start with UUID v4 or ULID when you need a tracing ID, a temporary reference, or a clean test value right away.
2. Compare storage formats through round-trip conversion
When logs, binary columns, or legacy datasets hold the same value in a different format, convert both ways before assuming they differ.
3. Move to UUID v7 when ordering matters
If the real question is about time-ordered identifiers, switch the generation mode to UUID v7 and compare it with v4 on this same screen. The v4 vs v7 guide covers the trade-offs.