Unity 6000.0.28
Why is the splash screen included in the build? That’s like the biggest texture in my build and increases build size, not ideal for WebGL builds when you want to optimize the load time.
Also the splashscreen is disabled
Uncompressed usage by category ..
The build report reports uncompressed sizes! Easily overlooked, keeps causing concerns and confusion. 
The logo isn’t actually consuming 2.7 mb in your build, it’s more likely around 100 kb. And with the logo disabled I would expect it not to be loaded thus not consuming memory nor CPU time and not slowing down app load time. So the extra 100 kb is just on your end when you upload the build respectively it’ll be a very minor contribution to the server’s disk space usage.
The actual build size (folder size on disk) is what matters when measuring how big the build is. Check how much this differs from the reported 46.8 mb build size.
Sounds good, but there’s still probably no reason to include it in build when disabled i think.
3 Likes
Not a solution, cause question was why this logo included in build at all, not your rate is it big or not for WebGL build.
1 Like
- Enable “Show Splash Screen”,
- Disable “Show Unity Logo”,
- Disable “Show Splash Screen”,
- Make build
6 Likes
This fixes it, thank you!
Really strange that a HIDDEN field (Show Unity Logo) has any impact on the build. Seems like UX issue from Unity. Disabling Show Splash Screen should also disable Show Unity Logo…
1 Like
Wow, thanks for that.
Sounds very similar to what happened with fog when they removed the Enable Mobile Fog setting coming from Unity4 to Unity5: if you had it disabled, you lost the ability to enable it, and it would override the basic fog setting, making that disabled.
You could only re-enable it by hand-editing the ProjectSettings.asset file.
1 Like