🚀 Quick Start

Choose version: prefer v4 (random); consider v1 only when approximate time ordering is needed
Set count: drag the slider to choose 1–100
Format: toggle uppercase/dashes for readability or compact form
Generate & export: click Generate, then Copy All or Download .txt

📌 Common Scenarios

🎛️ Version & Format Parameters

v1: time semantics + node identifier; roughly sortable by time
v4: strong randomness; suitable for most scenarios
Presentation: case and dashes only affect display/storage; comparisons are case‑insensitive

🧭 Usage Advice

General recommendation: prefer v4 in production to avoid time semantics
Storage convention: database fields use lowercase without dashes; logs/display use lowercase with dashes
Idempotency & tracing: use v4 for idempotency keys and tracing; standardize the string format
Batch imports: pre‑generate and verify a list for migrations/initialization

⚠️ Limitations & Compatibility

Batch limit: up to 100 per generation
Version support: currently v1 and v4
Cross‑language differences: serialization may vary (case/dashes); standardize within your team

🔒 Privacy & Security

❓ FAQ

What is a UUID?

A 128‑bit globally unique identifier. Standard format: 32 hex characters grouped as 8‑4‑4‑4‑12. Common versions: v1 (time semantics) and v4 (random)

Should I choose UUID v1 or v4?

v4 is recommended. v1 offers rough time ordering but carries time semantics; v4 has strong randomness and suits most scenarios

Will UUIDs collide?

Collisions are negligible for typical use. For cross‑system strong uniqueness, add business‑level deduplication/constraints

Does case matter?

Semantically identical. Case-insensitive when comparing, but keep consistent within your team

Are dashes required?

Not required. Dashes improve readability, while no dashes work better for URLs and compact storage

Can I use UUID as a password?

No. UUIDs are identifiers, not secrets. Use proper key generation methods for passwords