glTF and GLB Resource Inspector

How to use glTF and GLB Resource Inspector

Inspect a glTF 2.0 JSON or GLB file, its buffer ranges, node hierarchy and inert image-resource references. Find missing selected references and container-boundary problems before handing an asset to a renderer. Extract the original parsed JSON into a separate readable artifact without loading textures, extensions or geometry.

1. Provide local gltf or glb asset.
2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
3. Copy the result or download a separate output; reset to clear the current form.

Good to know

• 8 MiB file; 1 MiB JSON; 40 parsed levels; 128 GLB chunks; 2,000 objects per modeled top-level array and 5,000 combined. Duplicate decoded JSON keys and prototype-related keys are refused.
• Only asset version 2.0, with absent or 2.0 minVersion, is modeled. GLB version 2 requires exact file/chunk lengths, first JSON and optional second BIN. Unknown later chunks are inventoried and ignored; they are not interpreted.
• The first GLB buffer may omit its URI and must match BIN bytes plus at most three zero padding bytes. Other buffers require inert URI text. External/data URI contents are never fetched, decoded or checked against declared lengths.
• Checks node/scene hierarchy, selected node object indices, bufferView declared ranges, image URI-versus-bufferView storage and extension declaration membership. It does not validate accessors, mesh primitives, textures, skin/animation structure, transforms, full schemas or extension semantics.
• URI source previews are at most 160 characters and may contain sensitive text present in your file. They remain plain text, never links or mounted content. JSON extraction parses and serializes the source and is not a byte-for-byte copy or a repaired model.
• Inputs are processed on this device and are not automatically saved or uploaded.