How many polygons should a 3D model have?

A close-up character, a hundred background objects and a single product in a web viewer use resources differently. Giving them the same polygon limit does not guarantee the same performance.

Start with how the model will be used, then establish a budget the team can test.

Define what the number counts

A modelling application may count quads or other polygons, while the exported triangle count differs. State whether the limit applies to one object, each level of detail or the entire visible scene.

Unity notes that appropriate geometry depends on visual quality and platform. Its guidance also explains that UV seams and hard edges can increase processed vertices. One counter cannot describe the complete rendering workload.

Start with frame time

Divide 1,000 milliseconds by the target frame rate to calculate the available frame interval.

The mesh does not own all that time. Logic, animation, physics, interface and other work also contribute. CPU and GPU execution can overlap, so use the engine's profiler to identify the bottleneck.

Measure more than triangles

A 40,000-triangle mesh with one material is not necessarily faster than a 15,000-triangle mesh with six materials. It depends on the device and the workload limiting the scene.

Establish a useful limit

Build a test scene with the expected camera, lighting and object count. Include a demanding but realistic case instead of measuring only the isolated asset.

Profile on the target device and change one variable at a time. If reducing geometry barely changes frame time, investigate further before sacrificing the silhouette. If geometry dominates, try simplification or detail levels appropriate to screen size.

Leave room for the rest of the project and record the measured configuration. The resulting budget is specific to that context and should be revisited if the scene changes.

Make acceptance verifiable

A useful specification states platform, test camera, triangles per detail level, materials, textures, scale and format. Include a visual criterion: meeting the counter while damaging the silhouette is still a failed result.

Unreal Engine's Data Validation framework supports custom asset checks. Automating names, dependencies and agreed limits can reduce repeated errors, but the rules must be implemented and complemented by visual review and profiling.

For outsourced art, agree on these requirements before production. To define them for your project, tell us the target platform and scene.