Browser 3D tools
Convert GLTF to OBJ for desktop mesh editors. Include the referenced buffers and textures to export the supported geometry and material resources.
Source format
Target format
glTF is designed to move renderable assets between applications, but some mesh tools work best with OBJ. This route provides a static representation for editing, analysis or reuse in a different scene.
Select one main .gltf document together with its referenced resources. The JSON describes the asset; external buffers and images may contain much of its actual data.
For GLTF to OBJ, gathering the source resources is part of handing over a usable asset. A readable JSON document can contain names and references while the actual vertices live in a BIN file. Include those buffers even if the intended OBJ is only needed for geometry editing.
A glTF scene can position mesh instances through a hierarchy of nodes. The OBJ export applies imported instance transforms to the written geometry and uses mesh groups in the output.
The resulting coordinates describe placement, but OBJ does not retain the original parent-child scene graph. It is a different representation of the imported shapes, not an editable copy of the full glTF document.
A material reference can cross the format boundary without reproducing every rendering feature.
Available texture coordinates can be written with the mesh so supported images can be placed on the surface. GLTF to OBJ retains usable mapping information where represented, but does not invent a UV layout for a model that lacks one.
The exporter writes an MTL alongside the OBJ, with supported colours, opacity and map references. Keep the exported images with it so an editor can resolve the material resources without guessing their locations.
Metallic-roughness behaviour and specialised glTF extensions are not reproduced as a complete PBR scene. After GLTF to OBJ, an editor may need a new shader setup even when the base texture appears correctly on the surface.
Skeletal rigs and animation tracks have no equivalent in this output. This page also has no controls for choosing an animation frame or baking a deformed pose.
If a particular character pose matters, make it a static mesh in the authoring tool first. Retain the original glTF resources for animation work.
GLTF to OBJ is best treated as a static derivative of the source scene. A product prop or background object may fit that use well; a rigged character needs a more deliberate export from its authoring tool. Reimporting the OBJ later cannot restore the animation data omitted here.
No. The OBJ is a static geometry export and does not contain the rig, skin weights or animation tracks needed for skeletal editing.
Not as a glTF scene graph. GLTF to OBJ applies imported transforms to exported mesh instances; the resulting OBJ groups are not a substitute for the original parent-child relationships.
The conventional MTL description does not reproduce the entire glTF PBR material system. Similar base colours or textures can still react differently to lighting.
Use the exported MTL and image files with their generated names. They contain material references and supported maps that are not embedded in the OBJ text.
The generated OBJ contains its geometry as text, so it does not depend on the original BIN. Use the newly exported MTL and images for appearance. Keep the source set separately if you need to return to the original glTF scene.
GLTF to OBJ writes imported instances as transformed geometry. That can repeat vertex data for an object used many times, rather than keeping one shared mesh with several scene-node references. The output may therefore be less compact than the source.
