Unity Build Size Calculator - Estimate APK, IPA, EXE Size

Why does build size matter?

Install rate: Every MB reduces downloads by ~5%. 500MB vs 100MB = 20% fewer users
Device storage: Mobile devices have limited space. Compete with rival apps
WiFi vs Mobile data: On mobile data, users cancel downloads > 50MB
Store optimization: Google Play/App Store prioritize smaller apps
Boot time: Smaller builds = faster startup loading

Build Size Calculator

Target Platform Select your platform. Values will adapt automatically.

Total Textures (MB) All textures in your project (COMPRESSED). Without mipmaps.

Total Audio (MB) Music, SFX, voices. Already compressed as MP3/OGG.

Meshes and 3D Models (MB) Geometry of all models. Use MeshOptimizer.

Scenes (MB) Serialized scene data (GameObjects, components)

Code and Scripts (MB) .NET assemblies, plugins, libraries

Unity Engine (MB) Runtime, native libraries, dependencies

Compression Techniques

Texture Compression

Mesh Compression

Audio Compression

LZ4 Compression

Asset Bundles (On-demand content)

Engine Stripping

Select the optimizations you are applying

Content in Asset Bundles (MB) This content is downloaded separately. Not included in the base build.

Target Device (Android) Processor architecture. Affects size.

Build Size Analysis

Build Size

0 MB

total size

With Optimizations

0 MB

after applying all

Size Savings

total reduction

Download Time

0 sec

5G/Fast WiFi connection

Breakdown by Category

Category	Original Size	With Compression	% of Total	Reduction Potential

📊 Download Scenarios

5G (500 Mbps) - Ultra fast

Fast WiFi (100 Mbps) - Fast

Mobile 4G (20 Mbps) - Slow

Mobile 3G (5 Mbps) - Very slow

📦 Store Requirements

Store	Recommended Limit	Status	Note

🎯 Optimization Recommendations

📚 Build Size Reduction Guide

Texture Compression: ASTC/ETC2 (mobile), BC1/BC3 (PC). Reduces 70-80% vs RGBA.
Mesh Compression: Enable in Project Settings. Reduces 20-50% depending on precision.
Audio Compression: Vorbis (mobile), WAV (PC). MP3 is legacy.
LZ4 Compression: Enable in Player Settings. 30-40% reduction but more CPU usage at startup.
Asset Bundles: On-demand downloads. Strategy: core gameplay in base build + cosmetic content on demand.
Engine Stripping: Removes unused modules (Physics, Navigation, etc.). Saves 20-100MB.
Managed Code Stripping: Removes unreferenced code. Use Link.xml if you need to preserve dynamic types.
WebGL optimization: Minification, brotli compression. Target WebGL Server.

💡 Pro Tips for Small Builds

🎨 Use procedural generation for content instead of pre-generated assets
📱 Targets: ARMv7 or ARM64 separately (not Universal) for APK. AAB lets Google optimize.
🔗 Link.xml: Specify which code to preserve if using Reflection
🗂️ Categorize assets: critical gameplay in build, rest in bundles
✂️ Remove unused assets: use Asset Browser and Addressables to audit
🎬 Video: Use WebM (VP9) for web, H.264 for mobile
📦 CDN: Host asset bundles on CDN, not on Google Play/App Store