Back to Community

How to Request Removal of Cached Images from Jetpack's CDN

29 threads Sep 17, 2025 PluginJetpack

Content

Many WordPress site owners use Jetpack's Site Accelerator (also known as the Image CDN or Photon) to speed up image delivery. A common point of confusion arises when an image is deleted from a site's media library or server, yet it remains accessible via a Jetpack CDN URL (like i0.wp.com, i1.wp.com, etc.). This article explains why this happens and outlines the steps you can take to request removal.

Why Deleted Images Can Still Appear

Jetpack's Site Accelerator is a caching content delivery network (CDN). When enabled, it creates copies of your images on its global servers to serve them to visitors faster. The system is designed to be efficient, not to constantly check if the original image on your server still exists. Therefore, if an image is deleted from your site after it has been cached, the cached copy on the CDN may persist for a period. Manually accessing the i0.wp.com URL can even trigger the CDN to fetch and cache the image again if it's still available at its original location.

How to Request Image Removal from the CDN

Based on community reports, the Jetpack team can manually purge specific images from their CDN cache upon request. Here is the recommended process:

  1. Delete the Original Image: First, ensure the image has been permanently removed from your WordPress Media Library. If the original file remains on your server, the CDN may continue to cache it.
  2. Clear Your Site's Cache: Use your caching plugin or hosting provider's tools to clear your site's entire cache. This helps ensure your site is not serving old links.
  3. Gather the CDN URLs: Compile a list of the full Jetpack CDN URLs for the images you need removed (e.g., https://i0.wp.com/yoursite.com/wp-content/uploads/example.jpg?ssl=1).
  4. Contact the Jetpack Team: You will need to submit a direct request to the Jetpack team for manual removal. You can do this by using their official contact form. Be sure to provide the complete list of CDN URLs and explain the reason for the request (e.g., copyright issue, outdated image).

Important Limitations to Know

  • There is no user-accessible button to bulk purge the CDN cache; removal is a manual process handled by the Jetpack team.
  • Requests to remove an extremely high volume of images (thousands) may not be feasible.
  • The CDN is not an image hosting service. It requires the original image to be hosted on your server to function. If you delete the original, the CDN link will eventually break, but a manual request accelerates this process.
  • If you continue to see an old image, ensure you are not accidentally linking to the CDN URL somewhere on your site or in your browser history.

When Jetpack Might Not Be the Cause

If you are experiencing general image loading issues or 403 errors, the problem might not be Jetpack's CDN. First, confirm that the Jetpack plugin is actually active and connected on your site. Other plugins or a different CDN service could be responsible. Troubleshooting should always start by checking your active plugins and site configuration.

For urgent issues, such as copyrighted material, providing clear, specific URLs in your support request is the fastest way to get assistance.

Related Support Threads Support