Polycount Checker

The core confusion is quads versus triangles. Most DCC tools, Blender included, default to showing face count, which counts a quad (a four-sided polygon) as one face even though a GPU always renders it as two triangles internally. A mesh reported as "5,000 faces" in a modeling tool built from quads is therefore actually rendering as roughly 10,000 triangles, and this is exactly why a model can look like it matches a stated budget in your modeling software while running twice as expensive as expected once it hits an engine or a glTF export, where everything gets triangulated regardless of the source topology.

In Blender, enable Viewport Overlays then Statistics to see a live triangle count (labeled Tris) alongside face count in the corner of the 3D viewport, and this is the number that actually matters for a real-time budget, not the Faces line above it. Selecting a specific object and checking the N-panel's Item tab, or using the Mesh Analysis overlay, narrows the count down to just that object rather than the whole scene, which matters when you are checking one prop's budget inside a larger multi-object file.

In Unity, the true rendered triangle count for an imported mesh is mesh.triangles.Length / 3 in code, or visible directly in the Inspector when you select the model's mesh asset and expand the Model Preview panel, which shows both Vertices and Tris for the exact asset that will be drawn, already triangulated regardless of the source FBX or GLB's authoring topology. Godot shows an equivalent count in the MeshInstance3D inspector or via the Debugger's Monitors tab during play, and Unreal exposes it through the Static Mesh Editor's details panel, both post-triangulation just like Unity.

For a raw glTF or GLB file with no engine or DCC tool open, the triangle count is derivable directly from the file's JSON: each mesh primitive's indices accessor count divided by 3 gives the triangle count for that primitive (glTF meshes are required to be pre-triangulated, so there is no quad-vs-triangle ambiguity to resolve at the file level at all), and online glTF viewers like the official glTF Sample Viewer or Don McCurdy's glTF Report display this total automatically without needing to parse the JSON by hand. This file-level number is the ground truth every engine's import inspector should match, and a mismatch usually means an import setting silently added or removed geometry.

Checking polycount correctly, at the triangle level and for the specific object or file in question rather than trusting a tool's default face-count display, is the first real step in any polycount budget on this site, whether you are targeting the mobile, desktop or VR tiers referenced across every model and platform page. Everything generated here is yours to use commercially with no attribution required, and a quick habit of checking the real triangle count before shipping saves the much larger cost of discovering a budget was silently doubled after a game is already in players' hands.