How to automatically generate UUIDv7 as record IDs

[mascahyo1]

Hi everyone,
I hope you're all doing well.

I would like to ask if it’s possible to have PocketBase automatically generate record IDs using UUIDv7 instead of the default 15-character alphanumeric IDs.

I’ve looked through the documentation but couldn’t find a built-in option for changing the ID generation strategy. My goal is to have every new record in a collection use a UUIDv7 as its primary ID.

Is there a recommended way to implement this? For example:

Using a before-create hook in a custom PocketBase js backend?

Any simple example code on how to override the default ID generator?

A small, easy-to-understand example would be greatly appreciated.

Thank you so much for your help!

[ganigeorgiev]

The id field is a regular collection text field, meaning that you can simply set its value from the client-side with the create request. Here is an example with the JS SDK:

await pb.collection("example").create({
    id: "YOUR_CUSTOM_ID", // it is always string
})

If you want to set the custom id automatically with a server-side hook, then this could be done with something like:

• Go:

  // https://pocketbase.io/docs/go-event-hooks/#onrecordcreate
  app.OnRecordCreate().BindFunc(func(e *core.RecordEvent) error {
      e.Record.Set("id", "YOUR_CUSTOM_ID")
  
      return e.Next()
  })

• JS pb_hooks:

  // https://pocketbase.io/docs/js-event-hooks/#onrecordcreate
  onRecordCreate((e) => {
      e.record.set("id", "YOUR_CUSTOM_ID")
  
      e.next()
  })

You can adjust the allowed length and regex validators from the specific field options in the collection panel:

---

With that said, the better question is - why would you want to use UUIDv7 and what do you think would be the benefit of doing that?

If you don't have a good reason, my recommendation would be to stick with the default one.