Drop a STEP, IGES, BREP or mesh file to preview it here.
PERSP
Free online glTF viewer
Open a .gltf file in the browser and inspect its scene tree, triangle counts and dimensions. Self-contained files work best — a .gltf that keeps its buffers in sidecar files cannot be completed here.
Drop 3D files hereor click to browse — nothing leaves your browser
Drop your .gltf file onto the viewer above. A JavaScript loader parses the glTF JSON in a Web Worker, decoding Draco-compressed meshes locally where the file uses them. Nothing is uploaded — the page reads the file you picked and keeps it on your device.
Confirm the file is self-contained. A .gltf that stores its geometry in a sidecar .bin, or its images in separate files, cannot be completed here: only the file you dropped exists inside the page. Export with embedded buffers, or use the single-file .glb variant instead.
Inspect the scene, then measure it. The JSON scene description usually keeps node and mesh names intact, so the tree is readable. Check per-node triangle counts in the Properties panel, drag a section plane, and measure between snapped points.
What glTF files are, and what writes them
glTF is the Khronos royalty-free standard for transmitting 3D scenes. The JSON variant keeps the scene description human-readable with geometry in sidecar buffers, and the ecosystem — Babylon.js, Unity, Unreal, Blender and the browser engines — treats it as the native interchange format for real-time 3D.
The JSON variant of glTF is written by Blender, Khronos tooling and asset pipelines that deliberately keep the scene description readable and the binary payload separate. Babylon.js, Unity, Unreal and the browser 3D engines all treat glTF 2.0 as their interchange format.
Industry-standard for real-time and web 3D
Readable JSON scene description
Full PBR material model and animation support
Best for: Real-time engines, web development and 3D pipelines. There is a fuller write-up on the glTF format reference page.
What you can inspect in glTF files here
The scene graph with node and mesh names, which the JSON form of glTF preserves particularly well.
Per-node triangle counts and bounding boxes, for judging whether a scene is web-viable.
Base material colors per mesh, keeping material groups distinguishable.
Section planes, snapped measurement and PNG capture, as on every other format here.
Every format on this site also gets the same viewport tools: orbit, pan and zoom with fit-to-view, isometric and the six standard views, a perspective/orthographic toggle, shaded, shaded-with-edges, wireframe and X-ray display, hide-selected, and a PNG screenshot of the current view. The same controls are on the general 3D and CAD viewer, which accepts every importable format at once.
What this viewer does not show for glTF
Worth knowing before you rely on it. A viewer that overstates what it can read wastes more of your time than one that is specific about its limits.
External resources cannot be resolved. Geometry in a sidecar .bin and textures in neighbouring image files are unreachable, because the page receives one file and never touches the rest of your disk.
Textures and full PBR materials are not rendered even when they are embedded — each mesh is drawn in its base color.
Animations, skins and morph targets are not played; the pose is the one baked into the file.
Cameras and lights are skipped, since they contain no geometry.
Coordinates are metres by specification but carry a millimetre label in the readouts, so divide expectations accordingly.
glTF at a glance
glTF files
Extensions
.gltf
Geometry
GPU-ready triangle mesh
Units
Meters by spec
Colors & materials
Full PBR materials
Animations
Yes
Typical use
Real-time engines & web pipelines
glTF is specified in metres, while the readouts append a millimetre suffix to raw coordinates. A 2.00 mm dimension on a glTF file almost certainly means two metres.
Convert glTF instead of just viewing it
glTF can be read and written here. Packing it into a single .glb is usually the first thing worth doing. The converter runs on the same local pipeline as this viewer, so a conversion is just as private as a preview: glTF to GLB is the usual choice.
Most likely it references a separate .bin buffer. That file is not part of what you dropped and cannot be fetched from your disk, so there is no geometry to build. Re-export as .glb, or as glTF with embedded buffers, and it will open.
Should I open the .gltf or the .glb?
The .glb, whenever you have it. It is the same scene in one self-contained binary file, so nothing can go missing. Use the .gltf here when it is the only copy you have and its buffers are embedded.
Are animations and textures shown?
No. This is a geometry inspector: hierarchy, counts, dimensions, sections and measurements. Animation clips are not played and texture maps are not sampled — meshes are drawn in their base material color.
Is the file uploaded for processing?
No. The JSON is parsed by a JavaScript loader in a Web Worker inside your browser, and Draco decoding also runs locally. Nothing is transmitted.
What does glTF store, and how much of it does the viewer show?
Geometry: gpu-ready triangle mesh. Units: meters by spec. Colors and materials: full pbr materials. Animations: yes. Of that, the viewer draws geometry and flat base colors; texture maps and animation are never displayed. glTF is specified in metres, while the readouts append a millimetre suffix to raw coordinates. A 2.00 mm dimension on a glTF file almost certainly means two metres.
If the model is heavier than it needs to be, the mesh simplifier reads .gltf directly, decimates it in your browser and previews the result before you export. If the file is headed for a 3D printer, the G-code viewer shows the sliced toolpath layer by layer once your slicer has run.