Environment variables reference

This document describes different environment variables and their use cases.

Prisma Client


DEBUG is used to enable debugging output in the Prisma Client.

Example setting Prisma Client level debugging output:

$# enable only `prisma:client`-level debugging output
$export DEBUG="prisma:client"

See Debugging for more information.


NO_COLOR if truthy will activate the colorless setting for error formatting and strip colors from error messages.

See Formatting via environment variables for more information.

Prisma Studio


BROWSER is for Prisma Studio to force which browser it should be open in, if not set it will open in the default browser. It's also used as a flag when starting the studio from the CLI.

BROWSER=firefox prisma studio --port 5555
$prisma studio --browser firefox

See Studio documentation for more information.

Prisma CLI


PRISMA_HIDE_UPDATE_MESSAGE is used to hide the update notification message that is shown when a newer Prisma CLI version is available. It's a truthy value.

const shouldHide = process.env.PRISMA_HIDE_UPDATE_MESSAGE


PRISMA_GENERATE_SKIP_AUTOINSTALL can be set to a truthy value to skip the auto-install of prisma CLI and @prisma/client dependencies (if they are missing), if the prisma-client-js generator is defined in the Prisma Schema, when using the prisma generate command.


Disables all CLI warnings generated by logger.warn.

Proxy environment variables

The Prisma CLI supports custom HTTP(S) proxies to download the Prisma engines. These can be helpful to use when working behind a corporate firewall. See Using a HTTP proxy for the CLI for more information.


NO_PROXY is a comma-separated list of hostnames or IP addresses that do not require a proxy.



HTTP_PROXY is set with the hostname or IP address of a proxy server.



HTTPS_PROXY is set with the hostname or IP address of a proxy server.


Binary environment variables

By default all binaries are downloaded when you install Prisma CLI. There are however situations where you may wish to use a custom binary. See Prisma Engines for more information.


PRISMA_BINARIES_MIRROR can be used to specify a custom CDN (or server) endpoint to download the engines binaries for the CLI/Client. The default value is https://binaries.prisma.sh, where Prisma hosts the binaries.


See Prisma engines for a conceptual overview of how to use this environment variable.


PRISMA_MIGRATION_ENGINE_BINARY is used to set a custom location for your own migration engine binary.



PRISMA_QUERY_ENGINE_BINARY is used to set a custom location for your own query engine binary.



PRISMA_INTROSPECTION_ENGINE_BINARY is used to set a custom location for your own introspection engine binary.



PRISMA_FMT_BINARY is used to set a custom location for your own format engine binary.



PRISMA_CLI_BINARY_TARGETS can be used to specify one or more binary targets that the CLI will download, it must be provided during npm install.

For example: If you are on macOS, the binary target is darwin & AWS Lambda target is rhel-openssl-1.0.x

$PRISMA_CLI_BINARY_TARGETS=darwin,rhel-openssl-1.0.x npm install
Edit this page on GitHub