this post was submitted on 11 Mar 2025
80 points (98.8% liked)

Godot

6400 readers
21 users here now

Welcome to the programming.dev Godot community!

This is a place where you can discuss about anything relating to the Godot game engine. Feel free to ask questions, post tutorials, show off your godot game, etc.

Make sure to follow the Godot CoC while chatting

We have a matrix room that can be used for chatting with other members of the community here

Links

Other Communities

Rules

We have a four strike system in this community where you get warned the first time you break a rule, then given a week ban, then given a year ban, then a permanent ban. Certain actions may bypass this and go straight to permanent ban if severe enough and done with malicious intent

Wormhole

!roguelikedev@programming.dev

Credits

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
Feyter@programming.dev
80
How to Minify Godot's Build Size (93MB --> 6.4MB exe) (popcar.bearblog.dev)
submitted 2 days ago by popcar2@programming.dev to c/godot@programming.dev
12 comments fedilink hide all child comments
 

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 are viewing a single comment's thread
view the rest of the comments
[–] insomniac_lemon@lemmy.cafe 2 points 1 day ago* (last edited 2 hours ago)

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.