GLB Inspector (glTF 2.0 binary)
Validate a GLB file and list its nodes, meshes, materials, textures and size.
How it works
Check the structure of a binary glTF 2.0 file: chunk framing, buffer views, accessor ranges and min/max, triangle indices, node hierarchy and embedded textures. Lists node depth, triangles, materials and world bounds, and checks every mesh node for open or non-manifold edges.
- The 12-byte header (magic, version 2, total length) and the JSON and BIN chunks (type, 4-byte alignment, no trailing data) are checked first.
- Every buffer view must lie inside the binary chunk; accessors must be aligned to their component size, stay inside their view and contain finite values. POSITION min/max must match the data; indices must be unsigned and below the vertex count.
- The node graph must be a forest: each node has at most one parent, every node is reachable from the scene and there are no cycles. World transforms multiply parent and local TRS/matrix transforms.
- Each mesh node is welded by exact position and analysed with the Renderloom mesh engine (open, non-manifold and inconsistent edges).
This is a strict subset check, not the Khronos validator: external URIs, Draco and other required extensions, skins, morph targets, sparse accessors and non-triangle primitives are rejected or not analysed.
Sources
- glTF 2.0 specification (Khronos Group) (Khronos Group)
Part of Renderloom
-
Renderloom 3D scene & material studio
Shape a scene. Find its light. Keep every idea editable.
How to check a GLB file's structure, materials and watertightness
Validate a binary glTF 2.0 file and list its nodes, meshes, materials, textures, bounds and the watertightness of each mesh node.
What it is for
GLB Inspector opens a binary glTF 2.0 file and checks that its structure is sound before you hand it to a game engine, a 3D printing service or a web viewer. It reports the node hierarchy, triangle and vertex counts, materials with their texture bindings, embedded images and the world-space bounds, and runs Renderloom's mesh check on every mesh node.
Worked example
The example inspects the Little house exported by Voxel Greedy Mesher. The summary reads "Valid GLB: 2 nodes, 164 triangles, 4 materials, 0 images; 1 of 1 mesh nodes are watertight." The mesh table shows the voxel model node at depth 1 with 164 triangles, watertight, 0 open edges and 0 non-manifold edges. The materials table lists four flat colour materials with metallic 0 and roughness 1 and no textures.
How to read the result
The check fails with a clear message when the 12-byte header, the JSON or binary chunk framing, a buffer view, an accessor range or alignment, POSITION min/max, a triangle index, the node hierarchy (more than one parent, cycles, unreachable nodes) or a texture reference is wrong.
Watertight per node means no open or non-manifold edges and consistent winding after welding identical positions. Open meshes are fine for rendering but not for 3D printing or volume calculations. The volume reported for each node in the result data is computed with the divergence theorem in the file's units (cubic metres for glTF), so it is only meaningful for closed nodes.
Tips and common mistakes
- This is a strict subset check, not the Khronos glTF validator. Files that require extensions such as Draco compression, external or data-URI buffers, skins, morph targets, sparse accessors or non-triangle primitives are rejected.
- Limits: 64 MB, 2,000,000 triangles and 3,000,000 vertices.
- Bounds are in glTF units (metres) with Y up.
FAQ
Why is a GLB from another program rejected?
Most often it requires an extension this checker does not decode, such as Draco or meshopt compression, or it references external files. Export it again without compression and with embedded buffers, or check it with the Khronos glTF validator.
What does a non-watertight mesh node mean?
Its triangles leave open edges or share an edge between more than two faces after identical positions are welded. That is normal for planes, leaves or separate pieces modelled as one node, but a part you want to 3D print or measure must be closed.
Are the bounds in millimetres?
No. glTF uses metres with Y up, and the inspector reports the bounds exactly as the file defines them, after applying every node transform from the scene root down to each mesh.
Does the inspector change my file?
No. It only reads the uploaded bytes and reports what it finds; nothing is rewritten or stored.
Guide last updated:
For scripts and AI agents
- JSON API:
POST https://renderloomglbinspector.usefulweb.app/api/v1/calculate(same calculation as this page) - Interface description: OpenAPI 3.1 · AI guide: llms.txt
- MCP server (Streamable HTTP):
https://renderloomglbinspector.usefulweb.app/mcp· tool namerenderloom_glb_inspector
Example request
curl -s -X POST https://renderloomglbinspector.usefulweb.app/api/v1/calculate \
-H 'content-type: application/json' \
-d '{…see OpenAPI examples…}'