Local model inspection

glTF Viewer Online

Open a glTF 2.0 scene with its local binary buffers and image files, or select one self-contained GLB. Inspect the supported geometry and materials, and play the first imported animation clip when available. Remote resources and unsupported compressed data are not loaded.

Last updated

Works locally · GLTF, GLB · Maximum 50 MB combined

Select one model and its local BIN, MTL or texture files together.

Choose a GLTF, GLB model or drop it here.

Your file is parsed in memory. It is never uploaded.

Drag to rotate. Right-drag or two-finger drag to pan; scroll or pinch to zoom. Keyboard: arrows rotate, Shift + arrows pan, + / − zoom, R resets. Animation starts only when you press Play.

Choose an existing model from your device. This tool does not generate a new 3D asset.

How to open a glTF file with local resources

A .gltf file describes a scene in JSON. The geometry buffer and images can be stored in separate files. Select the .gltf together with every referenced local .bin, PNG, JPEG or WebP file. An embedded data resource does not need a separate file, but an external reference needs a matching selected resource.

Extract the asset package before selecting its contents. Keep the filenames that the glTF references. The tool does not accept an archive as a model and does not retrieve missing files from a remote URL. The combined selection must be 50 MB or less.

  • Find the primary .gltf and its referenced resources in the exported package.
  • Select the model, binary buffers and images together.
  • Read missing-resource errors and correct the file selection or source export.
  • Inspect shape, materials and available animation clips after loading.

Choose glTF or a self-contained GLB

glTF and GLB are related delivery forms. A .gltf scene can keep JSON, geometry and images in separate resources. A self-contained .glb can package those resources into one binary file. This page accepts either form under its supported import rules.

A GLB is convenient when you want to pass around one file and avoid a missing-resource selection. A glTF package can be useful when resources are managed separately. Neither container guarantees clean topology, correct project scale or support for every material extension.

Keep dependency resolution local and explicit

The importer resolves references against the local files you select. It does not use a model reference as permission to retrieve an arbitrary URL. If an asset refers to a remote buffer or image, export a local portable copy from the authoring workflow.

Missing textures and missing geometry buffers are different problems. A missing image can affect appearance; a missing geometry buffer can prevent the scene from loading. Include the original resources instead of supplying an unrelated file with the same extension. Preserve the source package while you prepare a clean selection.

Review the imported material and geometry together

Start with the shaded model, then compare its silhouette and surface details from several angles. A glTF material can use several texture roles, so check small features, transparency and areas that appear unexpectedly bright or dark. An inspection view is useful for finding a mismatch before an engine import.

Wireframe and normal views help separate a geometry issue from an appearance issue. A visible seam can come from UV mapping, normals, mesh layout or a texture. The viewer does not edit any of these sources. Use the authoring application to fix the cause, export again and compare the new file.

Inspect available clips without assuming engine parity

When the importer finds supported animation, use the playback control to inspect the first imported clip. There is no clip selector. Review the default pose, the movement range and any parts that should move together. Use the authoring or destination application to review the other clips.

The preview does not establish game-engine behavior, retargeting correctness or performance on a target device. Animation naming, rig setup and runtime integration remain separate checks. Keep the original authoring asset and test the exported scene in its intended environment.

Use an uncompressed export for unsupported extensions

A glTF file can require extensions or compressed resources that need a decoder. This tool does not promise support for every glTF extension. If an asset requires unsupported compression, export an uncompressed compatible copy before opening it here.

Likewise, a supported container does not make every image encoding or custom material portable. Use the accepted local raster images and a compatible export. Reported loading errors are a better guide than repeated attempts with the same unchanged package.

Recognize a complete glTF package

A simple exported package might contain scene.gltf, scene.bin and base-color.png. The JSON scene describes where the binary data and image are used. Selecting all three gives the importer the resources it needs, provided that the references and data are compatible. The image does not become a texture merely because it was selected; the scene must reference it correctly.

Some packages use several binary buffers or images. Include the required local files while staying within the total selection limit. Avoid mixing resources from different export versions. A newly exported scene with an old binary buffer can have the right filenames and still contain inconsistent data.

Keep the original package unchanged while creating an inspection copy. If a file is missing from a received asset, ask its source for a complete export or recreate the export in the authoring application. The viewer does not search a remote website or infer the missing geometry.

Check texture roles and transparent surfaces deliberately

A glTF scene can use images for different material properties. A color image, a normal map and a roughness-related texture are not interchangeable. If a surface looks wrong, inspect the source material connections and export settings instead of selecting another image with a similar filename.

Transparent and thin surfaces deserve a separate look from several angles. The browser renderer and the receiving engine may handle material details differently. Use a simple known background or another asset in the destination application when you need to approve a particular production appearance.

Keep material inspection separate from file validity. A scene can be valid enough to parse while still having an unsuitable texture, missing detail or an artistic mismatch. The viewer helps you see the imported scene. It does not establish that every material decision is correct for your intended use.

Keep file size and browser memory separate

All selected resources count toward the 50 MB limit. A set of small compressed images can still become large in graphics memory. Dense meshes, many separate objects and animation data add to the work required to create the scene.

For a demanding asset, export one relevant object or an inspection copy with smaller textures. This is a practical review step, not a replacement for the production source. If you need fewer triangles in a supported static GLB, use the separate simplifier and compare its result with the original.

Viewer questions

Which glTF version can I open?

Use a compatible glTF 2.0 scene or self-contained GLB. Unsupported extensions, compression or resources can prevent an import even when the container version is correct.

Can I select a glTF and its .bin together?

Yes. Select the primary .gltf and its required local .bin and image files in the same selection. Keep the referenced filenames unchanged.

Why does my glTF report a missing file?

The scene refers to a resource that was not resolved from the selected files. Include the correct local resource or export a portable local package. Remote dependencies are blocked.

Can this page also open GLB?

Yes. A self-contained GLB is accepted. The dedicated GLB viewer provides a focused page for that one-file workflow.

Does it support every compressed glTF?

No. Decoder-dependent and unsupported compressed assets need a compatible uncompressed export. The viewer does not fetch a remote decoder or missing model resource on the asset’s behalf.

Does MeshCrate upload my selected files?

The tool reads selected model files and their selected dependencies in your browser. It does not upload those file bytes. The website still loads application code, fonts and public assets, and it can send usage events. Local file processing does not mean the whole website is offline. Remove the file or close the tab when you finish.

What is the file size limit?

The total selected model and dependency files must be 50 MB or less. A small file can still require substantial browser memory after parsing. If loading fails, close other demanding tabs or export a smaller model. Archives and remote model URLs are not accepted.

Continue with the format you need

You’re on the early-access list.

We’ll email when MeshCrate launches.

Trial incentives for early participants

You’ll receive trial incentives when we launch. We’ll share the offer and how to claim it in your launch email.

You’re signed in for product updates and trial incentives. Joining does not charge you.

Privacy notice · No payment or image upload.