MobileReady — mobile game asset optimization for Blender

Ship assets that actually run on phones. Polygon budgets, LOD generation, draw call estimation, VRAM profiling, bone cleanup and texture optimization — all inside Blender.

The problem

Mobile GPUs are not desktop GPUs. Every triangle, every draw call, every megabyte of VRAM matters. Yet most artists work blind: model in Blender, export to the engine, hit play, and discover 12 FPS on a mid-range Android phone.

• Too many polygons — characters at 50 000 triangles that should be 5 000.
• Too many draw calls — dozens of materials where three would do.
• VRAM blown — uncompressed 4K textures on a device with 2 GB shared.
• Skeleton issues — eight bone influences per vertex on hardware that supports four.
• No LODs — full-detail meshes drawn at every distance.

You find out after the scene is built. Then it is hours of rework.

Polygon budgets with a viewport heatmap

Set a triangle budget per object and see compliance at a glance: green under 75 % of budget, yellow approaching the limit, red over it. The problem objects show themselves the moment they exist.

LOD generation with mobile presets

One-click LOD chains tuned to real mobile budgets — Character 5 000 / 2 500 / 1 000 / 500, Prop 2 000 / 1 000 / 500 / 200, Environment 10 000 / 5 000 / 2 000 / 1 000. Each level is named (_LOD0, _LOD1 and so on) and parented for a clean hierarchy. Custom targets are supported.

Draw call estimation

See how many draw calls your scene or selection will produce at runtime, with a per-material breakdown showing the expensive ones and how many calls you would save by combining materials.

Texture memory calculator

Know your VRAM footprint before you export. Compressed sizes for ASTC 4×4, 6×6 and 8×8, ETC2 RGB and RGBA, PVRTC 4bpp and 2bpp, and uncompressed as a baseline — including the mipmap chain, and a resolution override so you can see exactly what dropping 2048 to 1024 saves.

Bone influence checker

Most mobile GPUs and engines support four bone influences per vertex. MobileReady scans every vertex, flags the ones over the limit, cleans the excess in one click keeping the heaviest weights, and re-normalises what remains to sum to one.

Channel packing and atlasing

Pack metallic, roughness, AO and any mask into a single RGBA texture — fewer texture samples, better GPU performance — using the source textures from your material nodes. Combine textures from several objects into shared atlases with full PBR support (albedo, normal, ORM, emission): fewer materials, fewer draw calls.

Before and after

An example mobile RPG village scene with 23 unique assets: draw calls 87 to 12, texture VRAM 248 MB to 31 MB, triangles 412 000 to 68 000, bone influence violations 1 340 vertices to zero, estimated frame rate on a mid-range device about 14 FPS to about 55 FPS.

Who it is for

• Mobile game developers building for Android and iOS.
• Artists making assets for mobile titles against strict budgets.
• Indie studios without a separate technical-art pipeline.
• Anyone targeting WebGL, VR and AR, or low-end hardware.

Compatibility

• Blender 3.0 and newer.
• Windows, macOS, Linux.
• Works with any export format — FBX, glTF, OBJ.
• Unity, Unreal Engine, Godot, and any engine that imports standard mesh data.

How to use

1. Install the add-on through Preferences, Add-ons, Install from Disk.
2. Press N in the 3D Viewport and open the MobileReady tab.
3. Select your objects and use any panel: polygon budget, LOD, draw calls, texture memory, bones, channel packing or atlas.
4. Review the analysis, apply the fixes, export the optimized assets.