# Packaging a module

**URL:** <https://discourse.slicer.org/t/packaging-a-module/15107>\
**Category:** Development\
**Created:** [December 17, 2020, 8:03am UTC](https://discourse.slicer.org/t/packaging-a-module/15107 "2020-12-17T08:03:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jrl](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@jrl](https://discourse.slicer.org/u/jrl)\
**Post date:** [December 17, 2020, 8:03am UTC](https://discourse.slicer.org/t/packaging-a-module/15107/1 "2020-12-17T08:03:01Z")

</div>

This is more of a clarification question. If I created a module and wanted to pass that on to somebody, do I just “create installer package”? It’s unclear to me how to package the code for another person.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [December 19, 2020, 6:37am UTC](https://discourse.slicer.org/t/packaging-a-module/15107/2 "2020-12-19T06:37:33Z")

</div>

If you build Slicer then you can build an extension package (zip file) that users can install from file using the extensions manager in Slicer.

If you don’t want to build Slicer then the user needs to add your module folder to additional module paths in menu: Application settings / Modules.
