Environments are unique, isolated containers where your app is deployed. Deploy your app to multiple environments—such as production, staging, or development—using branches from your GitHub repository. Each environment is fully separate, giving you the flexibility to test, preview, and release features independently.

Environments automatically update when a deployment succeeds, with zero-downtime between versions. If a deployment fails, the environment continues serving your last successful deployment, ensuring continuous availability.

Learn more about deployments →

---

See the below documentation for guidance on:

• Creating environments
• Managing environments
• Creating environment variables
• Managing environment variables

---

Managing environments

Creating environments

When you create a Webflow Cloud project, you’ll be prompted to add your first environment. You can create additional environments (like staging and development) to support your development workflow.

To set up additional environments:

• In Webflow Cloud, select your project name to open the Environments Dashboard.
• Click “Create New Environment.”
• Select the GitHub branch you want this environment to track.
• Define the mount path (URL path) for your environment.
• Click Create Environment.

Every push to the selected branch will trigger a deployment to this environment.

Mount paths

Each environment is assigned a unique URL path under your Webflow domain. When you deploy to an environment, your application becomes accessible at its designated path. This path-based routing allows you to:

• Host multiple environments under a single domain
• Maintain separate URLs for staging, development, and production versions
• Seamlessly integrate with Webflow’s existing routing system

Mount paths are unique to each environment and are used to route traffic to the correct environment. Mount paths must be unique across all environments.

Changing mount paths

If you’ve already deployed an environment to your site with a mount path and you want to change it, you should:

• Click the ellipsis icon “…” for the environment
• Select “Edit”
• Change the mount path to your desired new path and save the changes
• Publish your Webflow site
• Trigger a deployment to the environment to propagate the mount path change

Route conflicts

If a route conflict occurs between your Webflow Cloud application and your Webflow site, the Webflow Cloud application route takes precedence.

For instance, if you have a Webflow site at mydomain.com with the following:

1. A Webflow Cloud app mounted at /users
2. A Webflow page also created at /users

When a user visits mydomain.com/users, they will see the Webflow page, not your Webflow Cloud app.

To avoid conflicts:

• Choose mount paths that don’t conflict with existing or planned Webflow pages
• Consider using distinct paths like /app for your Webflow Cloud applications
• Document your app routes to prevent future conflicts when creating new Webflow pages

Edit an environment

• Click the ellipsis icon “…” next to the environment.
• Select Edit.
• Modify the mount path or other details.
• Save your changes.
• Re-publish your site to reflect updates.

Unpublish an environment

To remove the environment from your domain entirely, you must delete the Webflow Cloud project and republish the Webflow site.

Deleting the environment by itself does not remove it from your domain.

Delete an environment

Delete and environment to remove it from Webflow Cloud. Note that deleting an environment does not delete the GitHub branch. Conversely, deleting a GitHub branch does not delete the environment - you must delete the environment manually from the dashboard.

• Click the ellipsis icon “…” next to the environment.
• Select Delete.
• Confirm the deletion.

Access control and permissions

Anyone with access to your deployed mount path can view the environment. For example, if deployed to /staging, anyone with the URL can access the staging version of your site.

Managing environment variables

Environment variables enable secure storage and management of sensitive data and configuration settings. Each environment supports up to 110 environment variables, which are accessible exclusively during runtime. For enhanced security, you can mark variables as secrets, which are then encrypted and masked in the Environment Variables dashboard. To view the value of a secret variable, click the eye icon to toggle its visibility.

Create an environment variable

• Open the Deployments Dashboard for the environment.
• Click Environment Variables.
• Click Add Variable.
• Enter a Key and Value.
• (Optional) Mark as a Secret to mask sensitive values like API keys or client secrets.
• Push a commit to trigger a new deployment using the updated variables.

Edit an environment variable

• In the Environment Variables dashboard, click the “…” next to a variable.
• Select Edit.
• Modify the Key and Value.
• (Optional) Mark as a Secret to mask sensitive values like API keys or client secrets.
• Make changes to your code and push a new commit to apply the updated environment variables.

Delete an environment variable

• In the Environment Variables dashboard, click the “…” next to a variable.
• Select Delete.
• Make changes to your code and push a new commit to apply the removal of this environment variable.

Visibility of environment variables

Anyone with access to the Webflow Cloud project can view environment variables. Keep sensitive values stored as Secrets.

Frequently asked questions

Projects

Environment access and visibility