Is this 3D model render-ready?

Drop a 3D file and get its numbers and a verdict per target before you import it anywhere. The file never leaves your browser.

Drop your 3D file here, or click to chooseFor OBJ and COLLADA, include the material and texture files, or a .zip containing everything. Nothing is uploaded — the file is read entirely in your browser.

What the numbers mean

Triangles

Every renderer draws triangles, whatever the modelling tool called them. Quads count as two, NURBS count as whatever density they were saved at. This is the number that decides whether a scene stays interactive, and it is read from the geometry, not from metadata.

Meshes and objects

Meshes are the geometry; objects are the places in the scene graph that use them. More objects than meshes means instancing, which some targets keep and others flatten into copies.

Materials

Counted as the file stores them. A Rhino 3DM shows "not read" here: we take its geometry from the saved render meshes and never look at its materials, so a zero would be a guess.

Textures and the largest one

Only textures inside the file, or dropped alongside it, are counted. The largest edge in pixels is read from each image header without decoding it. Textures the file refers to but could not find are listed separately, because that is the usual reason a model arrives grey.

Real-world size

Shown in metres when the format or the file declares a unit: FBX counts in centimetres, glTF in metres, COLLADA and Rhino say what they use. OBJ, STL and PLY carry bare numbers, so for those we show the numbers and say plainly that the unit is unknown.

File size

The bytes you dropped, across every file. Browsers have a memory ceiling we cannot raise, so above a certain size the verdicts switch to "too heavy" for conversion in a browser — the model itself may be fine.

Questions

How do I check the polygon count of a 3D model without opening it in 3D software?: Drop the file on this page. It is parsed in your browser, never uploaded, and the triangle, vertex, mesh and material counts are read from the geometry itself. GLB, glTF, OBJ, FBX, COLLADA, STL, PLY and Rhino 3DM are supported; a zip with the textures counts them too.
Why does my model import at the wrong size?: Most often because the file has no unit. OBJ, STL and PLY carry only numbers; FBX counts in centimetres and glTF in metres, a factor of one hundred. The report shows the real-world size when the format declares a unit, and says plainly when it does not.
Why are my textures missing after export?: The exporter wrote a path to an image instead of the image. OBJ and COLLADA always do this; FBX can embed or link. The report counts the textures inside the file and names the ones it references but could not find, so you know what to bundle before sending it.
Will this file convert cleanly to GLB, USDZ, OBJ or STL?: The report gives a verdict per target for the conversions we publish: clean, or a named loss such as dropped animation, an unverifiable scale or a material feature the target cannot carry. Each verdict comes from what we measured in your file and links to the matching converter.