Find files, editable templates and browser test targets by what you need to make or test. The directory below is cut by format; the two collections under it cut the same library by subject and by workflow.
Page 3 of 8; 24 results per page.
The finned cube as a GLB. It renders without complaint in any viewer (rasterisation never asks about adjacency), so this is the fixture that separates tools which actually analyse topology from tools which merely draw triangles.
Twelve nodes reference one sphere mesh, in three groups whose parents each apply a different rotation and scale. The fixture for importers that copy geometry per node: a correct import keeps one mesh resource with twelve transforms, a naive one produces twelve meshes.
The same sphere and the same brushed-metal material as the OBJ+MTL pair in this group, but as a single self-contained GLB. Convert the OBJ+MTL and diff against this to score an OBJ-to-glTF material converter.
The third storage strategy for the identical sphere: a GLB whose buffer is the BIN chunk, with no URI at all. Compare the three file sizes in this group to see exactly what base64 and JSON whitespace cost.
A 1.12 m signpost with its coordinates written in centimetres, so this file's numbers read up to 112. glTF has no unit field: the spec simply says metres, which means a wrongly-scaled export is indistinguishable from a genuinely enormous model until something is measured.
A 1.12 m signpost with its coordinates written in metres, so this file's numbers read up to 1.12. glTF has no unit field: the spec simply says metres, which means a wrongly-scaled export is indistinguishable from a genuinely enormous model until something is measured.
A 1.12 m signpost with its coordinates written in millimetres, so this file's numbers read up to 1120. glTF has no unit field: the spec simply says metres, which means a wrongly-scaled export is indistinguishable from a genuinely enormous model until something is measured.
The signpost authored +Y up, which is what the glTF specification mandates and what every conformant viewer assumes. The conformant half of the axis pair: load it, confirm the post stands, and you have calibrated your viewer before testing the Z-up twin.
The same signpost authored +Z up: what a Blender or 3ds Max glTF export produces when the axis conversion is skipped. glTF has no field in which to declare this, so the file is indistinguishable from a model that genuinely lies on its back, and every conformant viewer will show it that way.
The same unit sphere at 16,128 triangles: level 0 of a four-step ladder that spans 202x from top to bottom. Because every level is generated analytically from the same surface rather than decimated, the ladder is an exact reference: any deviation you measure is your tool's, not the fixture's.
The same unit sphere at 3,968 triangles: level 1 of a four-step ladder that spans 202x from top to bottom. Because every level is generated analytically from the same surface rather than decimated, the ladder is an exact reference: any deviation you measure is your tool's, not the fixture's.
The same unit sphere at 960 triangles: level 2 of a four-step ladder that spans 202x from top to bottom. Because every level is generated analytically from the same surface rather than decimated, the ladder is an exact reference: any deviation you measure is your tool's, not the fixture's.
The same unit sphere at 80 triangles: level 3 of a four-step ladder that spans 202x from top to bottom. Because every level is generated analytically from the same surface rather than decimated, the ladder is an exact reference: any deviation you measure is your tool's, not the fixture's.
The third texture-storage strategy: the PNG lives inside the GLB's BIN chunk as a bufferView, addressed by `mimeType` rather than a URI. This is what a GLB packer must produce, and extracting the image again is the round-trip test.
Three named scenes over three meshes, with the asset's `scene` property pointing at index 1 rather than 0. Loaders that hardcode scene 0 show the wrong content and never report an error: this is the file that catches them.
The same sphere with every attribute in its own bufferView and no byteStride: the layout most exporters emit and most parsers assume. The control against which the interleaved twin in this group is diffed.
The same four degenerate triangles inside a structurally valid GLB. The file passes every glTF schema check (nothing in the format forbids a zero-area face), so this is the fixture for geometry validation as opposed to document validation.
A single animation whose four channels drive two nodes at once: the parent's translation, rotation and scale, and a spinning child that inherits all of it. The fixture for checking that channels are applied per node and per path rather than collapsed into one track.
Two open half-shells with identical geometry and opposite `doubleSided` flags. Because the shells are open you can see straight into them, which is the only way to tell backface culling from a lighting difference.
A rough red base under a full-strength, near-mirror clearcoat lobe: the two-layer material that car paint, lacquered wood and phone cases all need. The base and coat roughness differ by an order of magnitude, so a renderer that collapses the layers is obvious.
Emission pushed past the core spec's 0-1 emissiveFactor clamp by a 6x strength multiplier: the extension that exists because HDR bloom needs values core glTF cannot express. A tone-mapping and bloom-threshold fixture.
A sphere whose material opts out of lighting entirely via KHR_materials_unlit: the shading path used for baked scenes, maps and stylised art. Renders as a flat silhouette in a conformant viewer and as a lit ball in one that ignores the extension, which makes the difference obvious.
One mesh, two named material variants (Copper and Cobalt) selectable at runtime: the extension behind every product configurator that swaps a finish without reloading geometry. The primitive also carries a plain `material`, so viewers with no variant support still render something.
A sphere with the glTF core metallic-roughness material: full metal, low roughness, no textures, so the numbers in the JSON are the whole material. The baseline half of the metallic-roughness vs specular-glossiness twin.
