Deployments
Learn about deployments in Webflow Cloud
Deployments automatically build and publish your application to Webflow Cloud. Each deployment creates a new version of your app in the associated environment. Webflow Cloud automatically triggers deployments when you push changes to the branch linked to that environment.
Learn more about environments →
See the below documentation for guidance on:
Webflow Cloud supports continuous integration and deployment (CI/CD) through GitHub. When you connect your GitHub repository, Webflow Cloud automatically:
You can also manually deploy your local environment using the Webflow CLI. In your terminal, run the following command to deploy your app to Webflow Cloud:
If you have access to over 100 repositories, you may not see a list of your repositories to select from. In this case, paste the link to your repository into the GitHub repository field.
There are two ways to manually deploy your environment:
Deploy using the Webflow CLI
Run the following command in your terminal:
Deploy in the Webflow Cloud dashboard
Navigate to your environments dashboard and click the “Deploy latest build” button.
Webflow Cloud serves your app through a streamlined deployment process:
Each step is logged and available for review in the build logs.
Each deployment appears in your environment’s deployment history. The history provides:
In the event of a failed deployment, your environment continues running your last successful deployment, ensuring zero downtime.
Build logs provide detailed information about how Webflow Cloud builds and deploys your app. To view build logs:
Build logs are particularly helpful for:
Runtime logs show you what’s happening on your application’s server after deployment. These logs capture server-side activity, including:
For example, if your application includes an API endpoint and a user makes a request to that endpoint, you’ll see the corresponding server-side activity in the runtime logs.
To view runtime logs:
Runtime logs are helpful for debugging server-side issues and monitoring your application’s API behavior in production.
If you need to revert to a previous version of your app:
Rolling back a deployment creates a new deployment with the previous code version. It doesn’t restore the exact state of the previous deployment.
Webflow Cloud currently supports Next.js and Astro apps. Make sure:
next.config.js or astro.config.mjs) with the necessary Webflow Cloud-specific configurations.Environment variables are only available at runtime, not during the build process.
This is typically related to base path configuration. Check your asset paths and ensure they’re configured for your environment. For more information on base path configuration, see base path configuration section of the Bring Your Own App documentation.
The most recent successful build will continue running. Failed deployments never impact your live site.
To rollback to a previous deployment:
Try refreshing your page - new deployments may not appear immediately in the dashboard.
No, only the most recent successful deployment for each environment can be previewed.
The Webflow Cloud GitHub App may not have access to your repository. To check, go to the Webflow Cloud tab in your Webflow site settings and click “Install GitHub App.” Follow the prompts on GitHub to ensure Webflow has access to read from your repository. Once you grant access, try committing to the branch that Webflow Cloud should be monitoring for deployments in your app.
No, the deployment process for Webflow Cloud apps does not automatically publish your Webflow site, and publishing your Webflow site does not trigger a Webflow Cloud deployment.