Pack Distribution

Compile and encrypt your components for distribution

This section covers everything you need to know about preparing your components for release. Whether you’re sharing your work with clients or publishing it on the Marketplace, it’s essential to package and protect your components correctly.

You’ll learn the difference between Dev Packs and Element Packs, how to compile and encrypt your components, and why only compiled Element Packs should ever be distributed.

Element Dev Packs

Element Dev Packs are for internal use only. Do not distribute or sell them.

An Element Dev Pack (.devpack) is designed strictly for local development. These are uncompiled and unencrypted versions of your components that allow for live editing and testing during development.

Every file inside a Dev Pack is actively monitored by Elements and the system, which enables real-time updates as you work in third-party editors, a huge benefit while building components.

However, this live monitoring comes at a cost. If too many Dev Packs accumulate over time, Elements (and macOS) can run out of file handles, leading to components failing to load or update. To avoid performance issues and ensure system stability, Dev Packs must never be shared or sold.

That said, Dev Packs are fine for internal use. If you’re collaborating with a small team, doing client work, or running a closed beta, it’s okay to share Dev Packs privately for testing and feedback. Just be mindful that these packs aren’t encrypted or optimised, and should never be used as a final delivery format.

Before distribution, all Dev Packs must be compiled and encrypted into standard .elementpack files. This process protects your code, improves load times (down from seconds to milliseconds), and ensures the pack is safe and optimised for use by others.

🚫 What Dev Packs Are Not For:

• 🛒 Selling or distributing – Never share Dev Packs via the Marketplace or with paying customers.

• 🌍 Public release – They’re not suitable for general distribution or production use.

• 🔐 Protecting your code – They are unencrypted and expose all your source files.

• ⚠️ Performance-sensitive – Too many Dev Packs can degrade performance or cause Elements to fail.

• 📦 Final deliverables – Always compile and export an .elementpack for finished work.

✅ What Dev Packs Are For:

• 🔧 Local development – Build and test your components live inside Elements.

• ✏️ Live editing – Make changes in your code editor and see instant updates without restarting Elements.

• 🧪 Internal testing – Use Dev Packs to test components within your team before compiling.

• 🧍‍♂️ Client work – Develop custom components for client projects during the build phase.

• 🧑‍💻 Closed beta testing – Share with a small group of testers for feedback before final release.

• 🔄 Rapid iteration – Quickly make and preview updates without going through the compile/export step.

⚠️ Do not distribute Dev Packs to Customers:

As stated above, you first need to compile your dev pack into an Element Pack before it's distributed. Here's a list of the high-level reasons why this is important:

• 🔓 Unencrypted & Uncompiled – Dev Packs contain raw, human-readable code that exposes your component logic and assets.

• 📉 Performance impact – Every file in a Dev Pack is actively monitored by the system, which can slow down Elements and cause issues if too many are installed.

• 🧪 Development-only – Dev Packs are designed for local testing and live updates, not end-user use.

• 🚫 System instability – Excessive Dev Packs can exhaust macOS file handles, leading to components failing to load or update.

• 🔐 Security risk – Distributing uncompiled packs could inadvertently leak sensitive or proprietary code.

• 💥 Unsupported usage – Distributing Dev Packs outside of local development is explicitly not supported.

Element Packs

Compiled Element Packs are intended for distribution and sale.

An Element Pack is a compiled and encrypted version of your component. It contains only the essential files, optimised for performance and security. These packs are what you’ll use when sharing or selling your work via the Marketplace or elsewhere.

Information on converting your Dev Pack into a distributable Element Pack will be available soon.

✅ What Element Packs Are For:

• 🛒 Selling your work – Use Element Packs to distribute components on the Marketplace

• 🔐 Protecting your code – Element Packs are compiled and encrypted to prevent reverse engineering.

• 🚀 Fast performance – Optimised for speed, they load instantly inside Elements.

• 🧑‍💻 Final production use – Only compiled Element Packs should be installed by end users.

---

I you need a help while developing your next great addon for Elements or you have questions about distribution, Please visit the Support Form.