Pages

Topics

Tools

↑↓navigate↵openescclose
Time, Text & CSS

UUID Generator

Generate UUID v4, time-ordered UUID v7, ULID or NanoID, format one to a hundred of them as lines, JSON or a SQL IN list, download the batch as .txt, .json or .sql, and break any UUID or ULID into its version, variant, embedded timestamp and BINARY(16) bytes.

Runs entirely in your browser — nothing you paste is uploaded.

UUID reference

quick reference
8-4-4-4-12
The canonical 36-character form with hyphens; the bare hex form is 32 characters.
v4
122 random bits, so collisions are practically impossible without coordination.
v7
Time-ordered UUIDs that sort by creation time and keep database indexes compact.
00000000-0000-0000-0000-000000000000
The nil UUID, used as an explicit empty value.
gen_random_uuid()
PostgreSQL 13+ function for a server-side default; MySQL uses UUID().
not a secret
A UUID is unpredictable in practice but not a token — never use it as an API key.

Frequently asked questions

answered below the tool
Are these UUIDs random?

Version 4 is: 122 random bits from the browser's cryptographic source, so collisions are not a practical concern. Version 7 and ULID mix a millisecond timestamp with randomness instead.

Should I use UUID v7 or a ULID as a primary key?

Both sort by creation time, so inserts stay at the end of the index instead of scattering across it. v7 is a 16-byte UUID that a UUID column takes as it is; a ULID is 26 characters of text with the same ordering.

How do I store a UUID in MySQL?

In BINARY(16) with UNHEX() or the X'…' literal the inspector shows. CHAR(36) costs more space and a wider index for the same value.

All SQL guides