<p>You can instruct Craft not to keep a local copy of remote assets by setting the <a href="https://docs.craftcms.com/v2/config-settings.html#maxcachedcloudimagesize" rel="nofollow noreferrer"><code>maxCachedCloudImage</code> config variable</a> to <code>0</code> (zero).</p>

<p>It may be worth experimenting with that setting, to find a balance between caching some smaller images locally (thereby speeding up transformations), and preserving disk space.</p>

CC BY-SA 4.0
2017-06-05T15:11:55.460Z
2020-03-06T09:33:04.410Z
2020-03-06T09:33:04.410Z
Stephen Lewis
<p>I was wondering if someone could help me with the following issue:</p>

<p>I'm saving assets on Amazon S3 and as per Craft's documentation Craft is keeping a copy of remote assets in <code>storage/runtime/assets/sources</code> folder. The issue is that this website has a lot of images and <code>sources</code> folder in storage is taking up a lot of space. It can go up to 5GB.</p>

<p>Is there a way I can tell Craft to not keep a copy of remote assets?</p>

<p>Many thanks</p>

<assets>
Remote assets space issue storage/runtime/assets/sources
# Remote assets space issue storage/runtime/assets/sources

(Asked by: username_0 on 2017-06-05)

I was wondering if someone could help me with the following issue:

I'm saving assets on Amazon S3 and as per Craft's documentation Craft is keeping a copy of remote assets in `storage/runtime/assets/sources` folder. The issue is that this website has a lot of images and `sources` folder in storage is taking up a lot of space. It can go up to 5GB.

Is there a way I can tell Craft to not keep a copy of remote assets?

Many thanks

**Tags:** assets


---

## 1 answers

### Answer by username_1 on 2017-06-05. Score: 3

You can instruct Craft not to keep a local copy of remote assets by setting the [`maxCachedCloudImage` config variable](https://docs.craftcms.com/v2/config-settings.html#maxcachedcloudimagesize) to `0` (zero).

It may be worth experimenting with that setting, to find a balance between caching some smaller images locally (thereby speeding up transformations), and preserving disk space.


---

