GLB Texture Extractor

Drop a binary glTF file, preview its materials, and download every embedded texture with a readable JSON material manifest. The model and extracted image bytes stay in the browser and are never uploaded.

Open the local GLB extractor · Read the GLB texture extraction guide

Drop one GLB

Choose a glTF 2.0 binary file. The local parser validates its header, reads the JSON and BIN chunks, and identifies image buffer views and embedded data URIs.

Preview PBR materials

Orbit a self-contained model and inspect base color, normal, metallic-roughness, occlusion, emissive, alpha, double-sided, extension, and UV-set bindings for each material. External resource URLs are not requested.

Download original images

Save PNG, JPEG, WebP, AVIF, KTX2, DDS, or unknown binary image payloads without resizing or recompression. Browser thumbnails appear when the format is natively displayable.

Keep the material context

The generated materials.json connects extracted filenames to material names, PBR slots, texture indexes, image indexes, UV sets, file sizes, image dimensions, and glTF extensions.

What the GLB texture ZIP contains

The ZIP places every embedded image under textures/ and writes materials.json at the package root. External image URIs are reported in the interface and manifest, but they are not requested because their bytes are not inside the dropped GLB.

Use the package for Blender, Three.js, Unity, Unreal Engine, Godot, WebGL asset audits, material repair, and texture reuse when the asset license allows it.

GLB Texture Extractor FAQ

Does the GLB Texture Extractor upload my model?

No. The GLB is read locally in the browser, and its model, images, and generated manifest are not sent to PLAYTEX AI.

Which embedded texture formats can it extract?

It preserves original PNG, JPEG, WebP, AVIF, KTX2, DDS, and unknown binary image payloads. Thumbnail support depends on the browser.

What is included in the material manifest?

The JSON lists materials, PBR factors, texture slots, UV sets, file and image indexes, extracted filenames, sizes, dimensions when readable, and glTF extensions.

Can it extract external GLB texture references?

External URIs are listed but not requested or downloaded because their image bytes are not in the single dropped file. Re-export with embedded resources for a self-contained GLB.