How to use this tool
- Choose the identifier format.
- Set a batch size; for NanoID, select length and alphabet.
- Generate and export newline text, JSON or CSV.
Put a UUID into a JSON fixture
Export an identifier as JSON for an API fixture. This public example shows the shape, not a credential.
Input
UUID v4 · JSON export Example ID: f47ac10b-58cc-4372-a567-0e02b2c3d479
Expected output
[ "f47ac10b-58cc-4372-a567-0e02b2c3d479" ]
The third group starts with 4 and the fourth group carries the RFC variant. Fresh generated values differ. UUID v7 embeds creation time, while NanoID uses a configurable random alphabet; none replaces access control.
More examples
- UUID v4 contains a version-4 nibble and the RFC variant.
- UUID v7 embeds a millisecond timestamp; it reveals approximate creation time.
- A 21-character URL alphabet NanoID has 64 possible symbols per position.
Know the limits
Uniqueness is probabilistic. Use database uniqueness constraints where required. Identifiers, especially time-bearing ones, are not a substitute for authorization.
Common questions
Which format sorts by time?
UUID v7 includes time in the high bits; follow your database’s UUID comparison behavior.
Are short NanoIDs secure secrets?
Short lengths reduce the search space. Use the secret generator for credentials.