How do I analyze what's driving the build size? (code)

Unity Engine
, , , , , ,
1

I’m looking to understand what’s driving the binary and wasm size of our build.

Our WASM currently sits at about ~10MB compressed, but it has grown over time from version to version.

I’m looking for a way to understand what code files are included in the WASM and mobile builds (Android/iOS), but most build reporting tools focus on assets usage.

What’s the best way to go about mapping the code that contributes to the build size?

2

if you look in your editor.log file, you see a build breakdown, there are also assets that pull that out of there…

1 Like
3

So I can safely assume that everything in the build report went into the final build?
e.g., if I’ve got files from “some package X for platform Y” even though I’m building for platform Z, that means the packages is taking up space in my deployed build?