Export a Unity Model to GLB or OBJ

Article

A model assembled by a user or procedural system may need to move from Unity into Blender, a server pipeline, or a mod package. A screenshot is insufficient, and a runtime mesh is not an external model file. Runtime Object Exporter writes OBJ or GLB and can use FBX when Unity FBX Exporter is installed. Choose the format according to the data that must survive.

Audit dependencies first

Assign the root GameObject and let the exporter scan its full hierarchy, including inactive children. Review MeshRenderer, SkinnedMeshRenderer, materials, and textures, then disable debug or helper content before export.

External export handles SkinnedMeshRenderer through BakeMesh. The result captures current geometry rather than a complete rig and animation set. Use another pipeline when an editable skeletal asset is required.

Choose GLB or OBJ deliberately

GLB creates one binary glTF 2.0 file with embedded geometry, materials, and textures. It can include positions, normals, UVs, base color, metallic, roughness, transparency, and double-sided state. Only the base texture from _BaseMap or _MainTex is embedded; normal, metallic, occlusion, and emission maps are not.

OBJ produces an .obj, an .mtl, and separate PNG files. The material contains diffuse color, transparency, and the base map, not a full PBR setup. X is inverted to match coordinate conventions. OBJ is easy to inspect, but its multi-file package is easier to break during transfer.

Import into the actual destination

Export a small representative object to a folder outside Assets and open it in the target DCC or viewer. Check orientation, scale, normals, UVs, transparency, and material appearance. A round trip into the same Unity project is not a sufficient compatibility test.

Runtime Object Exporter preserves geometry and core dependencies, not an exact Unity shader graph. GLB is practical for a portable package, while OBJ is straightforward for interchange; advanced material reconstruction remains manual.