Add, edit, or remove a value
Open the project → Settings → Build and locate its environment-variable editor
You need permission to manage the project's build configuration.
Add a name/value pair or paste the supported .env format
Use the names expected by the app and do not paste unrelated local credentials.
Review the editor for invalid or duplicated names and save the changes
If the UI permits revealing a stored value, do so only when authorized; a masked field does not mean its value is unrecoverable to every permitted manager.
Make a new build and open that new preview
A previously built browser bundle cannot update a compiled variable when you only save a setting.
Remove a value in the editor, save, and rebuild when it is no longer required
Remove or rotate a compromised credential at its issuing service as well.
Understand where the value is used
| Type | Behavior |
|---|---|
| Build-time | Read by the build command; a change normally requires a new build. |
| SSR/server runtime | Read by the application server if the selected hosting/runtime supports it. Check the framework's runtime expectations. |
| Public browser variable | Prefixes such as NEXT_PUBLIC_ and VITE_ can compile the value into public JavaScript. Encryption in a settings store does not make the compiled value secret. |
| Build-tool secret | Keep CLARON_API_KEY and deployment tokens in the build secret environment, without public frontend prefixes. |
Verify and troubleshoot
Confirm the app behavior in the new build without printing secret values into logs. Check the name, selected project/environment, framework prefix, and time of use when a variable appears missing.
Cannot find module generally requires a dependency/path check; it is not a reliable missing-variable diagnosis. For build errors, use Builds & Previews. For different staging and production targets, use Environments & Releases.