UUID Format

UUID With Hyphens

The hyphenated 36-character form is the canonical presentation — what every validator expects and what you should use whenever interoperability matters.

36 characters8-4-4-4-12 layoutUniversally accepted

Version

How many

Uppercase Hyphens Braces { }

Result

Generated locally with the Web Crypto API — nothing leaves your browser.

What Is UUID With Hyphens?

The hyphens mark the field boundaries of the UUID layout, so the string visually communicates time_low / time_mid / version / variant / node.
This is the form produced by crypto.randomUUID() and by the toString() method of essentially every UUID library in every language.

How to generate

Leave the Hyphens toggle on (the default).
Pick a version and generate.
Paste anywhere — every validator accepts the canonical form.

Use Cases

Interoperability with third-party APIs that validate the shape strictly.
Configuration files where the grouped form is easier to read aloud.
Documentation and tickets, since the grouped form is easier to scan.

How UUID With Hyphens Compares

Canonical	36 chars with 8-4-4-4-12 grouping
Raw	32 chars, no grouping
Braced	38 chars, wrapped in { }

Code Examples

JavaScript

const id = crypto.randomUUID(); // canonical, hyphens included

PostgreSQL

SELECT gen_random_uuid();  -- prints with hyphens

Frequently Asked Questions

Why does the length include hyphens?

The canonical length of 36 counts the four hyphen characters; the payload is 32 hex digits.

Do hyphens affect sorting?

Lexicographic sorting of the canonical form matches sorting of the raw form, since hyphens occur at fixed positions.