Always reading

Let's talk

Found a bug? Have a feature idea? Curious about UUID internals? Fill out the form below and we'll get back to you within 48 hours.

Send a Message

Please enter your name.
Please enter a valid email address.
Please enter a subject.
Please write a message (at least 20 characters).
You must accept the Privacy Policy to continue.
We respond within 48 h

Message sent!

Thanks for reaching out. We'll reply to your inbox within 48 hours.
In the meantime, feel free to keep generating UUIDs.

Frequently Asked Questions

No. All UUID generation happens inside your browser using the Web Crypto API. Nothing is ever sent to our servers — not the UUIDs you generate, not the name strings you enter for v5, not the count you request for bulk export. We have no technical means to see your UUIDs because they never leave your device.
For v4 UUIDs, yes. We use crypto.getRandomValues(), which is the browser's CSPRNG (Cryptographically Secure Pseudo-Random Number Generator) — the same entropy source used for TLS key generation. UUID v1 is time-based and therefore not cryptographically opaque; UUID v5 is deterministic by design.
Yes. UUIDForge is released under the MIT License. You can inspect the source, self-host it, fork it, and embed it in your own projects. If you improve it, pull requests are welcome.
It's on the roadmap. A GET /api/v4 and GET /api/bulk?count=N endpoint backed by FastAPI is planned for a future release. Use the Contact form to register your interest and help us prioritise it.
UUID v1 encodes a 60-bit timestamp (100-nanosecond intervals since 15 October 1582) in its first three fields. Anyone who decodes the UUID can extract the approximate creation time. For most database-key use cases this is harmless, but if creation time is sensitive data, prefer v4 (random) or v5 (deterministic from a secret name) instead.