<p>Craft doesn't have a setting for defining the transformations image path, they are automatically placed in a subfolder inside your created assets source' path. It could look something like this <code>_960x540_crop_center-center_70</code>, if you had a transform like this:</p>

<pre><code>{ width: 960, height: 540, mode: 'crop', position: 'center-center', quality: 70 }
</code></pre>

<p>By default, the url you're seeing is what Craft will return if the transform hasn’t been generated yet. The next time the page is loaded, it should reference the actual image file. <a href="https://craftcms.stackexchange.com/a/831/141">See Brandon's answer here</a>, for a more thorough explanation.</p>

<p>But, if everything is working, you should see the image in your browser even if it returns the transform url. If the image isn't created, check if the file path for your asset source is correct (guess it is if you can upload images), and that url rewriting is working. </p>

CC BY-SA 3.0
2014-10-20T12:39:07.103Z
Upload path is correct and is writeable as i have been uploading images to that folder quite happily. Subsequent refreshes don't show the image either. Quite the puzzler!
John
CC BY-SA 3.0
2014-10-20T12:42:06.777Z
Aha! The post you reference says to add 'generateTransformsBeforePageLoad' => true to the config and that is what did the trick. Thanks Andre!
John
CC BY-SA 3.0
2014-10-20T13:19:46.530Z
Ok, that setting should just ensure that the image is created before the first page load, so you'll never see that transform url. I prefer this too, but it should work without it unless there's something else that's wrong.
André Elvan
CC BY-SA 3.0
2014-10-20T12:08:48.040Z
2014-10-20T12:08:48.040Z
2017-04-13T12:50:59.930Z
André Elvan
<p>When using image transforms, Craft not only doesn't seem to be outputting the transformed image, but the image path it's then giving back to the template is: <code>&lt;img src="http://example.com/cpresources/transforms/1" /&gt;</code> which doesn't exist.</p>

<p>I have a upload path defined, which is <code>http://example.com/assets/uploads/</code> but obviously it isn't respecting that.</p>

<p>I can't find any docs on where to define the transformations image path so wondered if anyone could shed some light?</p>

<image-transforms>
Set transformations image path
# Set transformations image path

(Asked by: username_0 on 2014-10-20)

When using image transforms, Craft not only doesn't seem to be outputting the transformed image, but the image path it's then giving back to the template is: `![](http://example.com/cpresources/transforms/1)` which doesn't exist.

I have a upload path defined, which is `http://example.com/assets/uploads/` but obviously it isn't respecting that.

I can't find any docs on where to define the transformations image path so wondered if anyone could shed some light?

**Tags:** image-transforms


---

## 1 answers

### Answer by username_1 on 2014-10-20. Score: 4 | Accepted answer

Craft doesn't have a setting for defining the transformations image path, they are automatically placed in a subfolder inside your created assets source' path. It could look something like this _960x540_crop_center-center_70, if you had a transform like this:
{ width: 960, height: 540, mode: 'crop', position: 'center-center', quality: 70 }

By default, the url you're seeing is what Craft will return if the transform hasn’t been generated yet. The next time the page is loaded, it should reference the actual image file. See Brandon's answer here, for a more thorough explanation.
But, if everything is working, you should see the image in your browser even if it returns the transform url. If the image isn't created, check if the file path for your asset source is correct (guess it is if you can upload images), and that url rewriting is working.

> **Comments:**
> **username_0**: Upload path is correct and is writeable as i have been uploading images to that folder quite happily. Subsequent refreshes don't show the image either. Quite the puzzler!  
> **username_0**: Aha! The post you reference says to add 'generateTransformsBeforePageLoad' => true to the config and that is what did the trick. Thanks Andre!  
> **username_1**: Ok, that setting should just ensure that the image is created before the first page load, so you'll never see that transform url. I prefer this too, but it should work without it unless there's something else that's wrong.  

---

