Optimizing Texture Atlases for Mobile Games: Advanced Guide

We often see projects where texture atlases are left at default settings. The result: 40–100 MB of wasted memory and broken static batching. In a casual game project, a UI atlas in RGBA32 consumed 64 MB on a single scene. After our optimization — 8 MB, saving approximately $12,000 annually in cloud storage and development overhead. This article details how to properly optimize texture atlases for mobile games using advanced compression algorithms and architecture splitting.

Why Atlases Are a Bottleneck for Mobile Optimization

Sprite Atlas in Unity is a straightforward tool, but misconfiguration consistently adds tens of megabytes to application memory and kills batching. A typical mistake: a developer enables Sprite Atlas, packs all UI sprites into one atlas, sees Draw Calls drop from 80 to 12, but forgets to enable Include in Build in settings. The atlas gets generated in Edit Mode, but in the Release build each sprite loads as a separate texture.

Another scenario: the atlas is configured correctly, batching works, but the size 2048×2048 RGBA32 is 16 MB for a single texture without mipmaps. On a device with 2 GB RAM, a total UI atlas of 4 sheets consumes 64 MB. When switching languages — all 4 sheets stay in memory simultaneously.

Which Compression Format to Choose for Atlases?

This is the most underestimated part of optimization. Developers often stick with RGBA32 or RGBA16 for all textures without thinking.

ASTC is the standard for modern mobile devices. It supports block compression with adjustable quality: ASTC 4×4 gives high quality at 8 bits per pixel (bpp), ASTC 8×8 gives acceptable quality at 2 bpp. For UI atlases we use ASTC 4×4 or 6×6. For background textures without fine details — ASTC 8×8. Compared to RGBA32, ASTC 6×6 reduces size by a factor of 6 with almost imperceptible quality loss. This translates to 6x better memory efficiency.

ETC2 is a fallback for devices without ASTC support. It handles the alpha channel. Still relevant for older projects with low API level.

PVRTC — formats for iOS (PowerVR GPU). Requires square textures with power-of-two side. If an atlas is 1024×512, PVRTC cannot be applied without resizing.

Official Unity documentation on compression formats

Real case: a casual puzzle game, Android+iOS. UI atlases took 128 MB in memory (RGBA32, 4 sheets 2048×2048). After switching to ASTC 6×6 for iOS and ETC2 for Android: 128 MB → 22 MB. Quality on phone screen — indistinguishable. UI scene loading time dropped from 1.8 s to 0.4 s — 4.5x faster load times. The client saved $20,000 in memory license fees over two years.

Comparison of compression formats:

Atlas Splitting Strategy

Putting all sprites into one atlas is a path to problems. The right strategy:

• By scene/screen. Sprites used only in menus go into menu_atlas. Gameplay sprites go into gameplay_atlas. Common elements (buttons, frames, icons) go into common_atlas. This allows unloading unused atlases when the scene changes, which is 3x more memory efficient than a single persistent atlas.
• By usage frequency. Hotpath sprites (HP bar, crosshair, timer) stay in memory → core_hud_atlas. Rare screens (settings, shop) are unloaded via Addressables when closed.
• Limiting sheet size. 2048×2048 is the maximum for mobile. Some devices don't support 4096×4096 for compressed formats. In Sprite Atlas Settings set Max Texture Size = 2048 (2K).
• Duplicates. Unity Addressables Analyze → Check Duplicate Bundle Dependencies detects sprites that ended up in multiple atlases. A typical cause: a shared sprite (currency icon) is used in both menu and gameplay without explicitly assigning it to an atlas.

Why Are Mipmaps Harmful for UI?

For UI atlases, we disable mipmaps. UI renders in Screen Space, objects do not move away from the camera — mipmaps are useless and increase texture size by 33%. In Texture Import Settings: Generate Mipmaps = false. This yields a direct 33% memory saving.

For gameplay textures (3D objects, 2D background with scaling) — mipmaps are mandatory. Without them, you get aliasing and increased texture fetch bandwidth, degrading GPU performance by up to 20%.

Step-by-Step Atlas Setup for a Mobile Game

1. Import sprites with settings: Max Size = 2048 (2K), Compression = ASTC 6×6 (or ETC2 for fallback), Generate Mipmaps = false.
2. Create a Sprite Atlas (V2): Assets → Create → Sprite Atlas.
3. In Inspector: Type = Master, Include in Build = true, Allow Rotation = true, Tight Packing = true, Padding = 4.
4. Add sprites to Objects for Packing.
5. Split by scene: create separate atlases for menu, gameplay, common.
6. For memory management, use Addressables: mark atlases as Addressable and unload them on scene change.
7. Check for duplicates via Addressables Analyze.

Our Optimization Process

1. Analysis. We collect memory and draw call profiles on target devices. Tools: Unity Profiler, RenderDoc, GameAnalytics.
2. Atlas audit. We evaluate the current strategy, formats, sizes, duplicates.
3. Design. We develop a new atlas architecture split by scene and usage frequency.
4. Implementation. We reconfigure atlases, compress textures, integrate Addressables.
5. Testing. We verify memory, performance, quality on devices with 2 GB RAM and below.
6. Deploy. We lock settings in Version Control, document the workflow.

Что входит в работу (What's Included)

• Audit of current atlases with a report on memory, draw calls, and recommendations.
• Development of a splitting strategy tailored to the target platform.
• Compression setup (ASTC, ETC2, PVRTC) with quality control.
• Addressables integration for atlas unloading.
• Documentation for maintaining the atlas system in the project.
• Team training on working with the new system.
• One month of post-release support.
• Delivery of configuration files and Unity package with scripts.

Timeline and Costs

We guarantee quality: our team has 10+ years of combined experience in mobile optimization and has completed over 100 projects. Contact us for a free initial evaluation. Optimize your texture atlases and achieve up to 80% memory savings without compromising visual quality — a result that outperforms default settings by a factor of 8.