ToolBuddyToolBuddy
GameNew

glTF Material Inspector

Inspect every PBR material, texture, and extension a glTF or GLB declares, isolate any channel on the model, and get a validation report — read-only and entirely in your browser.

Select or drop a glTF or GLB model

See every PBR material, texture and extension a glTF declares, view any channel on the model, switch material variants, check texture memory, and validate it against the official Khronos glTF Validator.

In-browser processing — files never leave your device.
Full PBR material and texture breakdown, including extensions.
Channel isolation on the model plus per-channel texture views.
Validation report exported as Markdown or JSON.

Why ToolBuddy?

No file upload

Your files never leave your device.

Fast browser processing

Processing runs directly in your browser.

glTF and GLB

Reads the raw asset, so nothing declared is hidden.

Free, no signup

All tools are free forever. No account required.

Know your workflow

Supported files and how to use.

Check supported input/output details and follow the tool steps before exporting.

🧾

Technical specs and decision signals

Use these specs to validate workflow fit, privacy boundaries, and output expectations before you run the glTF Material Inspector.

Cost

Free workflow with no signup gate for core usage.

Security

All processing runs in-browser — files never leave your device.

Device

Supports modern desktop and mobile browsers with OffscreenCanvas support.

Tech specs

Input: glTF, GLB (plus side-car .bin and texture files, or a ZIP). Output: Markdown or JSON report. Read-only — the tool never writes to your model. Caps: up to 32 textures decoded per asset; statistics sampled at 256px.

🧭

How to use

Check supported input/output details and follow the tool steps before exporting.

01

Drop or select a GLB, a glTF with its files, or a ZIP, or try the sample.

02

Read the checks and the Khronos validator summary.

03

Pick a material to see its factors and textures, and use Show channel to view base colour, normal, metallic, roughness, occlusion or emissive on the model.

04

Open Textures to split a texture's channels and see its size and graphics memory, and switch material variants if the file has them.

05

Click a finding to jump to the material or texture it is about, and download the report.

Guide

Learn, decide, and apply.

Understand how to how to inspect gltf materials and textures in your browser, why it matters in repeat workflows, and when to use this tool with confidence.

✨

In-browser gltf material and pbr inspection

  • Runs entirely in your browser — files never leave your device.
  • Reads the raw glTF, so vendor extensions are listed rather than silently dropped.
  • Channel isolation renders one PBR input at a time, unlit, with no tone mapping in the way.
  • Per-channel R/G/B texture view makes packed ORM ordering obvious at a glance.
  • Statistical rules carry an explicit confidence score and are never reported as certainties.
  • Report exports as Markdown or JSON, generated from exactly what the screen shows.
🎯

Debug pbr materials, textures, and colour space in gltf assets

  • Trace why a model renders subtly wrong in Unity or Godot but shows no error.
  • Confirm a normal map is tangent-space before shipping an asset.
  • Check whether a packed ORM texture has occlusion, roughness, and metallic in the channels glTF expects.
  • Find textures that ship in the file but no material references.
  • Hand a reviewer a Markdown report naming the exact material and texture at fault.
About

About glTF Material Inspector

How to inspect gltf materials and textures in your browserIn-browser gltf material and pbr inspectionDebug pbr materials, textures, and colour space in gltf assets

Read every material the file declares

The Materials tab lists baseColorFactor, metallic and roughness factors, every texture slot with its UV set, alpha mode and cutoff, double-sidedness, and each declared extension with its parameters.

Extensions the tool does not interpret are listed by name as present-but-not-interpreted rather than hidden, so nothing in your file goes unreported.

Isolate a single PBR channel on the model

The channel buttons under the viewport replace the material with a flat, unlit read-out of one input at a time — base colour, normal, metallic, roughness, occlusion, or emissive. Tone mapping is off, so you are looking at the values themselves.

This is a diagnostic view, not a reference renderer, and it samples the primary UV set.

Validate against the mistakes that fail silently

The report covers colour-space conflicts, normal maps without tangents, missing UV sets, suspect ORM channel ordering, inert textures multiplied to nothing, duplicate and unreferenced textures, and oversized or flat-colour maps.

Statistical rules carry a confidence score and are never raised as errors. A clean report means none of these rules fired, not that the asset is guaranteed correct.

FAQ

Common questions.

Have more questions? Reach out via our contact page and we will respond within 24 hours.

Do my files upload to a server?

No. The Material Inspector runs entirely in your browser, including the Khronos validator, and never sends your files anywhere.

Which files can it read?

GLB, and glTF with its .bin and textures (choose them together, drop the folder, or use a ZIP). OBJ, STL and PLY carry no PBR materials.

What is the Khronos glTF Validator?

The official validator from the group that maintains glTF. It checks that the file follows the glTF 2.0 specification, which is what engines and marketplaces check; this tool runs it beside its own material checks.

Can it switch material variants?

Yes. When a file uses KHR_materials_variants, pick a variant from the Preview toolbar to see it on the model.

How is graphics memory worked out?

Each texture is counted as uncompressed RGBA with mipmaps, which is what PNG, JPEG and WebP become on the graphics card; KTX2 textures take about a quarter of that.

Are the normal-map and channel-order findings certain?

No. They are statistical guesses from the pixels and say how sure they are; use the channel view to confirm.