Environment variables

Environment variables are key/value pairs injected into your application at runtime and, optionally, at build time. Each environment has its own independent set of variables.

Adding and editing variables

Go to your environment and open the Variables tab. Click Add variable to add a new key/value pair. Changes are saved when you click Save.

Key names must:

Start with an uppercase letter (A–Z)
Contain only uppercase letters, digits, and underscores (A–Z, 0–9, _)

Build scope

By default, variables are only available at runtime — your running application. To also expose a variable during the build step, enable its Build scope toggle.

This is required for client-side public variables in Next.js and Nuxt:

Framework	Prefix	Example
Next.js	`NEXT_PUBLIC_`	`NEXT_PUBLIC_API_URL`
Nuxt	`NUXT_PUBLIC_`	`NUXT_PUBLIC_API_URL`

Variables with Build scope enabled are visible in build logs. Do not enable Build scope on sensitive values.

Hidden variables

Toggle Hidden on a variable to mask its value in the dashboard UI. The value is no longer visible after saving.

Hidden is a UI-only mask. Variable values are not encrypted at rest or in transit. Do not rely on Hidden for secrets management — treat all variable values as potentially visible to anyone with dashboard access to the environment.

Importing from a `.env` file

Click Import .env and paste the contents of a .env file. The importer:

Parses KEY=value lines
Strips surrounding quotes from values
Ignores blank lines and lines starting with #
Rejects the entire import if any line cannot be parsed

Imported variables are merged with existing ones. Existing keys with the same name are overwritten.

Conflicts

If another team member saves a variable change while you have unsaved edits open, a conflict banner appears. Review the latest values before saving to avoid overwriting their changes.