Primary keys for databases
Adopt UUID v7 when you need monotonic ordering that keeps B-Tree indexes healthy, especially in PostgreSQL or MySQL installations that struggle with random inserts.
Generate UUID versions 4 and 7 instantly.
UUID Forge focuses on canonical UUID generation so you can mint request identifiers, distributed database keys, and tracing IDs without leaving the console. It supports both random UUID v4 and time-ordered UUID v7, covering modern storage and observability workflows.
Adopt UUID v7 when you need monotonic ordering that keeps B-Tree indexes healthy, especially in PostgreSQL or MySQL installations that struggle with random inserts.
Assign UUID v4 identifiers to API requests, background jobs, or telemetry spans so you can correlate logs and metrics across services while avoiding guessable patterns.
Use the tool to pre-generate ID batches for demos, fixtures, or import scripts when the environment you are deploying to lacks a UUID utility.
Pick v4 for purely random identifiers or v7 for high-cardinality data that benefits from natural ordering and lower index fragmentation.
Press “Generate” to mint a new identifier. Each run uses cryptographically secure randomness and respects the version-specific bit layout.
Copy the UUID to seed databases, include in API calls, or paste into documentation. Regenerate whenever you need an additional value.
Choose UUID v7 when you need insertion order correlation (such as log streams or append-only tables). Stick with v4 when you require identifiers that reveal no timing information.
Increase the quantity above 1 to emit multiple identifiers in one run. Each UUID is placed on its own line for easy copying or downstream processing.
Yes. UUID Forge relies on the Web Crypto API when available and falls back to high-quality randomness logic, making the output safe for production identifiers.