# How to save the uploaded file in default image folder (/system/images/)?

**URL:** <https://forum.inductiveautomation.com/t/how-to-save-the-uploaded-file-in-default-image-folder-system-images/32771>\
**Category:** General Discussion\
**Tags:** perspective\
**Created:** [March 3, 2020, 3:47pm UTC](https://forum.inductiveautomation.com/t/how-to-save-the-uploaded-file-in-default-image-folder-system-images/32771 "2020-03-03T15:47:48Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [July 13, 2021, 3:39pm UTC](https://forum.inductiveautomation.com/t/how-to-save-the-uploaded-file-in-default-image-folder-system-images/32771/11 "2021-07-13T15:39:06Z")

</div>

> [@jsalas](#):
>
> Why is this considered ‘unsupported’? Are there any drawbacks to this approach, i.e. using too many of the Gateway’s resources?

It's unsupported, because if you use it and something goes wrong, you're on your own. We never explicitly set out to make the webserver/webapps/main path automatically hosted - it's just a coincidence of the way we set up Jetty. Some future upgrade of Jetty may make that work differently, or we could explicitly gate the feature behind a config flag, or something.

In practice, because it's such an open secret, we'd probably take pains to prevent anything from breaking it upon such a hypothetical Jetty upgrade, but the reason we claim it's 'unsupported' is because you're basically relying on undefined Jetty behavior, not anything coded into Ignition deliberately.

---

_[View the full topic](https://forum.inductiveautomation.com/t/how-to-save-the-uploaded-file-in-default-image-folder-system-images/32771)._