Large games are downloaded less often. Many players are on limited data plans or low-storage phones, and some will cancel a download that seems too big. Reducing your Unity build size improves install conversion and can also improve loading times. This guide covers the most effective ways to shrink a Unity mobile build.
Step 1: Find Out What Is Taking Space
After building, open the Editor log (from the Console window menu, choose Open Editor Log). Unity includes a build report listing the size of each asset category and the largest individual files. You can also use the Build Report Inspector package for a more visual breakdown. Always measure before and after changes.
Step 2: Compress Textures
Textures are usually the largest part of a mobile game.
- Use ASTC compression for modern Android and iOS devices, with platform overrides in each texture's import settings.
- Reduce Max Size for textures that never appear large on screen; a background shown at 1080 pixels does not need a 4096 texture.
- Disable Read/Write unless a script needs pixel access.
- Disable mipmaps for UI and 2D sprites that are not scaled down.
- Pack 2D sprites into Sprite Atlases to reduce memory and draw calls.
Step 3: Optimize Audio
- Use Vorbis (Android) or AAC/MP3 style compression for music, and set long tracks to Streaming.
- Force short sound effects to mono when stereo is not noticeable.
- Lower the quality setting for background music; most players will not hear the difference on phone speakers.
Step 4: Remove Unused Assets and Packages
Only assets referenced by scenes in the build, or stored in Resources folders, are included. Move unused files out of Resources folders, because everything there is always included. Remove unused packages in the Package Manager, such as old analytics or test tools, and delete demo scenes that came with plugins.
Step 5: Strip Code
In Player Settings, use IL2CPP and set Managed Stripping Level to Medium or High to remove unused code. Test carefully afterward; if reflection-based code breaks, add a link.xml file to preserve needed types.
Step 6: Use Android App Bundles
When you upload an Android App Bundle, Google Play generates optimized APKs for each device, so players only download the code and resources their device needs. This often reduces download size compared with a universal APK. Also build only the architectures you need, typically ARM64 and ARMv7.
Step 7: Consider Addressables and Asset Delivery
For bigger games, move optional content such as later levels, extra skins or high-resolution assets into Addressables that download after install, or use Play Asset Delivery on Android. The initial download stays small, and players get extra content when they need it.
Step 8: Optimize Meshes and Animations
- Enable mesh compression and remove unused vertex data such as extra UV channels.
- Reduce polygon counts for objects that appear small on screen.
- Compress animation clips and remove unnecessary keyframes.
Step 9: Fonts and Shaders
Font files with large character sets can be heavy; include only the characters and languages you need. Remove unused shader variants with shader stripping settings or by deleting unused materials.
A Realistic Target
For a casual or hyper-casual game, aim to keep the initial download as small as reasonably possible; many successful casual games stay well under 100 MB. Every reduction helps, especially in markets where data is expensive.
Checklist
- Build report reviewed.
- Textures compressed with sensible max sizes.
- Audio compressed and long tracks streamed.
- Resources folders cleaned.
- Code stripping enabled and tested.
- App Bundle uploaded with only needed architectures.
Many source codes in our Store are already optimized for mobile, giving you a lightweight base to build on.
Profile Memory as Well as Size
Download size and memory use are related but different. A small download can still use a lot of memory at runtime if textures are uncompressed in memory or many assets load at once. Use the Unity Profiler and Memory Profiler on a real device to check memory, especially on older phones with limited RAM, where high memory use causes crashes and poor reviews.
Frequently Asked Questions
Why is my empty Unity project already several megabytes?
Every build includes the Unity runtime and required libraries. Code stripping, removing unused packages and building only needed architectures help reduce this baseline.
Does texture compression reduce quality?
Some compression formats introduce small artifacts, but on phone screens the difference is usually invisible. Compare compressed and uncompressed versions and adjust quality settings only for textures where artifacts are noticeable.
Will Addressables make my game harder to manage?
They add some setup and testing work, but for larger games they are worth it. For small casual games, standard texture and audio optimization is usually enough.
Does build size affect store ranking?
Not directly, but smaller games often convert better and have fewer uninstalls, especially in markets with limited storage and data, which can indirectly help.
Comments (0)