Polygon Count Guide — How Many Polys is Too Many?
One of the first questions every new game artist asks is "how many polygons should my asset have?" The honest answer is: it depends. But it depends on specific, learnable things — asset type, target platform, and where the viewer's attention goes. This guide gives you real numbers and the thinking behind them.
Triangles vs Polygons — What Actually Gets Counted
When people say "polygon count" in a game context, they almost always mean triangle count. Game engines convert everything to triangles internally — it's the only shape the GPU's rasterizer works with. A quad (4-sided face) becomes 2 triangles. An n-gon with 6 sides becomes 4 triangles.
This matters because your modelling software might report polygon count in quads. A mesh that reads as 5,000 polygons in Blender could be anywhere from 5,000 to 15,000+ triangles depending on how many quads and n-gons it contains. Always check your triangle count before making decisions about optimisation — it's the number that actually matters at runtime.
Every triangle the GPU renders costs processing time. The more triangles visible on screen simultaneously — across all objects in the scene — the more work the GPU does per frame. Polygon budgets exist so that the total scene triangle count stays within what the target hardware can handle at the desired frame rate.
Triangle Budgets by Asset Type
These are industry-standard triangle ranges for common asset types. They're guidelines — not rules — but they represent what experienced game artists and studios use as starting targets. Mobile budgets are roughly 30–50% of the console/PC values.
| Asset Type | Mobile | Indie / Mid PC | AAA Console / PC |
|---|---|---|---|
| Playable character | 1,500 – 5,000 | 8,000 – 25,000 | 30,000 – 100,000+ |
| NPC / background character | 500 – 2,000 | 3,000 – 10,000 | 10,000 – 30,000 |
| First-person weapon | 500 – 2,000 | 3,000 – 12,000 | 15,000 – 40,000 |
| Third-person weapon / held item | 200 – 800 | 500 – 3,000 | 2,000 – 10,000 |
| Vehicle | 1,000 – 4,000 | 5,000 – 20,000 | 20,000 – 80,000 |
| Large environment prop | 100 – 500 | 300 – 2,000 | 1,000 – 8,000 |
| Small prop / pickup | 50 – 200 | 100 – 600 | 300 – 2,000 |
Platform Differences
The platform your game targets is the biggest factor in how aggressive your polygon budgets need to be. The gap between a high-end PC and a mid-range Android device is enormous — and your asset budgets need to reflect that.
Mobile
Tight budgets. Total visible scene often needs to stay under 100K triangles. Baked lighting only. Texture compression mandatory. Every triangle counts significantly.
PC / Console
Much more headroom. Scenes can comfortably handle 1M–20M+ triangles. Dynamic lighting viable. LODs still important but less critical at all ranges.
VR / AR
Rendered twice per frame — once per eye — at 90fps+. Budget is closer to mobile than PC despite running on PC hardware. Latency is critical.
Web / Browser
Highly variable by device. Target conservatively — keep individual assets under 5,000 tris for broad compatibility across low and high-end machines.
If you're making assets for multiple platforms, always build to the most restrictive target first. It's much easier to add detail to a low-poly mesh for a high-end version than to remove detail from a high-poly mesh for a mobile version.
Where to Spend Your Polygon Budget
Having a polygon budget doesn't mean distributing triangles evenly across the mesh. It means spending them intelligently — concentrating geometry where it has the most visual impact and eliminating it where it doesn't.
Silhouette edges
Curves that define the outline of the object need geometry to look smooth. A cylindrical barrel needs enough edge loops to appear round from any angle — flat sides don't.
Player-facing surfaces
The part of the asset the camera faces most gets the most detail. A first-person weapon's barrel and grip need more geometry than the stock the player rarely sees.
Animation deformation areas
Character joints — elbows, knees, wrists, shoulders — need enough edge loops to deform smoothly during animation without collapsing or pinching.
Flat surfaces
A perfectly flat face only needs two triangles regardless of how large it is. Adding extra edge loops to a flat wall panel is pure waste — the detail should come from textures instead.
Hidden geometry
Faces the player can never see — undersides, interiors of closed objects, surfaces flush against a wall — should be deleted entirely. Free triangles back in the budget.
LODs — How Distance Changes the Budget
Most game engines use a Level of Detail (LOD) system to automatically swap an asset to a lower-polygon version as the player moves further away. An asset that's 50 metres away occupies very few pixels on screen — it doesn't need the same detail as the same asset held in the player's hand.
| LOD Level | Triangle Reduction | When It's Used |
|---|---|---|
| LOD0 — Full detail | 100% (no reduction) | Close range — the version you spend the most time on |
| LOD1 | ~50% reduction | Mid distance — visible but not examined closely |
| LOD2 | ~75% reduction | Far distance — background fill, silhouette only |
| LOD3 / Billboard | ~90%+ reduction or flat quad | Very far distance — trees, rocks, distant props |
When the budget tables in Section 02 list a triangle count, they're referring to LOD0 — your full-detail version. LOD1 and beyond are usually auto-generated by the engine or hand-crafted later in production.
Polygon Count and Trumble
Trumble works with your low-poly mesh — whatever triangle budget you've settled on. The polygon count of your mesh doesn't affect how textures are painted or baked. A 300-triangle prop and a 30,000-triangle character both go through exactly the same Trumble workflow: import, bake, paint, export.
What polygon count does affect is how well your baked normal map compensates for the geometry. A very low-poly mesh with a well-baked normal map can look remarkably close to its high-poly source — the normal map does the work that the missing triangles can't. This is the entire point of the high-to-low workflow.
Transfers high-poly surface detail onto your low-poly UV space. The lower your poly count, the more your normal map needs to do — bake quality matters.
Paint albedo, roughness, metallic, and emissive on your low-poly mesh. Texture detail is independent of polygon count — a 200-tri prop can have a 2048×2048 texture.
Export engine-ready texture packs for Unreal, Unity, or Godot. Your polygon count is handled in the FBX/GLTF — Trumble handles the textures.