Add support for generating UUIDv7s

[jreidgreer]

What is the problem this feature will solve?

UUIDv7s are time-based UUIDs which can be helpful for sorting & database distribution. The standard is published here: https://datatracker.ietf.org/doc/html/rfc9562#name-uuid-version-7

Postgres recently shipped native support for UUIDv7 generation, and Bun has a helper Bun.randomUUIDv7();

Having to reach for a library in order to generate non-v4 UUIDs is a bummer and adds bloat for a very common workflow.

What is the feature you are proposing to solve the problem?

I'm proposing UUIDv7 generation support be included in the Crypto module.

The actual API for this could either follow Bun's path of a separate method .createRandomUUIDv7(), or add in a property to the existing createRandomUUID options parameter such as version. These are not mutually exclusive, and you could imagine the parameter & method both existing for convenience.

Examples:

const {
  createRandomUUIDv7,
  createRandomUUID
} = await import('node:crypto');

createRandomUUIDv7();
// => "019d45ea-151f-780b-82a6-d097b39db62a"

createRandomUUID({
  version: "v7"
});
// => "019d45ea-fc8e-7792-bfa1-ae58916be0e3"

What alternatives have you considered?

No response

[nabeel378]

Hi, I’m interested in implementing UUIDv7 support in the crypto module.
I plan to create a createRandomUUIDv7() method following the RFC.
Please let me know if this aligns with maintainers’ expectations.

[jasnell]

@nabeel378 ... no need to ask permission! Just go for it. A few recommendations: keep the implementation as simple as possible, include tests and documentation. Keeping it as a separate function createRandomUUIDv7 without touching the existing createRandomUUID is ideal. Happy to review it once implemented.

[nabeel378]

@jasnell Done! PR here: #62553

[Delapouite]

@panva and @jasnell : do you think this useful feature should also trickle to the WebCrypto WG and/or Winter TC in order to be standardized across all runtimes?

[panva]

You can certainly propose it as a feature in the Web Cryptography tracker. The judge of its usefulness there will be implementer interest, seldomly has niche use case user interest translated to adoption tho.

Its mere presence in node:crypto should have it trickle down to runtimes such as Deno, Bun and Cloudflare Workers through their node compatibility layers, such that they are.

[damianremington274-blip]

Yeah, might be worth proposing there to see if there’s any interest. Agree it’ll probably come down to whether implementers actually want it, but no harm in putting it on their radar.

…

On Fri, Apr 3, 2026, 8:27 AM Filip Skokan ***@***.***> wrote: *panva* left a comment (nodejs/node#62529) <#62529 (comment)> You can certainly propose it as a feature in the Web Cryptography tracker. The judge of its usefulness there will be implementer interest, seldomly has niche use case user interest translated to adoption tho. — Reply to this email directly, view it on GitHub <#62529?email_source=notifications&email_token=B7YAFGUHNEVSAEEWCKMDTOD4T632PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJYGM2DQMJVGI4KM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4183481528>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B7YAFGRBEKLKLI5VKC4KAST4T632PAVCNFSM6AAAAACXILW4QOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCOBTGQ4DCNJSHA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>