Every version worth having
v4 random, v1 timestamp-based, v7 time-ordered so it sorts lexicographically and makes a decent database key, plus the NIL and MAX constants.
Generate and copy UUIDs in one click.
Open the popup and a UUID is already there. Click it and it is on your clipboard. That is the whole product.
v1 · v4 · v7 · NIL · MAX One permission Zero network requests 17.6 kB
Add to Chrome Build it from source Free, MIT-licensed, Chrome for now.
uuidly
live, right here
—
Format
What it does
Nothing between you and the value
A UUID is on screen the instant the popup paints — generated before the UI mounts, not after. Click the value or the icon to copy exactly what you see.
Bulk, with a real CSV
Up to 100 at a time. Copy as text or JSON, or download a CSV with proper RFC 4180 quoting and a UTF-8 BOM, so Excel opens it without mangling anything.
Shaped for where it is going
Uppercase, hyphens on or off, and {braces},
"quotes" or urn:uuid:. Formatting never
regenerates the value.
Keyboard the whole way
1–5 pick a version, R refreshes, C copies, B opens bulk, Esc closes. Works with the mouse unplugged.
Small enough to audit
17.6 kB of JavaScript and two runtime dependencies. No background worker, no content scripts, no analytics.
What it does not do
These are not promises in a privacy policy. Each one fails the build if it stops being true.
-
One permission:
storage. It remembers your chosen version and formatting. There is nothing else in the manifest. -
No network requests, ever. A build-time check rejects the
bundle if
fetch,XMLHttpRequestorWebSocketappears anywhere in it. - No host permissions, no content scripts. The extension cannot read or change any page you visit.
- Your MAC address is never read. v1 uses a random node id, and a test asserts the multicast bit that proves it.
- No analytics, no telemetry, no remote code.
Questions
Which version should I use?
v4 unless you have a reason. Use v7 for database keys — it sorts by creation time, which keeps index inserts local instead of scattering them. Use v1 only for compatibility with something that already expects it.
Are these safe to use as secrets?
No. UUIDs are identifiers, not secrets. v1 and v7 encode their creation time and are guessable in that dimension; v4 is random but still not a substitute for a purpose-built token. Do not use them as passwords, session tokens or API keys.
Firefox? Edge? Safari?
Firefox and Edge are planned for v1.1.0. Safari needs an Xcode wrapper and a paid developer account, so it sits in the backlog rather than on the roadmap.
Why should I believe the privacy claims?
Because you can check them. The source is MIT-licensed on GitHub, the permission list is one line of the manifest, and the checks that enforce both run on every pull request.