<p>Asset fields require a transform to be set manually in the template or can be Created in the dashboard and the transform name used in the template.</p>

<pre><code>{% set thumb = {
    mode: 'crop',
    width: 100,
    height: 100,
    quality: 75,
    position: 'top-center'
} %}

&lt;img src="{{ asset.getUrl(thumb) }}"&gt;
</code></pre>

CC BY-SA 4.0
2018-12-22T14:32:10.160Z
Agreed. Where you decide to set the transform, either in the template or in the CP depends on whether you want to store more information in the DB or let the template do the work. I've been putting transforms in templates because it allows me to use the same transform name (eg. myHeaderTransform), but apply different settings in each template.
Vaughn D. Taylor
CC BY-SA 4.0
2018-12-22T16:24:54.807Z
Yes, I understand how to call a transform in a template, but that does not support having the content person apply a transform, without me adding another control field in the CP. In any case, the real issue here is that there is inconsistent user experience between inserting an image using Redactor versus an Asset field.
Roi Agneta
CC BY-SA 4.0
2018-12-22T16:50:54.153Z
Then you can add a field or a few to the asset field layout and the user can set them when adding an asset. Or make it a separate field alongside the assets. I’ll update my answer shortly
Chattervast
CC BY-SA 4.0
2018-12-22T05:19:22.310Z
2018-12-22T05:19:22.310Z
Chattervast
<p>If you insert an image in a Rich Text field you get an option to apply a transform, but that is not true when using an Asset field to choose an image, which seems strange. Is there any way to accomplish that?</p>

<image-transforms><image><assets-field>
Select Transform Feature with Asset Field
# Select Transform Feature with Asset Field

(Asked by: username_0 on 2018-12-22)

If you insert an image in a Rich Text field you get an option to apply a transform, but that is not true when using an Asset field to choose an image, which seems strange. Is there any way to accomplish that?

**Tags:** image-transforms, image, assets-field


---

## 1 answers

### Answer by username_1 on 2018-12-22. Score: 1

Asset fields require a transform to be set manually in the template or can be Created in the dashboard and the transform name used in the template.
{% set thumb = {
    mode: 'crop',
    width: 100,
    height: 100,
    quality: 75,
    position: 'top-center'
} %}

> **Comments:**
> **username_2**: Agreed. Where you decide to set the transform, either in the template or in the CP depends on whether you want to store more information in the DB or let the template do the work. I've been putting transforms in templates because it allows me to use the same transform name (eg. myHeaderTransform), but apply different settings in each template.  
> **username_0**: Yes, I understand how to call a transform in a template, but that does not support having the content person apply a transform, without me adding another control field in the CP. In any case, the real issue here is that there is inconsistent user experience between inserting an image using Redactor versus an Asset field.  
> **username_1**: Then you can add a field or a few to the asset field layout and the user can set them when adding an asset. Or make it a separate field alongside the assets. I’ll update my answer shortly  

---

