Generate RFC 4122 & RFC 9562 compliant UUIDs
Validate and inspect UUID format
UUIDv1: Time-based with MAC address. Sortable by creation time but reveals hardware info. Legacy use cases only.
UUIDv4: Random. Best for general use - IDs, tokens, session keys. No information leakage. Industry standard.
UUIDv7: Time-ordered random. Best for database primary keys. Combines v4 randomness with v1 sortability. Improves index performance.
Standard: 8-4-4-4-12 with hyphens (550e8400-e29b-41d4-a716-446655440000). Most compatible.
Compact: No hyphens (550e8400e29b41d4a716446655440000). Saves 4 characters.
Base64: URL-safe, shorter (VQ6EAOKbQdSnFkRmVUQAAA). Best for URLs and APIs.
1. Bulk Mode: Generate 1-100 UUIDs at once for batch operations, database seeding, or testing.
2. Copy Results: Click individual UUIDs to copy, or use "Copy All" for bulk clipboard export.
All UUIDs comply with RFC 4122/9562. Collision probability effectively zero. Safe for distributed systems without coordination.
UUIDv4 (random) is best for most cases - IDs, database keys, session tokens. UUIDv7 (time-ordered) is ideal for database primary keys as it improves index performance. UUIDv1 includes MAC address (privacy concern). UUIDv5 creates deterministic UUIDs from names.
UUIDv4 has a collision probability so low it's effectively zero (1 in 2^122). You could generate a billion UUIDs per second for 100 years and still have less than 50% chance of one collision. For practical purposes, they're unique.
Yes, but consider UUIDv7 for better performance. UUIDv4 causes index fragmentation due to randomness. UUIDv7 is time-ordered, providing UUID benefits (globally unique, no coordination needed) while maintaining good database index performance.
Standard format uses hyphens (8-4-4-4-12): "550e8400-e29b-41d4-a716-446655440000". Compact removes hyphens. Base64 is URL-safe and shorter. All represent the same 128-bit value, just different representations.