Low poly assets for mobile games: budgets that hold up

Triangles are only one of four budgets

On mobile, a scene can be well under its triangle budget and still stutter. Four things compete for the phone's limited power:

1. Triangles (vertex processing).
2. Draw calls (how many separate objects and materials the CPU submits).
3. Texture memory (how much image data sits in RAM).
4. Fill rate and overdraw (how many pixels are drawn, especially with transparency).

Low poly art helps with the first. The other three depend on how you build and organise the assets.

Set budgets on real hardware

Don't trust desktop previews. Pick the weakest device you'll support, build a test scene that represents your heaviest view, and profile it with the engine's tools (Unity Profiler, Unreal Insights, Godot's Monitors). Find the point where frame time breaks your target, then budget below it. The method in what's a good poly count for game assets works the same way on mobile; the numbers are just smaller.

Triangles

• Spend them on silhouettes, not flat surfaces.
• Give repeated props the smallest counts.
• Use LODs for anything that's sometimes far away.
• Check generated models before import. Vi3W retopologises every model, but check the count against your mobile budget and reduce further if needed (decimate vs retopology).

Draw calls

Every unique mesh-and-material combination can cost a draw call. Twenty props with twenty different materials can cost more than one detailed building.

• Share materials. Low poly games can often use one or two materials for most of the world.
• Use a palette texture or atlas so many models use one material. Texture low poly models with a colour palette shows how.
• Batch and instance static and repeated objects using the engine's built-in features.
• Merge small static props that are always together.

Texture memory

• Right-size textures. A small prop rarely needs more than a small texture. Generated textures often come at a high resolution by default; scale them down for mobile.
• Use compressed formats the platform supports (the engine handles this on import; check the settings).
• Palette textures for stylised games can be tiny, a few pixels per colour.
• Fewer maps. Flat-shaded low poly may not need normal or roughness maps at all.

Overdraw and transparency

• Avoid large transparent or alpha-blended surfaces like big glass panes, fog sheets and foliage cards stacked deep.
• Prefer alpha-tested (cutout) to alpha-blended where you need holes.
• Keep particles small and few.

A mobile asset checklist

1. Triangle count within the per-asset budget.
2. Uses a shared material or atlas where possible.
3. Texture resolution matched to on-screen size.
4. No unnecessary maps.
5. LODs for repeated or distant assets.
6. No large transparent surfaces.
7. Tested on the lowest supported device.

Generated assets on mobile

AI generation is a good fit for mobile's stylised look, as long as you treat the output as a starting point for a mobile asset: check the count, downsize textures, and re-texture to a shared palette where possible. That last step does more for mobile performance than any polygon reduction, because it collapses many materials into one.

Building for phones? Generate your props in Vi3W, then put each one through the checklist before it goes in.