Cache

Where to find it

1. Open your project.
2. Under Extensions, click Cache.
3. Use the switch next to the Enabled or Disabled badge.

Every team member can open the Cache page. Only team admins see the switch and can clear the cache.

Cache is off for new projects. When it is off, the page shows Cache is Disabled and nothing else.

How it works

With the cache off, every publish is a full rebuild. WCH fetches and renders every page and downloads your CSS and JavaScript files again.

With the cache on, WCH checks each page before it does the work:

• Unchanged in Webflow, skipped. WCH reads the lastmod date for each page in your source sitemap. If it matches the date from the last time the page was rendered, WCH skips the page.
• Unchanged output, not rewritten. If a page is rendered and the result is identical to what was published last time, WCH keeps the existing copy.
• No lastmod, always rendered. If your sitemap has no lastmod date for a page, WCH renders it every time and then compares the result.
• Output path overrides, always rendered. Pages that use an output path override are rendered on every publish. See Output path overrides.
• CSS and JavaScript kept. Files already downloaded stay in place instead of being cleared and fetched again.
• Webflow stylesheet names kept. Webflow gives each version of a stylesheet its own filename. With the cache on, WCH keeps those names, so a skipped page keeps pointing at the stylesheet it was built with. With the cache off, each stylesheet has one fixed name.

If every page is skipped, the publish finishes with "All pages are up to date. Nothing to publish." in the logs.

When it applies

The cache applies to every publish that renders pages: a single page, Publish selected, Publish all pages, Webflow webhooks, and CMS webhooks.

It takes effect after one full publish. The first publish after you turn the cache on, or after you clear it, rebuilds every page. Later publishes skip what has not changed.

The cache only changes how WCH builds your staging copy. Promote and deploy still package the full site for your destination.

Turning the cache on or off

1. Go to Extensions, then Cache.
2. Turn on the switch. WCH shows "Cache enabled".
3. Publish all pages once to build the baseline.

To turn it off, turn off the same switch. The next publish is a full rebuild.

Clearing the cache

Clearing the cache makes the next publish render every page again.

1. Go to Extensions, then Cache.
2. Under Clear All Cache, click Clear all cache.
3. Publish all pages.

Clearing does not remove your staging site, your archives, or anything at your destinations. It only resets what WCH remembers about each page.

Clear the cache after changing project settings

The cache only notices changes made in Webflow. A page that has not changed in Webflow is skipped, even if you changed a WCH setting that affects its output.

After you change any of these, click Clear all cache before you publish:

• Project domain, Root directory, or File Prefix
• Excluded URLs. See Excluded URLs.
• Include Code Components. See Code Components.

Without a clear, only the pages that changed in Webflow pick up the new setting. See Project Settings for every setting.

Testing your changes

1. Turn on the cache and click Publish all pages on the Dashboard.
2. Edit one page in Webflow and publish the Webflow site.
3. Publish all pages in WCH again. Open the logs and confirm the publish is faster and the edited page updated.
4. Once staging looks right, promote to production.

Troubleshooting

• A setting change does not appear on some pages: those pages were skipped because they did not change in Webflow. Click Clear all cache and publish all pages.
• Every page renders every time: your source sitemap has no lastmod dates, or the cache was cleared before this publish. Check that the switch shows Enabled.
• "All pages are up to date. Nothing to publish.": nothing changed since the last publish. Clear the cache if you need a full rebuild.