Extract the geometry of a GLB model (binary glTF) locally as OBJ - for Blender, Cinema 4D and 3D tools. No upload.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
GLB is the common single-file format for web and AR (glTF in binary form). If you want to edit such a model further in a classic 3D program like Blender, Cinema 4D, Maya or MeshLab, you often need the plain OBJ format. This tool reads the geometry out of the GLB and writes a clean OBJ file.
The GLB file is split apart (JSON structure plus binary buffer) and all meshes of the scene are read. The node transforms (translation, rotation, scale) are applied so the vertices end up at their actual position in the scene. Several meshes are merged into one combined geometry. Both indexed and non-indexed triangles (also strips and fans) are supported.
Everything runs entirely locally in the browser - your model never leaves your device. Honestly framed: pure geometry is extracted. Materials, textures, animations, skeletons and cameras from the GLB are not carried into the OBJ, and no MTL file is produced. A broken or geometry-less file is rejected with a clear message.
| Input formats | GLB |
|---|---|
| Output format | OBJ |
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Reads the geometry of all meshes from a GLB (binary glTF 2.0) and writes OBJ; node transforms are applied, meshes merged, indexed and non-indexed triangles (also strips/fans) supported. Pure geometry is extracted - material, texture, animation, skeleton and camera are not carried over (no MTL file). An invalid or geometry-less file is rejected with a clear error.
Yes. Translation, rotation and scale of the scene nodes are applied to the vertices so the geometry sits in the right place.
No. Pure geometry is extracted; material, texture, animation, skeleton and camera are left out.
Yes. All meshes of the scene are read and merged into one combined geometry.
No, the conversion happens entirely locally in the browser; your model never leaves your device.