GLB Inspector
Drop a GLB or glTF file to see its specs, the facet64 catalog checks and a 3D view.
Runs in your browser. Nothing is uploaded.
How the inspector works
The file is read in your browser with glTF-Transform, the library the facet64 processing pipeline uses. Nothing is uploaded, and closing the tab discards the file.
Specs and checks follow the catalog rules: the same check codes, thresholds and messages as on model pages. Objects named _LOD0, _LOD1… are levels of detail; names starting with UCX_ or COL_, or ending in _col, are collision meshes.
Dimensions are in meters with Y up, as the glTF format defines them. The pivot is the origin of the model’s root object, compared with its base and center.
What differs from the catalog pipeline
- The pipeline imports the file into Blender, converts it to every download format and reopens each file. A browser can’t run that step, so “Download files match the source” is not shown and the Game-ready result is worded differently.
- glTF stores triangles only, so a GLB never has n-gons. Vertices are counted as the file stores them, split at UV seams and hard edges, so the number can be higher than in Blender.
- Draco and meshopt geometry is decoded before measuring. KTX2 textures are measured but not shown in the 3D view.
Files up to 256 MB, including a .zip with the model and its textures.
