About uniqueid.tech

Whether you're a developer building a new system, a data engineer cleaning up a spreadsheet, or someone who just needs a one-off random ID for a form, this site exists to hand you one — quickly, correctly, and without the usual catch.

That catch, on most ID-generator sites, is that the value you're trusting them to make for you is also being handed to them. A server somewhere has seen every ID it sent out, who asked for it, and when. For something whose entire job is to be unique and uncorrelated, that's a strange trade.

uniqueid.tech doesn't make that trade. There is no server that generates IDs and no log of what you produce. Everything you see on the screen is created inside your own browser by code that has already been downloaded to your machine. After your first visit, the entire site is cached as a Progressive Web App and continues to work with no internet connection at all.

See for yourself

"It all runs in your browser" is the sort of claim that's easy to make and worth verifying, especially since this site isn't open source. You can do it in under a minute:

1. Open your browser's developer tools — F12 on Windows and Linux, ⌥⌘I on macOS.
2. Switch to the Network panel and clear any existing entries.
3. Click any Generate button on any generator page.

You'll see no network requests fire. The IDs are produced by the WebAssembly module that is already loaded in the tab; the only time this site contacts a server is when you load a new page, and even then only to fetch static files.

Correctness

A unique ID generator's output is the part most worth getting right, so the generators here are written to the relevant standards rather than to whatever looked easiest. UUID generation follows the byte layouts and bit assignments defined by RFC 9562, the current UUID standard that superseded RFC 4122 in 2024. The v3 and v5 implementations are tested against the RFC's published test vectors; v6 and v7 are tested to confirm the version and variant bits land in the right places. ULIDs are tested for monotonicity within the same millisecond and lexicographic sortability across them, and NanoID for correct alphabet usage and length.

Where .NET's standard libraries have gotchas, the generators take the longer code path to produce correct output rather than the more obvious one that doesn't. The clearest example is the byte-order pitfall around Guid.ToByteArray() and UUID v7 — a problem easy to introduce and hard to spot, which this site treats as a worked example rather than a footnote.

Who runs this site

uniqueid.tech is built and maintained by an independent developer based in New Zealand — one person, not a company or content farm. It started as a personal tool and grew into the public version you're using now. There's no team, no venture funding, and no data-collection business model behind it; the only revenue is the advertising described below.

The fastest way to reach a human is the contact page. Bug reports, corrections, and feature requests are all welcome.

How the site stays free

uniqueid.tech is paid for by Google AdSense ads, with visit counts measured by Google Analytics 4. Both load only after you accept the cookie banner, and rejecting the banner doesn't disable any generator or article on the site.

Neither AdSense nor Analytics sees the IDs you generate or the inputs you type into the generators — those are processed inside the WebAssembly module and never leave your browser. Full detail on what's loaded, what's stored, and how to opt out is in the privacy policy.