GLB to GLTF Converter
Unpack GLB binary files into editable GLTF with separate JSON scene description, buffers, and texture images for inspection and modification.
Loading...
Please wait
About This Tool
GLB bundles everything into a single binary file, which is great for delivery but difficult to edit. Converting to GLTF separates the scene into its JSON descriptor, binary geometry buffer, and individual texture images — making each resource independently accessible for editing, analysis, or replacement.
Tips
- 1Automatically extract model information
- 2Support mesh optimization and texture embedding
- 3Real-time 3D preview
How to Use
Upload Your GLB
Drag and drop your GLB file or click to browse
Review Model Info & Settings
Check model information and adjust conversion settings
Download GLTF
Click convert and download your GLTF file instantly
Frequently Asked Questions
What is the difference between Separated and Embedded modes?
Separated (default): exports a ZIP archive containing a .gltf JSON file, .bin mesh buffers, and individual texture images — ideal for editing and replacing resources one by one. Embedded: exports a single .gltf file with all buffers and textures inlined as Base64 data URIs — convenient for single-file distribution, but larger in size and harder to edit textures individually. Switch modes in Conversion Settings under Resource Mode.
What files will I get after unpacking?
It depends on the resource mode. In Separated mode you download a ZIP with a .gltf file, .bin buffers, and texture images (.png/.jpg) linked by relative paths. In Embedded mode you download a single .gltf file with all resources inlined — no extra files needed.
Will I get separate texture files from the GLB?
Yes, in Separated mode. All images embedded in the GLB — diffuse maps, normal maps, metallic-roughness maps, and others — are extracted as individual PNG or JPG files with proper URI references in the output GLTF JSON. In Embedded mode, textures are inlined as data URIs inside the JSON.
What format are the extracted textures?
Textures are output in their original format from the GLB, typically PNG or JPG. If the GLB uses compressed texture formats (e.g., KTX2), they are converted to standard PNG for editing.
Can I extract only specific resources from a GLB?
In Separated mode, all resources are stored as individual files after unpacking. You can keep only the textures or mesh data you need, delete unwanted files, and manually update the GLTF JSON references. Embedded mode inlines all resources in a single JSON file and is not suited for selective extraction.
Does unpacking lose any data?
No. GLB to GLTF conversion is lossless — all geometry, materials, textures, and animations are fully extracted. Unpacking only changes how data is organized, not the content itself.
Can I manually edit the GLTF JSON file?
Yes. The main GLTF file is standard JSON that can be opened in any text editor. You can modify material parameters, adjust node transforms, replace texture references, and more. Validate the JSON with a linter after editing.
Related Articles
From Blender to Production: An End-to-End Compression Walkthrough
Take a 50MB PBR model through Blender export, vertex compression, KTX2 texture conversion, and engine loading, all the way down to under 5MB. With a full automation script and a series cheat sheet.
Different Platforms, Different Fates: A Compression Selection Guide
Desktop, mobile, VR, Mini Programs—which compression combo should you actually use? This one rolls up the previous four into a decision matrix and an automation script. Just pick along it.
KTX2 in Practice: The Right Way to Do Texture Compression
ETC1S or UASTC? How do you use toktx and gltf-transform? How do you load KTX2 in Three.js / Babylon.js? This one is all copy-pasteable commands and code.