Skip to content
World Cup Kickoff Time Converter is liveSee kickoff times in your time zone and add calendar reminders.

UUID Generator

UUID Generator creates v1, v4, and v7 identifiers in batches with casing, hyphen, copy, and TXT download options for database IDs, idempotency keys, and trace IDs.

UUID Version

Count

1 / 100

Format Options

Uppercase letters

Include dashes

UUID Generator

Quick Start

1
Choose version: v7 is the default for time-ordered IDs; use v4 for pure randomness and v1 only for legacy timestamp semantics
2
Format: toggle uppercase/dashes for readability or compact form
3
Generate, then copy one/all or download a .txt list

Common Scenarios

Database UUID columns and test primary keys, with database uniqueness constraints still required

API idempotency keys and request deduplication identifiers

Logging/events/trace IDs

Version & Format Parameters

v1: timestamp semantics + random node identifier; do not rely on it as an authoritative creation-time record or sortable key
v4: random identifier; generated with the uuid library using modern crypto random values
v7: Unix Epoch time-ordered UUID; useful for database indexes and logs, but not an authoritative creation-time record
Presentation: case and dashes only affect display/storage; comparisons are case‑insensitive

📦 Batch & Export

Display: only the current batch is shown with timestamps
One-click actions: copy one/all or download a .txt file.
Result metadata: each row shows its UUID version and generation time

UUID Generation Boundaries

This tool generates UUID v1, v4, and v7 only; it does not provide v3/v5/v6/v8, Nil/Max UUIDs, namespace generation, validation, or decoding.
v4 output is suitable for identifiers, not passwords, API keys, auth tokens, or other secrets.
v7 output is roughly time-ordered, but formatting options do not turn UUIDs into secrets or business guarantees.
v1 output carries timestamp semantics and a random node identifier; prefer v7 or v4 unless you intentionally need that legacy timestamp-style behavior.
Uppercase and hyphens change string presentation only; normalize the format before comparing or storing UUIDs across systems.

Usage Advice

General recommendation: use v7 for sortable production identifiers, v4 for random identifiers, and v1 only when legacy timestamp semantics are deliberate
Storage convention: database fields use lowercase without dashes; logs/display use lowercase with dashes
Idempotency & tracing: use v7 or v4 for idempotency and tracing identifiers; UUIDs are not authentication tokens or secrets
Batch imports: pre‑generate and verify a list for migrations/initialization

Limitations & Compatibility

Version support: currently v1, v4, and v7 only; no v3/v5/v6/v8, Nil/Max, namespace UUID, validator, or decoder
Cross‑language differences: serialization may vary (case/dashes); standardize within your team

Privacy & Security

UUIDs are generated in your browser. Generated results are not sent to CrateX.app, and local settings can be cleared or reset.
Privacy note: v1 and v7 carry timestamp semantics; v1 uses a random node identifier and does not expose a real MAC address

FAQ

5

Continue with these related tools for the next step.

All tool processing happens locally in your browser.