> ## Documentation Index
> Fetch the complete documentation index at: https://cloudinary.com/documentation/llms.txt
> Use this file to discover all available pages before exploring further.

# Why is an old image/video still showing in my site after I replaced it with a new one?

When you overwrite an existing asset with a new file that has the same public ID, your Cloudinary account is updated with the new file. The first time you request a specific URL for that asset, it will be generated using the latest version of the image or video.

However, if a specific URL using that asset was already in use in your application or website, you may still see a CDN cached version of the previous version instead of the new, updated media asset. It's also possible that your browser or another third-party cache has stored the previous file generated from the URL and is still showing it to you.

To successfully display the new asset to your users for an existing URL transformation, you can use one of two methods:

* **Invalidate CDN cache**: Use the `invalidate` parameter during an `upload` or `explicit` API call to clear any cache for the overwritten asset on the CDN. This parameter is sent automatically if you replace an asset using the Console Media Library. For details, see [Upload API documentation](invalidate_cached_media_assets_on_the_cdn).
* **Bypass browser and other caches**: Use the optional [version](image_transformations#asset_versions) component as part of your asset delivery URLs to ensure the latest version is always delivered. You can retrieve the asset version from the upload response and then apply it to all transformations in your app that use that asset. 
> **NOTE**: :no-title

**← View all [Onboarding FAQ questions](developer_onboarding_faq)**