Troubleshooting binary size and deployment issues (Prisma ORM v6) (/docs/orm/v6/prisma-client/debugging-and-troubleshooting/troubleshooting-binary-size-issues)

For the complete Prisma documentation index, see llms.txt. A markdown version of any docs page is available by appending .md to its URL.

This page covers how to resolve large bundle sizes, slow builds, and deployment errors caused by Prisma ORM Rust engine binaries

Location: ORM > v6 > Prisma Client > Debugging and Troubleshooting > Troubleshooting binary size and deployment issues

If you encounter large bundle sizes, slow builds, or deployment errors related to Prisma’s Rust engine binaries, for example, in serverless or edge environments, the issue may be caused by the default native Rust query engine that ships with Prisma Client.

As of v6.16.0, you can resolve these issues by removing the Rust-based engine binary from Prisma ORM by configuring your generator block as follows:

generator client {
  provider   = "prisma-client"
  output     = "./generated"
  engineType = "client"
}

[!NOTE] Note that you need to use a driver adapter in this case.

With this architecture:

• No Rust query engine binary is downloaded or shipped.
• The database connection pool is maintained by the native JS database driver you install (e.g., @prisma/adapter-pg for PostgreSQL).

This setup can help if you are:

• Deploying to serverless functions or edge runtimes
• Running in read-only filesystem environments
• Working within CI/CD pipelines with strict size limits

Visit No Rust engine for complete setup instructions and supported databases.

To learn why Prisma ORM moved from Rust binary engines to an all-TypeScript approach, and how the two compare in benchmarks, read this blog post.

• Debugging: This page explains how to enable debugging output for Prisma Client by setting the DEBUG environment variable.
• Handling exceptions and errors: This page covers how to handle exceptions and errors