Configure options below — the preview updates in real time.
Configures how Prisma ORM connects to your database.
The database connector to use.
Connection URL for the database. Use env("DATABASE_URL") to read from environment.
Direct connection URL used when the main url goes through a connection pooler (e.g. PgBouncer).
Connection URL for a shadow database used by Prisma Migrate in restricted environments.
Whether referential integrity is enforced by the database (foreignKeys) or emulated by Prisma (prisma).
List of database schemas to include (PostgreSQL and SQL Server multi-schema support).
List of PostgreSQL extensions to enable (e.g. pgcrypto, postgis).
Determines what client or assets are generated when running prisma generate.
The generator to use. Prisma ORM 7+ uses "prisma-client" by default. Can also be a path or npm package.
Target directory where the generated client is saved. Required for the prisma-client provider.
OS/architecture targets for query engine compatibility.
Unstable or beta Prisma features to enable.
Internal query engine type. Use 'client' for edge environments or Bun.
Generated code module format (only for prisma-client provider).
File extension used in import statements within the generated client.
File extension for the generated Prisma Client files.
Target runtime for optimized client generation.
CLI-level configuration introduced in Prisma ORM 7. These fields map to prisma.config.ts settings.
Path to the schema file or folder for multi-file schemas.
Directory where SQL migration files are stored.
Command executed when running prisma db seed.
Script to manually initialize a shadow database during migration generation.
Database connection URL override (separates secrets from schema file).
Shadow database URL for schema diffs.
Directory for SQL definitions of database views.
Output directory for TypedSQL assets.
Legacy configuration from the prisma key in package.json (pre-Prisma 7).
Command invoked when running npx prisma db seed.
Custom location of the schema.prisma file.
1