How to invalidate CDN cache for deleted image assets in Sanity?

21 replies
Last updated: Nov 29, 2025
Hi there!
My team deleted some image assets from our Sanity CMS. However, it appears those images are still available from the CDN. When reviewing the
CDN’s caching protocol it looks like assets are cached indefinitely. It is important we remove this asset we removed due to some copywright issues. How can we invalidate the cache for these images so that the Sanity CDN will remove them from cache?
Thanks a bunch!
AI Update

I understand your concern about copyright issues - this is definitely something that needs immediate attention.

Unfortunately, based on Sanity's Asset CDN documentation, assets are cached indefinitely once processed, and cache invalidation only occurs when an entire dataset or project is deleted. This is by design because Sanity uses content-addressable URLs (with SHA-1 hashes) that change when content changes, so there's typically no need for manual cache invalidation.

However, for urgent situations like copyright violations, you need to contact Sanity support directly. Here's what I recommend:

Immediate Steps:

  1. Contact Sanity Support - Reach out to support@sanity.io or use the support chat in your Sanity dashboard. Explain the copyright situation and provide:

    • The specific asset URLs that need to be removed
    • The asset IDs from your dataset
    • Details about the copyright issue
  2. Delete the assets from your dataset - If you haven't already, make sure to delete them from Sanity Studio or via the API to prevent future references

  3. For DMCA takedowns - If this is a formal DMCA situation, Sanity will have a process for handling these legal requests. They'll need proper documentation of the copyright claim.

Why you can't do this yourself:

The Asset CDN is managed infrastructure, and regular users don't have access to purge individual assets from the cache. This is different from the API CDN where you might have more control. Since assets are distributed across Google's global CDN infrastructure, only Sanity's operations team can force a cache purge.

Bottom line: Contact Sanity support immediately (support@sanity.io or through your dashboard chat) with the asset details and explain the copyright urgency. They should be able to help expedite the removal from the CDN given the legal nature of the issue.

Show original thread
21 replies

Sanity – Build the way you think, not the way your CMS thinks

Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.

Was this answer helpful?