Validate glTF & GLB online
Drop a GLB or glTF and run the official Khronos glTF 2.0 validator right in your browser — every error, warning and hint, with the JSON pointer to fix it. Free, private, and nothing is uploaded.
Capabilities
What it does
- Runs the official Khronos glTF-Validator — the exact same engine the glTF ecosystem uses — right in your browser.
- Reports every error, warning, info and hint with its issue code and JSON pointer, so you know precisely what to fix and where.
- Filter issues by severity, and see the format, glTF version, generator and extensions used at a glance.
- Validates a self-contained GLB, an embedded glTF, or a glTF plus its external .bin buffers and texture images — just drop them together.
- 100% client-side — your model is never uploaded, with no account or watermark.
Process
How it works
- Drop your fileDrag a .glb or .gltf onto the tool. For a .gltf with external buffers or textures, add those files too so they’re checked.
- ValidateThe official Khronos validator runs locally against the glTF 2.0 specification — nothing is uploaded.
- Read & fixWork through the errors first, then warnings. Each issue links to a JSON pointer so you can find it in your asset.
Notes
Good to know
- The validator checks spec conformance, not visual quality — a file can be 100% valid and still look wrong or be far too heavy for the web.
- For a glTF with external resources, drop the .bin and image files alongside it; otherwise those buffers and textures can’t be fully validated.
- Reports are capped at the first 100 issues to keep things readable — fix those and re-validate to surface the rest.
- Want a web-readiness score (size, draw calls, VRAM, compression) instead of raw spec errors? Use the GLB inspector.
FAQ
Questions, answered
What does the glTF validator check?
It checks your asset against the official glTF 2.0 specification: JSON structure, accessor bounds and types, buffer views, image formats, material and mesh rules, extension usage and more — the same checks the Khronos reference validator performs.
Is my model uploaded anywhere?
No. The validator is compiled to WebAssembly/JavaScript and runs entirely in your browser. Your file and its textures never leave your device.
What’s the difference between an error, a warning and a hint?
Errors are spec violations that make the asset invalid and must be fixed. Warnings flag things that are risky or likely wrong but still technically valid. Infos and hints are advisory notes about best practice.
My .gltf reports missing buffers or images — why?
A .gltf stores geometry and textures in separate files. Drop the referenced .bin and image files together with the .gltf so the validator can resolve and check them.
How is this different from the GLB inspector?
The validator answers “is this a spec-correct glTF file?”. The inspector answers “is this model good for the web?” — grading size, triangle count, draw calls, VRAM and compression. They pair well: validate first, then optimize.
Next