<p>As pointed out on the official Discord by a Gentleman named &quot;Thanasis Psarros&quot; the following general configuration enables this feature:</p>
<p><a href="https://craftcms.com/docs/5.x/reference/config/general.html#revasseturls" rel="nofollow noreferrer">https://craftcms.com/docs/5.x/reference/config/general.html#revasseturls</a></p>
<p>(maybe their are some downsides to this that we did not notice right now)</p>

CC BY-SA 4.0
2024-04-18T06:43:49.373Z
2024-04-18T06:43:49.373Z
Leonardo
<p>Craft's native transform URLs doesn't include any information about the focal point, which means that updating the focal point will not result in the final transform URL being changed, and browser caches might serve up previously generated transforms for returning visitors.</p>
<p>The <a href="https://craftcms.com/docs/5.x/reference/config/general.html#revasseturls" rel="nofollow noreferrer"><code>revAssetUrls</code></a> setting offers a solution to the problem by adding a modified timestamp to all asset URLs.</p>
<p>Another solution is to eschew Craft's native transforms for the <a href="https://plugins.craftcms.com/imager-x" rel="nofollow noreferrer">Imager X</a> plugin. Unlike Craft's core transforms, Imager will add information about the asset focal point to its transform URLs, ensuring that the URL changes if and when asset focal points are changed.</p>

CC BY-SA 4.0
2024-04-19T22:33:38.813Z
2024-04-19T22:33:38.813Z
Mats Mikkel Rummelhoff
<p>I have a Question about image transform focal point behavior.</p>
<p>Twig templating or with php. Getting the url of an asset with a transform $asset-&gt;getUrl('transformer')</p>
<p>If i am understanding the documentation correctly and my testing was not faulty. One has to implement caching busting himeself if changing the focal point of an image or changing the transformer settings.
Because the url never changes in both cases, the browser will cache those images and not pull the newly generated ones.
Am i correct on this one or am i missing something?</p>

<cache><image-transforms><craft4><focal-point>
ImageTransform Focal Point Cache Busting
# ImageTransform Focal Point Cache Busting

(Asked by: username_0 on 2024-04-16)

I have a Question about image transform focal point behavior.

Twig templating or with php. Getting the url of an asset with a transform $asset->getUrl('transformer')

If i am understanding the documentation correctly and my testing was not faulty. One has to implement caching busting himeself if changing the focal point of an image or changing the transformer settings.
Because the url never changes in both cases, the browser will cache those images and not pull the newly generated ones.
Am i correct on this one or am i missing something?

**Tags:** cache, image-transforms, craft4, focal-point

---

## 2 answers

### Answer by username_0 on 2024-04-18. Score: 1 | Accepted answer

As pointed out on the official Discord by a Gentleman named "Thanasis Psarros" the following general configuration enables this feature:

<https://craftcms.com/docs/5.x/reference/config/general.html#revasseturls>

(maybe their are some downsides to this that we did not notice right now)


---

### Answer by username_1 on 2024-04-19. Score: 1

Craft's native transform URLs doesn't include any information about the focal point, which means that updating the focal point will not result in the final transform URL being changed, and browser caches might serve up previously generated transforms for returning visitors.

The [`revAssetUrls`](https://craftcms.com/docs/5.x/reference/config/general.html#revasseturls) setting offers a solution to the problem by adding a modified timestamp to all asset URLs.

Another solution is to eschew Craft's native transforms for the [Imager X](https://plugins.craftcms.com/imager-x) plugin. Unlike Craft's core transforms, Imager will add information about the asset focal point to its transform URLs, ensuring that the URL changes if and when asset focal points are changed.


---

