CDN Management

Manage Kinsta CDN cache to ensure visitors see your latest content updates

CDN Management The [[gloss:content-delivery-network|CDN]] Management feature allows you to control Kinsta's Content Delivery Network cache for your WordPress sites. Clear cached content to ensure visitors see your latest updates immediately. This feature is specifically for Kinsta CDN. Other CDN providers like Cloudflare or AWS CloudFront are not currently supported. What is CDN Cache? A CDN (Content Delivery Network) stores copies of your website's static files (images, CSS, JavaScript) on servers around the world. This speeds up your site by serving content from locations closer to your visitors. However, cached content can sometimes show outdated versions after updates. When to Clear CDN Cache Clear your CDN cache when: CSS or design changes aren't appearing. Updated images still show old versions. JavaScript functionality changes aren't working. After major content updates. When troubleshooting display issues Clearing CDN cache temporarily increases server load as the CDN rebuilds its cache. Avoid clearing during peak traffic times unless necessary. Setting Up CDN Management Via Kinsta Integration Connect Kinsta in the Integrations page. CDN management will be available automatically. Navigate to CDN in the sidebar Direct Connection For temporary access without saving credentials: Go to the CDN page. Enter your Kinsta API Key. Enter the Environment ID from MyKinsta. Enter the CDN Cache ID. Click Connect Find your CDN Cache ID in MyKinsta under Sites > Your Site > CDN > Settings. Clearing CDN Cache To clear your CDN cache: Navigate to the CDN page. Verify you're connected to the correct site. Click 'Clear CDN Cache'. Wait for confirmation (usually takes 10-30 seconds). The last cleared timestamp will update Cache clearing is immediate, but it may take 1-2 minutes for changes to propagate globally across all CDN edge servers. Understanding Cache Behavior What Gets Cached Static files (CSS, JS, images, fonts). Media uploads. Theme assets. Plugin resources What Doesn't Get Cached Dynamic PHP content. Database queries. User-specific content. Admin pages. Shopping cart data URL Parameters for Automation You can bookmark or automate CDN management using [[gloss:url-parameters|URL parameters]]: /cdn?apiKey=YOUR_API_KEY&environmentId=ENV_ID&cdnCacheId=CACHE_ID This is useful for: Quick access bookmarks. Sharing with team members. Integration with deployment scripts. Automation workflows Best Practices Clear cache after deploying CSS/JS changes. Use cache busting for development (version query strings). Schedule major cache clears during low-traffic periods. Document when and why cache was cleared. Test changes in staging before production cache clear Browser Cache vs CDN Cache Remember that CDN cache is different from browser cache: CDN cache: Server-side, affects all visitors. Browser cache: Client-side, affects individual users. Clearing CDN doesn't clear browser caches. Users may need to hard refresh (Ctrl+F5) for immediate updates Troubleshooting Cache Clear Fails Verify API credentials are correct. Check CDN Cache ID matches your site. Ensure Kinsta CDN is enabled for your site. Try again after a few minutes Changes Still Not Showing Wait 2-3 minutes for global propagation. Clear browser cache (Ctrl+F5). Check if Kinsta Edge Cache also needs clearing. Verify files were actually updated on server Pro Tip: Kinsta's CDN automatically caches new content after clearing. No manual intervention needed to rebuild the cache.