How to fix Invalid input syntax for UUID in PostgreSQL

What this error means

PostgreSQL uses the UUID data type to store Universally Unique Identifiers as defined by RFC 9562. When you try to insert a value into a UUID column or use it in a WHERE clause, PostgreSQL validates that the value conforms to strict formatting rules. The "Invalid input syntax for UUID" error indicates the provided value fails this validation check, typically due to malformed characters, incorrect hyphen placement, or values that aren't hexadecimal digits.

Typical symptoms

• INSERT or UPDATE statements fail with "invalid input syntax for type uuid" error
• SELECT queries with UUID comparison fail when filter values are incorrect
• ORM queries fail when UUID parameters are passed as strings in wrong format
• Migration scripts fail when trying to populate UUID columns with legacy data

Common causes

1. UUID value is missing or has extra characters (e.g., missing hyphens or malformed hex)
2. Value contains non-hexadecimal characters or is too short/long
3. Two UUIDs are concatenated together instead of being separate values
4. Extra quotes or braces are added around the UUID value by the application
5. ORM serialization error that wraps the UUID in JSON instead of passing it as a string
6. Legacy data format doesn't match PostgreSQL UUID expectations

How to fix "Invalid input syntax for UUID"

Valid: a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11
Valid: A0EEBC99-9C0B-4EF8-BB6D-6BB9BD380A11 (uppercase also accepted)
Valid: a0eebc999c0b4ef8bb6d6bb9bd380a11 (no hyphens)
Invalid: a0eebc99-9c0b-4ef8-bb6d (too short)
Invalid: a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11-extra (extra characters)

-- WRONG:
INSERT INTO users (id, name) VALUES ('"a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"', 'John');

-- CORRECT:
INSERT INTO users (id, name) VALUES ('a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11', 'John');

SELECT * FROM users WHERE id = 'a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11'::uuid;

INSERT INTO users (id, name) VALUES ('a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11'::uuid, 'John');

import { validate as uuidValidate } from "uuid";

const userInput = req.body.id;
if (!uuidValidate(userInput)) {
  throw new Error('Invalid UUID format');
}
await prisma.user.create({ data: { id: userInput, name: 'John' } });

from uuid import UUID

try:
  UUID(user_input)
except ValueError:
  raise Exception('Invalid UUID format')

import { Column, PrimaryGeneratedColumn } from 'typeorm';

@Entity()
export class User {
  @PrimaryGeneratedColumn('uuid')
  id: string;

  @Column()
  name: string;
}

model User {
  id    String  @id @default(cuid())
  name  String
}

-- For UUID v4 (random):
CREATE TABLE users (
  id uuid PRIMARY KEY DEFAULT gen_random_uuid(),
  name text NOT NULL
);

-- Insert without specifying id:
INSERT INTO users (name) VALUES ('John');

-- For older PostgreSQL versions (< 13), use uuid-ossp extension:
CREATE EXTENSION IF NOT EXISTS "uuid-ossp";

CREATE TABLE users (
  id uuid PRIMARY KEY DEFAULT uuid_generate_v4(),
  name text NOT NULL
);

Advanced notes

Frequently asked questions

What does "Invalid input syntax for UUID" mean?

PostgreSQL uses the UUID data type to store Universally Unique Identifiers as defined by RFC 9562. When you try to insert a value into a UUID column or use it in a WHERE clause, PostgreSQL validates that the value conforms to strict formatting rules. The "Invalid input syntax for UUID" error indicates the provided value fails this validation check, typically due to malformed characters, incorrect hyphen placement, or values that aren't hexadecimal digits.

How do I fix "Invalid input syntax for UUID"?

This error occurs when you attempt to insert or query a UUID column with a malformed value. PostgreSQL expects UUIDs in the standard 8-4-4-4-12 hexadecimal format, and will reject any value that doesn't match valid UUID syntax.

What causes "Invalid input syntax for UUID"?

UUID value is missing or has extra characters (e.g., missing hyphens or malformed hex) Value contains non-hexadecimal characters or is too short/long Two UUIDs are concatenated together instead of being separate values

Is the "Invalid input syntax for UUID" error serious?

It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Related errors

• Invalid JSON text

  How to fix "Invalid JSON text" in PostgreSQL

  MEDIUM

• invalid input syntax for type uuid

  How to fix "invalid input syntax for type uuid" in PostgreSQL

  MEDIUM

• ERROR: invalid name syntax

  Invalid name in PostgreSQL

  MEDIUM

• Invalid datetime format

  How to fix "Invalid datetime format" in PostgreSQL

  MEDIUM

• Invalid password

  How to fix "Invalid password" in PostgreSQL

  HIGH

• FATAL: no pg_hba.conf entry for host

  How to fix 'FATAL: no pg_hba.conf entry for host' in PostgreSQL

  HIGH

Official resources & further reading

• 📚PostgreSQL Official Documentation
• 📖
  PostgreSQL Docs - UUID Type(Official Docs)
• 📖
  PostgreSQL Docs - UUID Functions(Official Docs)
• Neon - PostgreSQL UUID Tutorial