Generate, format, export, and parse RFC 4122 / RFC 9562 Universally Unique Identifiers (v1, v3, v4, v5, v7, Nil, Max).
Quick Presets:
Name-based Namespace Configuration
Ready to generate a UUID.
Ready to generate batch.
Enter a UUID above to analyze its version, timestamp, variant, and byte representations.
UUID Analysis Breakdown
Canonical Format-
Uppercase Format-
Detected Version-
Variant Standard-
Extracted Timestamp (UTC & Local)-
Clock Sequence & Node MAC-
Base64 Representation-
Base58 (Bitcoin / Short UUID)-
BigInt Integer Representation-
Hex Byte Array-
Universally Unique Identifier (UUID) Overview
A UUID (Universally Unique Identifier) is a 128-bit number used to uniquely identify information in computer systems without requiring a central registration authority.
Distributed legacy systems requiring timestamp tracking
Partially
v3
MD5 Name & Namespace Hash
Deterministic identifier generation from text/names
No
v5
SHA-1 Name & Namespace Hash
Deterministic identifier generation (preferred over v3)
No
Online RFC 4122 & RFC 9562 UUID Generator
Generate secure version 4 random UUIDs, time-sortable version 7 UUIDs, or name-based version 3 & 5 UUIDs instantly. Features high-performance client-side generation, batch generation up to 1000 items, custom syntax code exporting (JSON, SQL, CSV, C#, Java), and a deep UUID structure inspector.
Frequently Asked Questions
Why is UUID v7 recommended for database primary keys?
UUID v7 incorporates a 48-bit millisecond Unix timestamp at the beginning of the identifier. This guarantees chronological sorting order, preventing B-Tree index fragmentation in databases like PostgreSQL, MySQL, and SQLite while keeping collision risk virtually zero.
Are generated UUIDs secure?
Yes. All Version 4 and Version 7 UUIDs are generated in your browser using Web Cryptography crypto.getRandomValues() API, ensuring cryptographic randomness without sending data to external servers.
What is the probability of a UUID collision?
For Version 4 UUIDs, the probability of generating a duplicate is approximately 1 in 2122 (or 5.3 x 1036). You would need to generate 1 billion UUIDs every second for 85 years before having a 50% chance of a single collision.