4d ago

How to Minify Godot's Build Size (93MB --> 6.4MB exe)

popcar.bearblog.dev How to Minify Godot's Build Size (93MB -> 6.4MB exe)

A quick guide on how to dramatically reduce Godot's export sizes for your game/app!

This was a fun one. Here's my newest post on how to dramatically reduce Godot's build size.

Some sacrifices were made... But the end result is a Godot project that works exactly the same, albeit with slightly worse performance. Hope this can help others in achieving tiny build sizes!

You're viewing a single thread.

13 comments

But, why?
100mb are already negligible. I want a reasonable size (less 20GB) and ok performance.
- @Gladaed @popcar2 because every bloated 100gb game is a mix of a thousand different assets/executables/libraries where the developer thought "why optimize, 100MB is nothing".
  Often with little more than symbol stripping, removing unneeded files, and basic lz compression you can cut most game sizes in half, reduce load times, and free up terabytes of space on your system.
  
  because every bloated 100gb game is a mix of a thousand different assets/executables/libraries
  Also needlessly uncompressed audio or poorly compressed video (that likely could instead be in-engine) particularly when multiple resolutions are needed. Sometimes one of these might be the bigger issue, particularly with remasters.
  @Gladaed I have less-than-stellar internet (~6mb/s, shared with others), 20GB is definitely not a reasonable size for me. 100MiB is fine, but not negligible. Consider also storage space, particularly because users will run games from slower(->cheaper) drives when they deem games too big (which for me is already at 1GiB+, at least in terms of having a library because that adds up).
  and I live in the US, not even in the woods! The price isn't even great, either.
  As I see it, data size is an inverse multiplier for viability. The smaller a download is the more likely that users will be able to get and store it (long-term even) without issue. The difference between a day and an hour is huge, the difference between an hour and 5 minutes is still worthwhile (especially if this impacts household internet speed). Less than that (nearing instant download) is peak.
  Updates also make this difference larger.
  EDIT: A better way to say this is that this probably makes a lot of sense for small developers to do in stable releases at-very-least. Even then I could see picking-and-choosing for all sorts of different reasons. If this is part of an export script I could see it being practically free minus a slightly longer build time that is probably still in an acceptable range.
- @Gladaed @popcar2 web, mobile, and as always, less space and optimization is always a good thing.
  
  Wasting time on metrics that don't matter is waste. I get and agree with mobile/web constraints. I did not consider them.
- The article begins by talking about web exports. The default there is 42MB, which is kind of a lot for the web
  Edit: Of course, compressed it is ~9, which isn't so bad, I suppose.
- For mobile this is a legit difference imo
  Also what raptor said.
- @Gladaed @popcar2
  See https://mastodon.gamedev.place/@popcar2/114144232496373416

13 comments