Give each record its own identifier
When building fixtures or manually preparing a few records, a distinct identifier makes references easier to follow. The UUID Generator creates version 4 UUIDs with the browser’s crypto.randomUUID() method. You can request from 1 to 100 values in one operation, with one identifier returned per line.
Version 4 means the identifier’s variable bits come from random generation. It does not include a meaningful creation date, ordering sequence, or project name. Keep those attributes in separate fields if your application needs them. Sorting randomly generated UUIDs should not be used as a replacement for sorting a timestamp column.
Inspect a three-record batch
Set How many UUIDs? to 3 and process the input. The expected result is three lines using the familiar 8-4-4-4-12 hexadecimal grouping:
xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxxThis line is a format diagram rather than an identifier to copy. In an actual result, every x is a hexadecimal digit, and the first digit of the third group is 4. The variant position represented by y is one of 8, 9, a, or b. Your generated lines will differ from someone else’s and from your next batch.
Assign one line to each sample record. If you paste the values into JSON, surround them with quotes because a UUID is a string. JSON Formatter can help check that the fixture remains syntactically valid after editing.
Preserve uniqueness where records are stored
Cryptographic randomness makes accidental collisions unlikely, but a generator is not a database constraint. Your application should still enforce uniqueness for primary keys and handle an insertion conflict. It should also prevent accidental reuse when someone copies an existing fixture and forgets to replace its identifier.
The browser’s implementation supplies the randomness; the tool does not maintain a central registry of every UUID ever created. The Web Cryptography specification documents randomUUID alongside the browser random-value interface. A supported secure browser context is necessary for this API to be available.
Keep identifiers and secrets distinct
Generation happens in the browser, without submitting the resulting values to an ERITHRA processing service. UUIDs frequently become visible in URLs, logs, and exports. Do not grant access merely because someone knows a record identifier. Use normal authorization checks, and use Password Generator when your task actually requires a secret password rather than a public reference value.