> ## 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.

# How to update an already fetched asset?



When you fetch an asset, it's cached in your Cloudinary product environment for performance reasons. If you the original asset at the remote source is later updated, you can invalidate the cached asset and re-fetch it when the URL is next requested in one of the following ways:

* Through the Console UI, you can delete the asset from the Media Library. This will automatically invalidate it on the CDN, and it will be re-fetched when the URL is next requested.
* Using the API, you can call the [explicit method](image_upload_api_reference#explicit_method) with the public ID (the remote asset URL) and set the `invalidate` flag to `"true"`. For example, using the Node SDK:

```nodejs
cloudinary.uploader.explicit(
  "URL", 
  { type: "fetch", invalidate: true }, 
  function(result) { console.log(result) }
  );
```

* Using the API, you can also call the [destroy method](image_upload_api_reference#destroy_method) with the public ID (the remote asset URL in this case) and set the `invalidate` flag to `"true"`:

```nodejs
cloudinary.v2.uploader.destroy(
  "URL", 
  { type: "fetch", invalidate: true }
)
.then(callback);
```

> **NOTES**: The CDN may take a few minutes to fully propagate the purge and display the updated asset.