Generate v1/v4 UUIDs, parse timestamps and node information
🎲UUID GeneratorReady
Click "Generate UUID" to create a new UUID
📦 Bulk Generated UUIDs
🔍UUID InspectorNo UUID
🔍 UUID Analysis
💡 Sample UUIDs
Try these examples to test the inspector:
About UUID Generator & Inspector
Our free online UUID generator and inspector helps developers create and analyze Universally Unique Identifiers. Whether you're generating IDs for databases, APIs, or applications, our tool provides comprehensive UUID generation and analysis capabilities.
Features
UUID v4 Generation: Generate cryptographically secure random UUIDs
UUID v1 Generation: Generate time-based UUIDs with node information
Bulk Generation: Generate multiple UUIDs at once
UUID Inspection: Parse and analyze UUID components
Timestamp Analysis: Extract creation time from v1 UUIDs
Node Information: Display node and clock sequence data
Multiple Formats: Support for standard, simple, and braces formats
Copy as Array: Export UUIDs as JSON arrays
How to Use
Choose UUID version (v1 or v4) and format
Click "Generate UUID" for single generation or "Generate Bulk" for multiple
Paste UUIDs in the inspector to analyze their components
Review timestamp, node, and version information
Copy results for use in your applications
Common Use Cases
✅ Database IDs: Generate unique identifiers for database records
✅ API Development: Create unique resource identifiers
✅ File Naming: Generate unique file names
✅ Session IDs: Create unique session identifiers
✅ Debugging: Analyze UUID structure and timestamps
About this tool
Free Online UUID Generator
Generate UUID v4 identifiers instantly in your browser. Generate one or a batch of up to 100 at once. All UUIDs are generated using crypto.randomUUID() — the browser's cryptographically secure random source. Nothing is uploaded or stored.
What is a UUID?
A UUID (Universally Unique Identifier) is a 128-bit identifier formatted as 32 hexadecimal digits in five groups: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Defined by RFC 4122, UUIDs are designed to be globally unique without requiring a central authority — any machine can generate one independently.
UUID v4 vs v1 vs v7
v4 (random) — 122 bits of cryptographic randomness. No information about when or where it was generated. Best for most use cases
v1 (time-based) — encodes the current timestamp and the machine's MAC address. Sortable by creation time but leaks information about the generating machine
v7 (new — RFC 9562) — embeds a millisecond-precision Unix timestamp in the high bits, making it sortable like v1 but using random data instead of MAC address. Recommended for use as database primary keys
When to Use UUIDs vs Auto-Increment IDs
Use UUIDs when: multiple services or clients generate IDs independently, you need to merge data from multiple databases without conflicts, or you want opaque IDs that don't reveal total record counts. Use auto-increment integers for simple single-database apps where sequential IDs are acceptable — they are smaller (4–8 bytes vs 16 bytes) and have better B-tree index performance.
Can two UUIDs ever be the same?
In theory yes, in practice no. UUID v4 has 2122 possible values. Generating 1 billion UUIDs per second for 85 years gives a 50% chance of one collision. For any real application, UUID collisions are not a concern.
What is the difference between UUID and GUID?
They are the same thing. GUID (Globally Unique Identifier) is Microsoft's name for the same 128-bit format. UUID is used in open standards and most languages; GUID is used in Windows, .NET, and SQL Server.
How should I store UUIDs in a database?
PostgreSQL has a native UUID type — use it. MySQL/MariaDB: use BINARY(16) with UUID_TO_BIN() for best performance, or CHAR(36) for readability. SQLite: store as TEXT or BLOB. Storing as a string in MySQL with random UUIDs causes write amplification in InnoDB — consider UUIDv7 or ordered UUIDs.