Runs locally in your browser. Nothing you enter is uploaded to our servers.
Result will appear here
Tips for UUIDs
UUID v4 is random — fine for IDs, not for secrets alone.
Do not treat UUIDs as unguessable auth tokens.
Keep a consistent string format (with/without hyphens) in APIs.
Generate server-side when uniqueness must be authoritative.
Avoid embedding meaning inside UUID fields.
UUIDs for ids, not for secrets
Processing stays in your browser — your input is not uploaded to our servers.
A UUID is a 128-bit identifier. This generator mints new values in the browser so you can fill fixtures, primary keys, and request ids.
Do not treat a UUID as a password or a capability token unless the system is designed that way — they are unique, not automatically confidential.
Generate a UUID
Create one or more ids
Each click should yield a new value. Do not hand-edit characters to “make it unique”.
Copy the canonical form
Most APIs want lowercase hex with hyphens. Match the consumer’s expected version if it checks.
Paste into the fixture
Use a different UUID per entity so tests do not collide.
UUID generator FAQ
Can two browsers generate the same UUID?
Collision is astronomically unlikely for v4 random UUIDs. Still do not use them as proof of identity.
Is a UUID a secret?
No. If it appears in URLs or logs, assume it can leak. Use a real token for authorization.
Which version is this?
The tool generates random (v4-style) ids in the browser — not time-based v1 MAC addresses.