UUID Inspect

Generate and inspect ID/random/timestamp values in your browser. No input is sent to a server. Use it for first-pass spec compliance checks.

Status

Version

Variant

UUIDv7?

Timestamp (ms)

Timestamp (UTC)

Timestamp (TZ)

Runs in your browser. No input is sent to a server. Use this as a first-pass diagnostic step.

How to use

Paste a UUID and click “Inspect”. For UUIDv7, it also extracts timestamp(ms).

Notes (this tool)

  • A valid format does not guarantee issuer or usage correctness; verify context separately.
  • UUIDv7 timestamps are estimates; strict ordering within the same millisecond is not guaranteed.

About this page

What does this page do?

Among the UUID tools, this is the hub that centralizes terminology and structure. It focuses on the meanings you need for inspection.

This page focuses on inspection. Use the Generator to issue UUIDs, and Timestamp→UUID / Range Builder to build boundary UUIDs from time.

Key points (from the RFC)

  • The string form is hex-and-dash (upper/lower/mixed case allowed).
  • unix_ts_ms is a 48-bit big-endian unsigned Unix timestamp in milliseconds.
  • The Version field is bits 48–51; v7 means value 7.
  • For RFC UUIDs, the Variant is 0b10 (RFC4122).
  • Remaining bits provide uniqueness; implementations may also use constructs for monotonicity.

Debugging workflow (recommended)

  • Generate or paste a value
  • Check format, timestamp, and character constraints
  • Confirm against destination validation requirements

Operational notes

  • Format validity does not guarantee security or uniqueness. Confirm requirements by use case.
  • Align randomness, timestamp, and formatting handling with your operational policy.

Referenced specs

  • RFC 9562 (UUIDv7 structure and fields)
  • Variant: RFC4122 family (0b10)
  • Version field (v7)
  • unix_ts_ms: 48-bit (big-endian)
  • String form: hex-and-dash (ABNF)

FAQ (UUIDv7)

How is it different from UUIDv4?

UUIDv4 is primarily random; UUIDv7 embeds time (milliseconds) in the most significant bits.

Can it parse UUIDs without dashes?

A 32-hex string is normalized into the standard 8-4-4-4-12 form.

Is the timestamp exact?

We extract the embedded millisecond value. Order within the same millisecond can’t be reconstructed, so treat it as an estimate.

Is uniqueness guaranteed?

UUIDs are designed to make collisions extremely unlikely, but not mathematically impossible. Design accordingly for your use case.

References (RFC)

  1. RFC 9562 §5.7 (UUIDv7 structure)
  2. RFC 9562 §4 (string format / ABNF)
  3. RFC 9562 §4.1 (Variant)
  4. RFC 9562 §4.2 (Version)

These links are generated from site_map rules in recommended diagnostic order.

  1. UUIDv7 Range Builder — Build UUIDv7 range boundaries from start/end milliseconds
  2. UUIDv7 from Timestamp — Create UUIDv7 boundary values (earliest/random/latest) from Unix ms
  3. UUIDv7 Generator — Generate/validate UUIDv7 and extract time-derived fields

Example

0193f0c0-2a2b-7b9d-b5a9-2a6e0c7b3a8e