Field notes

Keep a glTF kit together

Import the model with its textures, then check the result before making it part of a larger scene.

Extract the entire folder

Our model downloads are complete ZIP kits, not isolated geometry files. Extract the whole archive before importing. Keep the .gltf file, its .bin buffer and the textures folder in their supplied relative positions. Copying only the small .gltf file into another folder can leave its dependencies behind.

glTF can refer to external buffers and images using relative paths. This is why the folder arrangement matters. The Khronos glTF specification documents that structure. The kits here use glTF with separate files, rather than claiming to be self-contained GLB files.

Make a small import test

Open a fresh scene and import the .gltf file through your application's glTF importer. Look at the object under neutral lighting before placing it in the production scene. Confirm that the intended materials appear, then inspect a close view and the object's silhouette.

If the object is unexpectedly untextured, confirm that the archive was fully extracted and that the original folder names are intact. If the materials exist but look different, compare lighting, exposure and colour management. A material preview and a final renderer need not present exactly the same result.

Record your changes

Check the object's scale against a known reference in your scene. The triangle count on our page is calculated from the supplied mesh primitives; it does not describe every possible imported or subdivided result. Avoid renaming texture files until you have established how the importer resolves their paths.

Save a working copy separately from the original kit. If you simplify geometry, resize maps or alter materials, record those choices so another project can reproduce them. Start with the folding stool: test the wood grain, the legs and the frame from a few camera angles, then place it beside your own furniture at the intended scale.