How to Reduce Mobile Game App Size
ملخص
Pixel shares a practical guide to reducing mobile game app size, starting with build reports to identify the largest assets. It covers texture and audio compression, removing unused content, stripping unused engine code, Android App Bundles, and on-demand downloads—helping reduce download friction and update sizes.
DEV Community
How to Reduce Mobile Game App Size: A Practical Guide
The short answer Measure before you cut. In almost every mobile game, textures are the largest share, followed by audio, then meshes, animation, fonts and code. Resize and compress textures, compress audio, delete what is unused, strip engine code you do not call, ship with Android App Bundles and move later content to on-demand download. Those six steps commonly cut a build by a third to a half without visible loss. Why size matters Conversion. Fewer people finish a large download, especially on mobile data or with a nearly full phone. Store behaviour. Stores show download size on the listing and may ask for confirmation before large downloads over mobile data. Markets. In regions with expensive data and entry-level phones, a small build is a competitive advantage. Updates. A large app means large updates, and people postpone them. Ad campaigns. Paid installs that are abandoned mid-download are wasted spend. Step 1: find out what is big Do not guess. After a build, read the engine's build report, which lists every asset and its size after compression. In Unity, the editor log and the build report tools show this, and Android Studio's APK analyser shows the final package contents. Sort by size. The top twenty entries usually account for most of the build, and several will be surprises: a huge background image, an uncompressed music track, a font with every language. Step 2: textures Textures are normally more than half of a mobile game. Action Effect Reduce resolution to what the screen actually shows Halving width and height cuts size by about three quarters Use ASTC compression on modern Android and iOS devices Large savings with adjustable quality Pick block size by importance Higher quality for characters and interface, stronger compression for backgrounds Pack sprites into atlases Fewer files, less wasted padding, fewer draw calls Remove unneeded mipmaps for interface art Saves about a third on those textures Avoid alpha channels where not needed Cheaper formats become available Use tiling textures and tints One texture serves many surfaces Review maximum texture size per platform in import settings. A 4096-pixel texture on a phone is rarely justified. Step 3: audio Compress music and long ambience with a lossy codec at a moderate quality setting. Most players use phone speakers or basic earphones. Convert to mono where stereo adds nothing, such as most sound effects. That halves the data. Lower the sample rate for effects that do not need high frequencies. Stream long tracks instead of loading them into memory. Trim silence at the start and end of clips. Remove alternate takes and unused voice lines. See how video game music is made for how audio is produced and delivered. Step 4: meshes and animation Enable mesh compression and remove unused vertex data such as extra UV sets or colours. Reduce polygon counts for objects seen at a distance, and use levels of detail. Compress animation and reduce keyframes. Remove curves for bones that do not move. Share animation sets between characters on one skeleton. See game animation cost. Step 5: remove what is not used Projects accumulate leftovers. Unused assets. Anything in special always-included folders ships whether referenced or not. Audit those folders first. Duplicates. The same texture bundled into several asset groups is a common cause of bloat. Analysis tools report duplicated dependencies. Test content. Debug scenes, placeholder art and sample scenes from plugins. Fonts. Include only the character sets you need, and consider dynamic or subset fonts for large scripts. See game localization cost. Video. Pre-rendered video is very heavy. Replace with in-engine sequences or stream it. Step 6: code and engine Use the engine's code stripping at the highest level that still works, and test thoroughly, since stripping can remove code reached only through reflection. Build with IL2CPP and target only the processor architectures the stores require. Disable engine modules you...

Powered by Readybot.io