# Image Processing Outside Folder

**URL:** <https://discourse.gohugo.io/t/image-processing-outside-folder/9887>\
**Category:** support\
**Created:** [January 7, 2018, 3:25am UTC](https://discourse.gohugo.io/t/image-processing-outside-folder/9887 "2018-01-07T03:25:10Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![alexandros](https://avatars.discourse-cdn.com/v4/letter/a/ecc23a/32.png) [@alexandros](https://discourse.gohugo.io/u/alexandros)\
**Post date:** [January 13, 2018, 2:24pm UTC](https://discourse.gohugo.io/t/image-processing-outside-folder/9887/25 "2018-01-13T14:24:30Z")

</div>

I am replying to myself here.

Because I’ve just tested @talves [Github repo](https://github.com/talves/hugo-resource-images) and changed the media folder into a symbolic link under `/content/` while the original folder is under `/static/`

It works all right. But the interesting part is that Hugo thinks of the symbolic link as a section.

So `/media/` does have its own URL and its contents are rendered even when under `/static/` or even `/data/`.

Now that’s interesting.

There is a[known hack](https://discourse.gohugo.io/t/would-like-to-ignorefiles-but-use-the-underlying-content/6368/10?) to disable a section’s output and naturally I’ve tried it with this /media/ folder workaround.

I’m happy to report that with the above hack `/media/`no longer renders as a section and at the same time its contents are available for `.Resources`

Of course as @bep said everything will be improved if issue [#3612](https://github.com/gohugoio/hugo/issues/3612) is resolved.

But this looks like a very promising technique since it opens up Image Processing beyond Page Bundles.

---

_[View the full topic](https://discourse.gohugo.io/t/image-processing-outside-folder/9887)._