UUID Generator
Generate UUIDs for apps, tests, and databases.
- On your device
- No signup
A UUID generator creates random unique identifiers (v4) for databases, APIs, and test data. IDs are generated locally in your browser.
Private on your device
Your information stays on your device and is not uploaded.
Generate UUIDs for apps, tests, and databases.
Service UUID lookup: inspect version, variant, and embedded timestamps.
Generate strong, secure random passwords with customizable length and character sets.
Format, minify, and validate JSON with optional key sorting.
Compare two JSON documents and instantly see added, removed, and changed values. JSON mode highlights changed keys with path hints.
Format, minify, and validate XML with readable indentation.
Compare two XML documents and see tag, attribute, and text line changes.
Compare source files such as JavaScript, TypeScript, Java, Python, HTML, CSS, and SQL.
This UUID v1 generator creates time-based RFC 4122 version 1 identifiers embedding timestamp and node components. Use when you need roughly time-ordered IDs for logs or legacy systems—prefer v4 for pure randomness or v7 for modern sortable IDs.
UUID v1 includes timestamp information—IDs sort roughly by creation time but may expose clock details.
Privacy-sensitive apps often prefer random v4 or sortable v7 over v1 node-based patterns.
Select version 1 if offered on the base tool, generate UUIDs, and copy for your application or database seed.
Example: generate v1 UUIDs for a legacy Java service that expects time-ordered keys in an audit log table.
Generates UUID v4 (random) or v7 (time-ordered) identifiers using crypto-random bytes on your device. Supports bulk generation with optional uppercase and hyphen formatting.
Results are based on the inputs you provide and may not cover every edge case. This tool is for general use and is not professional advice.
Your data stays on your device and is not uploaded.
These pages use the same uuid generator with examples tailored to different tasks.
FAQ
v1 is time-based with node bits; v4 is fully random.
Designed to be unique when clock and node are configured correctly—still use proper generation libraries in prod.
Many teams prefer v4 for privacy or v7 for sortable IDs—match your platform requirements.
Page last reviewed: