GLB & GLTF Packager

One file or many — both are the right answer sometimes

A glTF asset can live in two shapes, and which one you want depends entirely on what you are about to do with it.

GLB — one binary file. Everything is inside: JSON, buffers, textures. It cannot lose its textures in an email, cannot break when a folder gets reorganised, and drops into any viewer without a directory structure around it. This is what you deliver.

glTF — JSON plus separate files. The scene description is readable text you can open, diff in git, and edit by hand. Every texture is an ordinary PNG or JPEG sitting in a folder, editable in place with no round trip through a 3D tool. This is what you work with.

This free online packager converts between them, in both directions, in your browser.

Why unpacking is underrated

Most tools only go one way — toward GLB — because delivery is the obvious use case. But unpacking solves problems that are genuinely annoying otherwise:

• Fix one texture. Unpack, open the PNG in any image editor, save, repack. No DCC tool involved.
• Read the material values. The .gltf is JSON. Search it for metallicFactor and read the number.
• Version control. A binary GLB produces a useless diff. An unpacked glTF shows you exactly which value changed in a pull request.
• Debug a loader. When an engine rejects a file, being able to read the JSON usually reveals why in seconds.

Embedded images

Unpacking offers a third state: a .gltf with its images inlined as base64 data URIs. That gives you a single file that is also readable text — handy for pasting into a bug report or committing a small asset. The cost is roughly 33% size inflation, because base64 is not a compact encoding. Use it for small assets, not for a 40 MB model.

Nothing is re-encoded

Both directions copy texture bytes verbatim. A PNG that goes into a GLB comes out of the unpacker as the same PNG, byte for byte. Draco and Meshopt compressed geometry survives the round trip intact, because the reader and writer both understand those extensions.

Missing resources fail loudly

A .gltf on its own is an incomplete asset — it points at .bin buffers and image files that must travel with it. If you try to pack one without supplying those companion files, this tool stops and tells you exactly which ones are missing. The alternative, which some converters do, is to produce a GLB that looks fine until someone opens it and finds no geometry.

Privacy

Packing and unpacking happen entirely in your browser. Nothing is uploaded, stored or logged.