Create time-ordered UUID version 7 values with cryptographic randomness, or inspect the timestamp stored inside an existing UUID v7.
UUID v7 exposes its creation time; do not treat it as a secret or an unpredictable token.
UUID v7 is a 128-bit identifier standardized by RFC 9562. Its first 48 bits contain a Unix timestamp in milliseconds, followed by version, variant, and random bits. This arrangement means UUID v7 values created later usually sort after earlier values when stored in their normal hexadecimal representation.
The generator uses the browser's cryptographic random-number source for the random portion. Values follow the familiar 8-4-4-4-12 UUID format and set the version nibble to 7 and the RFC variant bits to 10.
UUID v4 is almost entirely random. That makes it excellent when an opaque random identifier is required, but random insertion order can scatter new records across a database index. UUID v7 places time in the most significant bits, which can improve insertion locality while retaining substantial randomness.
Choose UUID v7 when chronological sorting and database-friendly insertion patterns are useful. Continue using UUID v4 when you specifically need a random identifier without an embedded creation timestamp.
unix_ts_ms | version | random_a | variant | random_b
48 bits | 4 bits | 12 bits | 2 bits | 62 bits
The timestamp is visible information. Decoding it does not break encryption because a UUID is not encrypted; the creation time is deliberately part of the format.
You can generate up to 1,000 values at once and copy or download them as plain text. Randomness makes collisions extraordinarily unlikely, but no client-side generator can coordinate ordering across every process or guarantee strictly increasing values produced within the same millisecond. Systems that require monotonic UUIDs should use a library with an explicit monotonic strategy at the point where identifiers are created.
Generation and decoding happen entirely in your browser. No UUID values are sent to MiniUtil. UUIDs are identifiers, not passwords, API keys, or session tokens. Use the Password Generator for credentials and the Hash Generator for message digests.
The implementation follows the UUID v7 field layout in RFC 9562. The decoder checks the hyphenated hexadecimal syntax, version nibble, variant bits, and embedded timestamp before displaying a result.
Keep working