# Motoko WASM size diagnosing tips?

**URL:** <https://forum.dfinity.org/t/motoko-wasm-size-diagnosing-tips/25268>\
**Category:** Motoko\
**Created:** [December 4, 2023, 6:59pm UTC](https://forum.dfinity.org/t/motoko-wasm-size-diagnosing-tips/25268 "2023-12-04T18:59:18Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Gekctek](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/gekctek/32/6863_2.png) [@Gekctek](https://forum.dfinity.org/u/Gekctek)\
**Post date:** [December 4, 2023, 7:35pm UTC](https://forum.dfinity.org/t/motoko-wasm-size-diagnosing-tips/25268/3 "2023-12-04T19:35:10Z")

</div>

Seems with my specific issue is that I am including multiple actor classes which end up being ~500KB in size each.  
Made a new thread for that

> [@Motoko actor class deployment options](https://forum.dfinity.org/t/motoko-actor-class-deployment-options/25271):
>
> I have an issue where I have a few actor classes that I want to deploy from my main canister but I am running into an issue where each actor class takes about ~500KB of WASM space, so im looking into alternative options. Here is what I see as options Spread out the actor classes to other canister(s) Deploy actor classes from dfx (This might have an issue of not being deployable via a DAO) ? Any help or suggestions would be appreciated

But still interested in the original question about how to figure this out easier

---

_[View the full topic](https://forum.dfinity.org/t/motoko-wasm-size-diagnosing-tips/25268)._