# \[FEATURE\] SVG custom icons

**URL:** <https://forum.inductiveautomation.com/t/feature-svg-custom-icons/22913>\
**Category:** Ignition Early Access\
**Created:** [February 27, 2019, 8:32am UTC](https://forum.inductiveautomation.com/t/feature-svg-custom-icons/22913 "2019-02-27T08:32:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrea.morando](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/andrea.morando/32/8039_2.png) [@andrea.morando](https://forum.inductiveautomation.com/u/andrea.morando)\
**Post date:** [February 27, 2019, 8:32am UTC](https://forum.inductiveautomation.com/t/feature-svg-custom-icons/22913/1 "2019-02-27T08:32:45Z")

</div>

Hi,  
I am currently using the **b2019021902** build.  
I need to manage custom SVG icons library. I know there is a “material.svg” file inside the path “\data\modules\com.inductiveautomation.perspective\icons”: I like so much this approach and I would like to personalize some icons in a dedicated library.  
As a workaround, I created a “myIcons.svg” inside the same folder and it works fine.  
Nevertheless, I am wondering if it is possible to have the icons as project resources (i.e. inside the new data/projects path). In this way, I could version also the icons and transfer easily all the project resources form a gateway to another.  
What do you think about?

Thank you,  
Andrea

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [February 27, 2019, 4:01pm UTC](https://forum.inductiveautomation.com/t/feature-svg-custom-icons/22913/2 "2019-02-27T16:01:22Z")

</div>

You should still be able to version the icons in the current location by simply renaming the relevant library (myIconsv1.svg, myIconsv2.svg), while leaving them available to ALL projects.

Moving them to the data/projects directory would make them unavailable to other projects.
