Is there a difference between this and prisma-zod-generator?

prisma-zod-generator is a Prisma generator plugin that auto-generates Zod schemas during prisma generate. This converter is a quick online tool — no install, no Prisma CLI needed. Great for prototyping or when you just need a few schemas.

Prisma to Zod

Q: Why use Zod with Prisma?

Prisma provides database-level types, but those types aren't available at runtime for input validation. Zod schemas let you validate API request bodies against the same shape as your Prisma models — before data reaches the database.

Q: How are Prisma optional fields handled?

Prisma fields marked with '?' (e.g., 'email String?') become '.optional()' or '.nullable()' in the Zod schema, preserving the same optionality semantics.

Q: How are Prisma relation fields handled?

Relation fields (fields that reference another model) are omitted from the Zod schema with a comment suggesting z.lazy() for recursive schemas. This is intentional — relations are loaded separately in Prisma queries.

Convert Prisma schema models to Zod validation schemas with AI.

Using Prisma with tRPC, Next.js API routes, or any TypeScript backend? Convert your Prisma models to Zod schemas for runtime input validation — no manual mapping needed.

Paste your code, then click Convert

Zod

How to use this tool?

This online converter harnesses AI to translate Prisma schema models to Zod validation schemas. Follow these steps:

Paste your Prisma model definitions into the input box.
Click the "Convert" button to generate Zod schemas from the Prisma models.
View the Zod schemas and inferred TypeScript types in the output box.

Example: Simple Function

Prisma

model User {
  id        Int      @id @default(autoincrement())
  name      String
  email     String   @unique
  active    Boolean  @default(true)
  createdAt DateTime @default(now())
}

Zod

import { z } from 'zod';

export const UserSchema = z.object({
  id: z.number().int(),
  name: z.string(),
  email: z.string(),
  active: z.boolean(),
  createdAt: z.date(),
});

export type User = z.infer<typeof UserSchema>;

Frequently Asked Questions

Why use Zod with Prisma?

Prisma types exist at compile time but not runtime. Zod schemas validate API inputs against your Prisma model shape before any database call — combining Prisma's type safety with runtime validation.

How are Prisma optional fields handled?

Prisma 'field String?' becomes '.optional()' or '.nullable()' in Zod, preserving the same optionality semantics.

What Prisma scalar types are supported?

String→z.string(), Int→z.number().int(), Float→z.number(), Boolean→z.boolean(), DateTime→z.date(), Json→z.unknown(), Decimal→z.number(). Relation fields are omitted with a comment.

How are Prisma relation fields handled?

Relation fields are omitted from the Zod schema with a comment suggesting z.lazy() if needed. Prisma loads relations separately via include/select, so they're typically not part of input validation.

Is this different from prisma-zod-generator?

prisma-zod-generator is a Prisma generator plugin that runs during 'prisma generate'. This is a quick online converter — no install, no CLI needed. Great for prototyping or generating schemas for a few models.

Do @default and @unique attributes affect the Zod schema?

No. @default values and @unique constraints are database-level concerns handled by Prisma. The Zod schema focuses on runtime shape validation, not database constraints.

From the blog

View all →