Check GLB / GLTF files for header, chunk and JSON structure and common issues, fully local.
or click to browse, paste supported
Upload a GLB or GLTF file and the tool checks the container header, chunk layout and JSON structure against the glTF 2.0 specification. GLTF files may reference external .bin buffers and textures; upload them together. Results are shown immediately; nothing is uploaded to a server.
Drop a GLB or GLTF file
See magic, version, chunk and JSON details
Re-export a valid GLB or glTF from your DCC tool
About this tool
GLB is a single binary container that bundles the JSON, buffers and textures into one file. GLTF is a JSON file that may reference external .bin and texture files. Upload them together for a full check.
Yes. External .bin buffers and textures referenced by GLTF can be uploaded together; the tool checks the integrity of these references.
The JSON is parsed against the glTF 2.0 specification: required fields such as asset.version and meshes, buffer and image references, and bufferView/accessor bounds are checked. GLB files additionally get their magic number, version, total length and chunk layout verified. EXT_ or vendor extensions are not interpreted.
The most common causes are invalid JSON, missing required fields such as asset.version, external .bin or texture files not uploaded together with the .gltf, and buffer references that point outside their data. Re-export the file as glTF 2.0 from your DCC tool. The report names the exact field or chunk that failed.
No. Validation is read-only: neither the GLB binary chunks nor the glTF JSON document are modified. Issues are fixed by re-exporting the file from your DCC tool.
Structural checks rule out common problems in the header, chunks and required JSON fields. Special extensions or business fields required by particular applications are not covered.
General questions
Core features are free forever. Format conversion, model optimization, and online preview do not require an account. Some advanced features are paid.
No. Files you select are processed only in your browser on this device, so they never leave your device and are never sent to our servers. We don't store any user files; after processing, related data in browser memory is released.
No installation required. Any3D is entirely browser-based; just open the webpage to use all features. It works on Windows, Mac, Linux, and other major operating systems.
There is no cap on file size or polygon count. How large a model you can open depends on your device's memory and graphics card, and very heavy models may make the page lag or crash. Some tools do limit how many files go in at once, such as 50 models per batch or single images up to 50 MB in texture compression. See Limits for the full list.
