JWT Decoder
Decode and debug JSON Web Tokens, see when they expire, and verify HS, RS, PS, ES, and EdDSA signatures.
Generate v4, v7, v1, v5, and v3 UUIDs / GUIDs in bulk, and inspect any UUID. Free, private, and 100% in your browser.
v4 (random): 122 random bits. The most widely used UUID.
A UUID (universally unique identifier), also called a GUID, is a 128-bit value that can be created independently on any machine with practically no chance of a duplicate. That makes UUIDs ideal for database keys, request and correlation IDs, file names, and distributed systems. They are defined in RFC 9562, which replaced RFC 4122 in 2024 and added versions 6, 7, and 8.
0190f2a4-6b3e-7c12-9f4d-2b8e1a7c5d30
^ ^
version variant (8, 9, a, or b)v4 (random), v7 (time-ordered), v1 (time-based), and name-based v5 (SHA-1) and v3 (MD5).
Generate 1 to 10,000 UUIDs at once, then copy them all or download a .txt file.
Switch to uppercase, remove hyphens, or wrap in braces for Microsoft-style GUIDs.
Paste any UUID to check it and see its version, variant, and creation time for v1, v6, and v7.
Random bits come from the browser's crypto.getRandomValues, not Math.random.
UUIDs are generated on your device. Nothing is requested from or sent to a server.
v4 is fully random and the most common choice. v7 stores a Unix millisecond timestamp in its first 48 bits, so values sort by creation time, which keeps B-tree indexes in PostgreSQL and MySQL compact. v1 uses a 100-nanosecond Gregorian timestamp. v5 and v3 are deterministic and derived from a namespace and a name.
Use v4 when you just need a unique random ID. Use v7 for database primary keys: it starts with a timestamp, so new rows are inserted in order and indexes stay efficient. Use v5 when the same input must always produce the same UUID. v1 and v3 are mainly for compatibility with older systems.
None in practice. GUID (globally unique identifier) is Microsoft's name for a UUID. GUIDs are often written in uppercase and wrapped in braces, like {3F2504E0-4F89-11D3-9A0C-0305E82C3301}. Enable Uppercase and Braces to get that format.
In theory, yes; in practice, no. A v4 UUID has 122 random bits. You would need to generate about a billion UUIDs per second for around 86 years to reach a 50% chance of a single collision.
No. Browsers cannot read your MAC address, and this tool uses a random node ID with the multicast bit set, as RFC 9562 recommends. v1 UUIDs do reveal their creation time, though.
They hash a namespace UUID together with a name (SHA-1 for v5, MD5 for v3). The same namespace and name always produce the same UUID, which is useful for stable IDs derived from URLs, domain names, or other keys. Enter one name per line to generate several at once.
No. Every UUID is created in your browser with the Web Crypto API. Nothing is sent to or stored on a server.
Decode and debug JSON Web Tokens, see when they expire, and verify HS, RS, PS, ES, and EdDSA signatures.
Create and sign JSON Web Tokens with HS256, RS256, ES256, PS256, or EdDSA, and generate test key pairs.
Generate MD5, SHA-1, SHA-256, SHA-384, and SHA-512 hashes and HMACs of text or files, live as you type.
Hash passwords with bcrypt at any cost factor and verify a password against an existing bcrypt hash.