After a site migration, Webflow’s server-side cache may cause delays in showing updated content or DNS changes. Here's how to clear or bypass it effectively.
1. Publish the Site Again
- Go to the Webflow Designer or Project Settings.
- Click Publish in the top-right corner.
- Select your custom domain(s) and webflow.io staging domain, then click Publish to Selected Domains.
- This forces Webflow to rebuild and serve the latest version of your site.
2. Force a DNS Propagation Refresh
- If you changed DNS records, Webflow might still be referencing old caches.
- Ensure that your domain’s A records point to Webflow’s IPs: (a) 75.2.70.75, (b) 99.83.190.102.
- You can check DNS propagation using tools like WhatsMyDNS.net to see if records are resolving globally.
3. Clear Cloudflare or External CDN Cache (If Used)
- If your domain uses Cloudflare or another third-party CDN, log in and purge the cache from the provider’s dashboard.
- Webflow’s built-in hosting does not use Cloudflare by default, but domain-level services might.
4. Use Incognito Mode or Bypass Browser Cache
- Browser cache can also make it seem like old files are still being used.
- Use incognito/private mode or clear your browser cache to rule this out.
5. Check Asset Versioning
- Webflow appends version parameters to published assets (e.g., image.jpg?v=12345).
- Republishing the site ensures that new asset URLs are generated, which bypasses cache.
Summary
To clear Webflow’s server cache after migration, republish your site to both custom and staging domains, ensure DNS is properly set, and flush any third-party CDN caches. This triggers Webflow to serve a fresh version of your site.