HTML5 build is way too big

Pre-build content folder is 31MB, it’s mostly audio - there’s minimal anything else, including blueprints. I’ve enabled ‘Create compressed cooked packages’ and set to shipping but the after build HTML5 folder is 188MB. I’ve tried to find a simple step by step to reduce the size but can’t seem to get it smaller. Can I zip up anything? I tried to disable all plugins but the builds didn’t work after that - are there required plugins?

Anything I can get rid?

215092-build.png

See this previous conversation on the same question: Size of final package - Platform & Builds - Epic Developer Community Forums. That goes through the gzipping process as well, and switching from .asm to much smaller .wasm.

Does that help?

Thanks juj - that link seems to be broken though, do you know if this info is anywhere else? I completely broke my project by disabling plugins, I couldn’t package for either windows or html! Migrated everything to a new project and can package again. Doesn’t seem to change the size considerably anyway.

It looks like the forum added the ending period after the sentence to the URL, here is the same without the . at the end:

I can’t build as WASM because it’s greyed out - commentary says “This requires GitHub Source” but I’m not sure what to do about that. Also, the build fails with the error " Package Native Shader Library failed for HTML5." when I have Shared Material Native Libraries enabled. Thanks for helping with my other question too, I’ll take another look at that over the weekend :slight_smile:

215170-wasm.png

Oh, it looks like to build Wasm, one needs to rebuild Unreal Engine 4 from scratch from source code available at GitHub. I presume that might be due to something not making it into the UE 4.17 release, and UE 4.18 will have the support in the downloaded version of the editor built-in.

I have UnrealEngine 4.19.2 and even after following the recommendations, and activating wasm and gz, still the build is ~150mb and I am just compiling the plain new project with just the grey platform.
It is hard for end user to wait for a 150mb page all at once, is there a way to, at least, brake it down into several files and download them progressively in browser ?