<p>Those folders are created automatically for new <a href="https://craftcms.com/docs/4.x/image-transforms.html" rel="nofollow noreferrer">image transforms</a>. The folder name is derived from the transform size, focus point and cropping method.</p>
<p>Some, maybe all, of the transforms you're seeing are just created by the CP to display as thumbnails or previews of the image in different contexts. For example, the assets lists displays previews in one size, the preview of a linked asset in an asset field in another one.</p>
<p>Other transforms may be created by your frontend templates and/or modules on demand, see the documentation linked above for details.</p>
<blockquote>
<p>Is this supposed to happen, and if so, what is the purpose and what can I do with it?</p>
</blockquote>
<p>You don't need to do anything with it. Transforms and their corresponding folders are created on demand and can be cleared out without problems. They will, however, be recreated the next time those image transforms are requested, so there isn't really a point to doing that.</p>
<p>You should <em>definitely</em> use transforms in your frontend templates to size images according to their function, output sizing and positioning. You never want to send original uploaded image files directly to the end-user, as they will likely be poorly compressed and way larger than they need to be.</p>
<blockquote>
<p>This causes a lot of additional files taking up hard drive space.</p>
</blockquote>
<p>The generated images are mostly small thumbnails, so their file size will be negligible. Furthermore, storage is cheap. If your hosting has a super lower hard drive space limit to the point where this is actually a problem, find a different hosting provider.</p>

CC BY-SA 4.0
2022-08-28T12:43:11.563Z
2022-08-28T12:43:11.563Z
MoritzLost
<p>I am using Craft 4 and I noticed after uploading an asset, additional folders are created automatically with multiple sized versions of the same image I uploaded. This causes a lot of additional files taking up hard drive space.</p>
<p>Here are the list of folders created:</p>
<p><strong>&quot;_34x9_crop_center-center_none&quot;
&quot;_68x18_crop_center-center_none&quot;
&quot;_120x33_crop_center-center_none&quot;
&quot;_240x66_crop_center-center_none&quot;
&quot;_350x96_crop_center-center_none&quot;
&quot;_700x192_crop_center-center_none&quot;
&quot;_1000x275_crop_center-center_none&quot;</strong></p>
<p>Is this supposed to happen, and if so, what is the purpose and what can I do with it?</p>

CC BY-SA 4.0
2022-09-27T20:45:13.900Z
By the way, if anyone stumbles upon this question
In the ImageOptimize plugin, this causes a [problem](https://github.com/nystudio107/craft-imageoptimize/issues/356), as the plugin tries to transform SVG images for thumbnails in the CP
RomanAvr
<assets>
Multiple image are automatically created?
# Multiple image are automatically created?

(Asked by: username_0 on 2022-08-28)

I am using Craft 4 and I noticed after uploading an asset, additional folders are created automatically with multiple sized versions of the same image I uploaded. This causes a lot of additional files taking up hard drive space.

Here are the list of folders created:

**"\_34x9\_crop\_center-center\_none"
"\_68x18\_crop\_center-center\_none"
"\_120x33\_crop\_center-center\_none"
"\_240x66\_crop\_center-center\_none"
"\_350x96\_crop\_center-center\_none"
"\_700x192\_crop\_center-center\_none"
"\_1000x275\_crop\_center-center\_none"**

Is this supposed to happen, and if so, what is the purpose and what can I do with it?

**Tags:** assets
> **Comments:**
> **username_1**: By the way, if anyone stumbles upon this question In the ImageOptimize plugin, this causes a [problem](https://github.com/nystudio107/craft-imageoptimize/issues/356), as the plugin tries to transform SVG images for thumbnails in the CP  

---

## 1 answers

### Answer by username_2 on 2022-08-28. Score: 2

Those folders are created automatically for new [image transforms](https://craftcms.com/docs/4.x/image-transforms.html). The folder name is derived from the transform size, focus point and cropping method.

Some, maybe all, of the transforms you're seeing are just created by the CP to display as thumbnails or previews of the image in different contexts. For example, the assets lists displays previews in one size, the preview of a linked asset in an asset field in another one.

Other transforms may be created by your frontend templates and/or modules on demand, see the documentation linked above for details.

> Is this supposed to happen, and if so, what is the purpose and what can I do with it?

You don't need to do anything with it. Transforms and their corresponding folders are created on demand and can be cleared out without problems. They will, however, be recreated the next time those image transforms are requested, so there isn't really a point to doing that.

You should *definitely* use transforms in your frontend templates to size images according to their function, output sizing and positioning. You never want to send original uploaded image files directly to the end-user, as they will likely be poorly compressed and way larger than they need to be.

> This causes a lot of additional files taking up hard drive space.

The generated images are mostly small thumbnails, so their file size will be negligible. Furthermore, storage is cheap. If your hosting has a super lower hard drive space limit to the point where this is actually a problem, find a different hosting provider.


---

