UUID v4 generator
RFC 4122-compliant UUID v4 identifiers, generated locally using the platform CSPRNG. Click anything to copy it.
What is a UUID v4?
A UUID v4 is a 128-bit random identifier defined by RFC 4122. Out of those 128 bits, 122 are random and 6 are fixed to encode the version (4) and variant. The collision probability is so low that you can treat them as effectively unique forever.
Where UUIDs are useful
- Primary keys for distributed databases (no central allocator needed).
- Idempotency keys for HTTP requests.
- Correlation IDs in microservices and logs.
- Filenames for user uploads that mustn't collide.
- Anonymous client identifiers in analytics.
UUID v4 via API
Need to generate UUIDs from a server (or a language that doesn't ship a CSPRNG-backed UUID library)? Use the Oxide Hash & Encryption Toolkit /v1/token endpoint.
curl -X POST https://hash-toolkit1.p.rapidapi.com/v1/token \
-H "Content-Type: application/json" \
-H "X-RapidAPI-Key: YOUR_KEY" \
-H "X-RapidAPI-Host: hash-toolkit1.p.rapidapi.com" \
-d '{"type":"uuid"}'FAQ
What is a UUID v4?
A UUID v4 is a 128-bit random identifier defined by RFC 4122. Out of those 128 bits, 122 are random and 6 are fixed to encode the version (4) and variant. The collision probability is so low that you can treat them as effectively unique forever.
Is this UUID generator cryptographically secure?
Yes. We use the browser's built-in window.crypto.randomUUID() (or crypto.getRandomValues as a fallback), both of which draw from the platform CSPRNG. No PRNG, no Math.random, no server round-trip.
How many UUID v4s can I generate before risking a collision?
In practical terms, you would have to generate ~2.71 quintillion UUIDs to have a 50% chance of one collision. For any reasonable application this is essentially zero.
Can I generate UUIDs from an API instead of the browser?
Yes — the Oxide Hash & Encryption Toolkit /v1/token endpoint returns RFC 4122 UUIDs (and hex / base64 tokens) at the network edge.