Generate random UUID v4 identifiers straight from crypto.randomUUID. RFC 4122 compliant, one or many at once. All in your browser, nothing sent anywhere.
A universally unique identifier (UUID) version 4 is a 128-bit identifier generated from random numbers. Unlike v1 or v6, it contains no timestamp or MAC address — just 122 bits of randomness. Use them for database primary keys, correlation IDs, or anywhere you need a unique identifier without a central authority.
Because it runs entirely in your browser. The UUIDs come from crypto.randomUUID, the standard Web API for RFC 4122 identifiers. Nothing is logged, uploaded, or transmitted. Generate one UUID or fifty at a time, copy them with a click, and paste them straight into your code or database.
A UUID v4 looks like f47ac10b-58cc-4372-a567-0e02b2c3d479. It’s a 36-character string with five groups separated by hyphens: 8-4-4-4-12 hexadecimal digits. The 13th digit is always “4” (the version), and the 17th digit is one of 8, 9, a, or b (the variant).
A UUID v4 (version 4) is a 128-bit identifier generated from random numbers, following RFC 4122. Unlike UUID v1 which uses a timestamp and MAC address, a v4 UUID is almost entirely random — 122 of the 128 bits come from a cryptographically-secure random source.
Select 'UUID v4' as the type, choose how many you need (1 to 50), and click Generate. Each identifier comes from crypto.randomUUID, the built-in browser API, and you can copy individual UUIDs or all of them at once.
Yes. Set the 'How many' field to any number between 1 and 50. All UUIDs are generated in a single click and displayed in a list you can copy individually or as a batch.
Yes. They come from crypto.randomUUID which uses the browser's cryptographically-secure random number generator, the same source used for TLS and encryption.
UUID v4 is purely random — no timestamp, no MAC address, no namespace. UUID v1 uses the host's MAC and clock; v3 and v5 hash a namespace and name; v6 and v7 are newer ordered-UUID proposals. For most web applications where you need a unique key without exposing metadata, v4 is the standard choice.
Yes. Generate as many UUIDs as you like, with no sign-in and no limits.
Generate cryptographically-random hex strings from the Web Crypto API. Choose the byte length, optio
Generate cryptographically-random Base64URL tokens from the Web Crypto API. URL-safe, no padding, gr
Generate random alphanumeric API keys and secrets. Set a custom prefix to match your service's forma
Generate a 64-byte (512-bit) cryptographic secret as hex. Use it for Django SECRET_KEY, Rails secret
Spotted a bug, want a feature, or just have feedback on KeyForge? Send us a note and we will get back to you.
Prefer to talk it through? Book a 30-min call →