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.

What Are the Typical Game Performance Problems and How Optimization Solves Them?

A project runs smoothly on developer devices. On a five-year-old mid-range Android, it hits 20 fps and overheats after five minutes. On iPhone 11 it maintains 60 fps, but on iPhone XR it drops in heavy scenes. We encounter this every day. Optimization is not a later task—it is an architectural decision from the first commit. With eight years of experience, we have optimized over fifty games, from hypercasual to AAA on consoles. We guarantee: after our audit, you get not just a list of problems, but a concrete plan with measurable goals and deadlines. Order a performance audit — we evaluate your project in three days and show how to reduce draw calls by 40% without losing quality.

How to Profile Game Performance? Tools and Best Practices

Before any optimization, measure. Optimization without profiling is guesswork.

Profile on target hardware, not in the editor. The editor adds overhead — Play Mode numbers are not representative. Distinguish between GPU and CPU bottlenecks: CPU may cause many draw calls or heavy logic, GPU may have complex shaders or overdraw. Unity Documentation: profiling on device is mandatory for mobile games. Typical profiling time for one scenario is five to eight hours, including metrics collection on three to five devices of different generations.

How Does Game Performance Optimization Reduce Draw Calls? Static Batching to SRP Batcher

A draw call is a command from CPU to GPU to “draw this.” Each call has overhead regardless of geometry complexity. On mobile, 200–300 draw calls per frame is typical. The goal is to minimize their number by combining geometry that shares the same material.

Static Batching combines stationary meshes during build. Requirement: Static flag on objects and the same material. Effective for static environments but increases memory usage – the combined mesh is stored separately. In scenes with thousands of static objects, monitor memory via Memory Profiler.

Dynamic Batching combines meshes at runtime with strict limits: fewer than 900 vertex attributes per mesh, same material and scale. In practice, it works only for small objects (particles, UI). Disabled by default in URP – replaced by SRP Batcher.

SRP Batcher is not classic batching – it optimizes CPU overhead when preparing draw calls. Instead of reloading shader uniform data each frame, SRP Batcher caches it in GPU memory and updates only when changed. Draw calls remain the same in number, but each takes less CPU time – sometimes 2–3 times less on render CPU time compared to standard batching. Requirement: shader must be compatible with SRP Batcher (declare per-object properties in UnityPerDraw CBUFFER). Standard URP Lit/Unlit shaders are compatible. Custom ones – check in Material Inspector: SRP Batcher compatible: Yes/No. To enable, ensure the SRP Batcher option is active in URP Asset, and for custom shaders use UNITY_INSTANCING_BUFFER macro and declare per-object properties in CBUFFER_START(UnityPerDraw). After enabling, the RenderLoop.Draw CPU time should decrease in Profiler.

GPU Instancing is for many copies of the same mesh with the same material (trees, grass, NPCs). It sends one draw call with an array of per-instance data. Enable on material: Enable GPU Instancing. Limitation: all instances in one batch must have the same material and mesh. Graphics.DrawMeshInstanced / Graphics.DrawMeshInstancedIndirect enable procedural rendering without GameObject overhead.

The choice of method depends on scenario. Static Batching for static environments. SRP Batcher wins in projects with many unique materials. GPU Instancing is indispensable for mass objects (forests, crowds). Dynamic Batching only for small and rare cases. In practice, we combine all methods, starting with profiling.

For more details on the technology, see Geometry instancing (Wikipedia).

Why Is Memory Optimization Critical for Mobile Games?

Mobile platforms have strict RAM limits. iOS kills apps without warning on memory pressure. Android does similarly with onLowMemory callback. Target budgets: iOS <1 GB for modern devices, <512 MB for iPhone 8/X support; Android <800 MB for broad compatibility (OS uses 400–600 MB). Typical savings after our optimization are 30–50% of RAM while maintaining quality.

Addressables and Asset Bundles: How to Stay Within Budget

Loading everything at startup is unacceptable for large projects. Addressables (a wrapper over Asset Bundles) provide addressable asynchronous asset loading. Explicit unload: Addressables.ReleaseInstance / Addressables.Release. Addressables do not automatically unload assets when objects are destroyed. A common mistake: Addressables.InstantiateAsync in a loop without Release – memory grows until crash. Reference counting: an asset is unloaded only when all its handles are freed. Architectural pattern: a service/manager holds the handle of the loaded asset and releases it during scene transitions.

Groups and Bundle Strategy: group assets by loading logic. For example, all assets of one level in one bundle, shared assets (UI, fonts) in a separate group with Prevent Updates. This strategy saves up to 30% memory.

Texture Memory: Where 70% of RAM Comes From

Textures are the main memory consumer. Analyze via Memory Profiler: All Of Memory -> Texture2D shows the heaviest textures immediately. In practice, we find textures with inflated Max Size (4096 for a mobile icon is a typical mistake). Measures: Mipmap for 3D textures (enable), for UI (disable); Streaming Mipmaps for open world – loads mip levels as camera approaches. A common problem: textures referenced by unused Materials remain in memory – Memory Profiler shows the reference chain. Remove unnecessary materials. After replacing all RGBA32 textures with ASTC 6×6 on Android, savings reach 60% without quality loss.

GC Allocations: How to Eliminate Freezes in Hot Path

C# garbage collector in Unity is stop-the-world. If heap memory is allocated per frame, GC pause causes visible freezes. Goal: zero allocations in hot path (Update, FixedUpdate, render). Typical sources: string concatenation in Update (replace with StringBuilder); LINQ in hot path (manual loops with pre-allocated lists); GetComponent<T>() every frame (cache in Awake/Start); boxing value types when passed as object parameters. After profiling with Unity Profiler, we reduce hot path allocations by 95% – freezes disappear.

How Can LOD and Culling Cut 40% of Draw Calls?

LOD Group switches to simplified geometry as the object moves away from camera. Standard for 3D environment: LOD0 (100% triangles), LOD1 (30–50%), LOD2 (10–15%), Culled. For mobile, set Culled threshold more aggressively – draw less per frame.

Occlusion Culling – Unity does not render objects behind walls. Requires baked occlusion data. For indoor scenes, reduces draw calls by 20–40%.

Frustum Culling works automatically – objects outside camera FOV are not rendered. But the draw call for the check still happens. For scenes with thousands of objects, use custom spatial partitioning (Quadtree, Octree). In one of our projects, implementing occlusion culling and LOD reduced total draw calls from 2800 to 450 on Android.

How to Maintain 72 FPS on Quest 3 with VR Optimization?

VR is a separate class of tasks. Frame rate of 72 or 90 Hz must not be violated, or motion sickness occurs. In addition to standard methods: Single Pass Instanced Rendering – renders both eyes in one pass (halves draw calls); Fixed Foveated Rendering (Quest) – reduces peripheral resolution; Late Latching (Quest 3) – updates controller position as late as possible before rendering; Dynamic Resolution in URP/HDRP – automatically lowers render resolution on fps drops. For Quest, profile via OVR Metrics Tool – displays CPU/GPU time directly in headset. After applying these methods, frame rate on Quest 2 stabilizes at 72 FPS even in scenes with 1.5 million polygons.

What Deliverables Do You Get from Game Performance Optimization? Stages and Timelines

We offer a comprehensive turnkey service. Here is exactly what you receive:

1. Profiling report on target devices – metrics (FPS, draw calls, memory, GC) for 5–7 main scenarios. Delivery: 3–5 business days.
2. Priority action plan – which problems are critical, which can be deferred. Priorities based on impact on gaming experience.
3. Optimization implementation – batching, LOD, Addressables, shaders, occlusion culling. Average implementation cycle: 2–4 weeks.
4. Re-profiling results – measured improvements. Typical FPS increase: 30–60% on mobile devices.
5. Documentation – recommendations for maintenance and further development.
6. Team training – how to prevent regressions. We conduct workshops on profiling and optimization.

Get a consultation – we evaluate your project for free and show the optimization potential. Contact us to learn exact timelines and details for your stack.