# Theme Lock against changes

**URL:** <https://forums.realmacsoftware.com/t/theme-lock-against-changes/46841>\
**Category:** Elements\
**Created:** [March 23, 2025, 6:03pm UTC](https://forums.realmacsoftware.com/t/theme-lock-against-changes/46841 "2025-03-23T18:03:26Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Beblebroks](https://avatars.discourse-cdn.com/v4/letter/b/db5fbb/32.png) [@Beblebroks](https://forums.realmacsoftware.com/u/Beblebroks)\
**Post date:** [March 23, 2025, 6:03pm UTC](https://forums.realmacsoftware.com/t/theme-lock-against-changes/46841/1 "2025-03-23T18:03:26Z")

</div>

Hi

I know that the delivered themes from Elements are not changeable do to the fact that they are encrypted in the library folder.

Is there an option maybe in the props for own themes to do the same? Would be just nice to have an option not to change the theme by accident.

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [March 24, 2025, 10:16am UTC](https://forums.realmacsoftware.com/t/theme-lock-against-changes/46841/2 "2025-03-24T10:16:07Z")

</div>

This will all be part of our distribution system. Once you’ve built your Devpack, you’ll be able to encrypt it ready for distribution.

It will encrypt everything inside, including, Themes, Components, and Templates.

They will be part of Elements in an upcoming build as we near a 1.0 launch 🙏

---

<div class="post-metadata">

**Author:** ![Beblebroks](https://avatars.discourse-cdn.com/v4/letter/b/db5fbb/32.png) [@Beblebroks](https://forums.realmacsoftware.com/u/Beblebroks)\
**Post date:** [March 24, 2025, 10:41am UTC](https://forums.realmacsoftware.com/t/theme-lock-against-changes/46841/3 "2025-03-24T10:41:08Z")

</div>

But that would mean I would need to distribute also my private devpacks. That I do not want to sell 😃

Thats why I was curious about it.

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [March 24, 2025, 10:47am UTC](https://forums.realmacsoftware.com/t/theme-lock-against-changes/46841/4 "2025-03-24T10:47:16Z")

</div>

Ah yes, I see… we’ll have a think on that 🤔

---

<div class="post-metadata">

**Author:** ![Beblebroks](https://avatars.discourse-cdn.com/v4/letter/b/db5fbb/32.png) [@Beblebroks](https://forums.realmacsoftware.com/u/Beblebroks)\
**Post date:** [March 24, 2025, 12:07pm UTC](https://forums.realmacsoftware.com/t/theme-lock-against-changes/46841/5 "2025-03-24T12:07:04Z")

</div>

Could be a prop in the info.json. If its set not changes can be done and while developing it it could be unset. That could be handy. But yeah just an idea 😃

---

<div class="post-metadata">

**Author:** ![logrunner](https://avatars.discourse-cdn.com/v4/letter/l/59ef9b/32.png) [@logrunner](https://forums.realmacsoftware.com/u/logrunner)\
**Post date:** [April 14, 2025, 3:46pm UTC](https://forums.realmacsoftware.com/t/theme-lock-against-changes/46841/6 "2025-04-14T15:46:31Z")

</div>

Hi @dan  
How far are we away timewise from being to encrypt DevPacks?