UUID

The UUID (Universally Unique Identifier) field generates a unique identifier (UUID v4) for each record. A UUID is a 128-bit value. It shows as a 36-character string in the format xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (for example, 31c46437-0bb9-4072-bf7a-40cd7aebcae3). Use UUIDs when your records need globally unique identifiers that are not sequential.

Create a UUID field

1. Click the + icon next to the last field in your table.
2. Enter a name for the field (optional).
3. Select UUID from the list of field types.
4. Click Save Field. NocoDB adds the field to your table.

Refer to the general guidelines on creating a field.

Cell display

The UUID field shows as a read-only text cell. NocoDB generates the value when you create a new record. You cannot edit the value or paste into the cell.

Key behaviours

Read-only

The database generates UUID values. You cannot edit, paste or override them. If you try to edit a UUID cell, NocoDB shows a read-only warning.

Unique constraint

The database applies a unique constraint to every UUID field. Thus no two records in the same table can have the same UUID value.

Auto-generated on record creation

When you add a new record to the table, NocoDB assigns a UUID value with the PostgreSQL gen_random_uuid() function. You do not need to fill the field.

Not available in forms

The system generates UUID values, so UUID fields do not show in form views. When a form submission creates a new record, NocoDB assigns the value.

Filtering UUID fields

UUID fields support these text filter operations. You can filter with full or partial UUID values.

Sorting UUID fields

You can sort UUID fields in ascending or descending order. The sort uses the text of the UUID. Thus it follows lexicographic (alphabetical) order, not a chronological sequence.

Duplicating a table with UUID fields

When you duplicate a table that has UUID fields, the new table keeps the UUID column structure. But NocoDB generates new UUID values for all records in the duplicated table. It does not copy the original values.

Limitations

• PostgreSQL only: UUID fields need a PostgreSQL database. They are not available on MySQL, SQLite or other database backends.
• No default value configuration: NocoDB sets the default value (gen_random_uuid()). You cannot change it.
• No copy-paste: You cannot paste values into a UUID field.

• For external database connections, NocoDB supports UUID fields only on PostgreSQL databases.

Availability

• UUID is available on all NocoDB Cloud plans and licensed self-hosted deployments (Business plan and above).