# Deleted images are still accessible via CDN (copyright risk)

**URL:** <https://community.sitejet.io/t/deleted-images-are-still-accessible-via-cdn-copyright-risk/5375>\
**Category:** Feature Requests\
**Created:** [December 9, 2025, 1:27pm UTC](https://community.sitejet.io/t/deleted-images-are-still-accessible-via-cdn-copyright-risk/5375 "2025-12-09T13:27:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Detlef\_Danitz](https://avatars.discourse-cdn.com/v4/letter/d/b5e925/32.png) [@Detlef\_Danitz](https://community.sitejet.io/u/Detlef_Danitz)\
**Post date:** [December 9, 2025, 1:27pm UTC](https://community.sitejet.io/t/deleted-images-are-still-accessible-via-cdn-copyright-risk/5375/1 "2025-12-09T13:27:44Z")

</div>

Hi everyone,

I’m not sure if this is expected behavior or if I’m missing something, but I’m running into an issue with image deletion:

### **Use case**

I upload images to the Website Builder for certain pages or campaigns.

Some of these images may only be published for a limited time (copyright restrictions, licensing agreements, etc.).

Later, I remove the images from:

- the Website Builder

- **and** from “Files & Stock Photos”

### **Issue**

Even after deleting the images in both places, they are still publicly accessible through the Sitejet CDN, for example:

[https://cdn1.site-media.eu/images/…](https://cdn1.site-media.eu/images/%E2%80%A6)

### **This means**

The files appear to be deleted in the UI, but they still remain on the CDN and are publicly reachable. This is a potential legal problem, since licensed images continue to be accessible.

In my case, I’ve had to contact Sitejet Support several times to remove the images manually and permanently.

### **Is there a direct delete / purge option?**

Something like:

- a permanent delete / “hard delete”

- a purge from CDN

- an expiration date / auto delete

- or a button to fully remove files from the server

### **Why this matters**

For images that are only allowed to be published for a certain period, being accessible in the CDN afterwards can still be considered a copyright violation and may result in legal consequences or claims.

**Has anyone experienced the same issue? Is there a workaround or a recommended process to permanently delete images? Who else thinks that Sitejet should handle this in a way that when an image is deleted from the ‘Files & Stock Photos’ section, it is also automatically removed from [https://cdn1.site-media.eu/images?](https://cdn1.site-media.eu/images?)**

Thanks a lot!

---

<div class="post-metadata">

**Author:** ![Kalisperakichris](https://dub1.discourse-cdn.com/flex017/user_avatar/community.sitejet.io/kalisperakichris/32/3572_2.png) [@Kalisperakichris](https://community.sitejet.io/u/Kalisperakichris)\
**Post date:** [December 10, 2025, 5:25am UTC](https://community.sitejet.io/t/deleted-images-are-still-accessible-via-cdn-copyright-risk/5375/2 "2025-12-10T05:25:41Z")

</div>

**Here’s what I’ve noticed from my own workflow with Sitejet and CDN-cached assets:**

**1) Deleting files from the UI does not instantly purge them from the CDN**  
This is normal behaviour in many CDN systems — they keep cached versions for a while unless a forced purge is triggered.  
So the file looks deleted inside Sitejet, but the cached version still resolves for some time.

**2) In my case, the image disappeared from CDN once the CDN cache expired**  
Usually after some hours or (rarely) a day.  
It’s not ideal for licensed images, but it _does_ eventually clear.

**3) The only “instant” workaround I’ve used:**

- Rename the file (slightly) before deleting it

- Delete the renamed version  
This prevents the old CDN URL from resolving because the filename no longer matches any stored asset.

**4) If the image must be removed _immediately_ for legal/contract reasons**  
Then contacting support is still the fastest way, since they can manually purge it on their side.

**5) I agree that a ‘Hard Delete / Purge From CDN’ button would solve this**  
Especially for licensed or time-restricted photos.  
It would make the process clear, safe and compliant.

So yes, I’ve seen the same behaviour — and a CDN-purge feature would be a really useful addition.  
Thanks for raising it, it’s an important topic.

---

<div class="post-metadata">

**Author:** ![Andre](https://dub1.discourse-cdn.com/flex017/user_avatar/community.sitejet.io/andre/32/3459_2.png) [@Andre](https://community.sitejet.io/u/Andre)\
**Post date:** [December 10, 2025, 11:12am UTC](https://community.sitejet.io/t/deleted-images-are-still-accessible-via-cdn-copyright-risk/5375/3 "2025-12-10T11:12:55Z")

</div>

> [@Kalisperakichris](#):
>
> **3) The only “instant” workaround I’ve used:**
> 
> - Rename the file (slightly) before deleting it
> - Delete the renamed version  
> This prevents the old CDN URL from resolving because the filename no longer matches any stored asset.

That is a nice workaround.

---

<div class="post-metadata">

**Author:** ![Detlef\_Danitz](https://avatars.discourse-cdn.com/v4/letter/d/b5e925/32.png) [@Detlef\_Danitz](https://community.sitejet.io/u/Detlef_Danitz)\
**Post date:** [December 10, 2025, 11:48am UTC](https://community.sitejet.io/t/deleted-images-are-still-accessible-via-cdn-copyright-risk/5375/4 "2025-12-10T11:48:40Z")

</div>

**thanks for the advice** 🙂
