While Builds are incremental, deploying site changes to Gatsby Cloud Hosting still pushed the entire site. With Incremental Deploys, this process is now incremental as only the routes and pages that have changed will be deployed.
For a large site like gatsbyjs.com which has over 50,000 routes, deploys decreased from 40 seconds to about 2 seconds. The speed of deploys is now dependent on the number of routes being updated rather than the size of site. For example, updating a single blog post will deploy only that blog post instead of the entire site.
Incremental Deploys does not improve cold build performance since all routes must be updated.
Who can use Incremental Deploys?
Incremental Deploys works alongside Incremental Builds—Gatsby 4 required. Builds that are not incremental will not be incrementally deployed.
Incremental Deploys already powers all incremental CMS Preview builds on Gatsby Cloud.
Incremental Deploys powers all Branch and Pull Request builds for non-enterprise sites. Enterprise sites can follow the instructions below to opt-in to Incremental Deploys before the are enabled by default for all Gatsby 4 sites in Q4 of 2022.
Incremental Deploys does not support Gatsby 3 or 3rd party hosting providers (ie: S3).
Not running Gatsby 4 yet? Learn how to upgrade →
How-to Enable Incremental Deploys
Enable Incremental Deploys for Branch and Pull Request builds by going to Site Settings → Builds → Enable Incremental Deploys.
How do I know Incremental Deploys is working?
To verify Incremental Deploys is working, you should see a single "Deploying to Gatsby Cloud Hosting" step at the end of your build.