What a version 4 UUID contains

A standard UUID is 128 bits displayed as 32 hexadecimal characters in five groups. Version 4 reserves specific bits for the version and variant, leaving 122 random bits. In the familiar text form, the first character of the third group is 4 and the first character of the fourth group is 8, 9, a, or b.

Random does not mean mathematically impossible to collide

The identifier space is extremely large, so collisions are unlikely when UUIDs are generated correctly, but uniqueness is probabilistic rather than guaranteed by a central registry. Systems that require a strict database invariant should still enforce a unique constraint and handle a conflict.

Formatting does not change the underlying identifier

Uppercase versus lowercase hexadecimal has the same numeric value. Removing hyphens creates a compact 32-character representation, but some libraries, database types, validators, or APIs require the standard hyphenated form. Confirm the consumer’s accepted syntax.

UUIDs are identifiers, not secrets

A random UUID can make casual guessing difficult but is not a substitute for an authentication token, access-control check, password, encryption key, or session design. Do not grant access merely because someone knows an identifier.

Generation stays in this browser

The tool uses crypto.randomUUID(), which is available only in supported secure browser contexts. Generated values are displayed locally and are not intentionally transmitted by Gypes. Clear them when using a shared device.

Use UUIDs according to the schema and security requirements of the destination system. This tool does not reserve identifiers, check them against a database, guarantee global uniqueness, or make them suitable as credentials.