What is an MTL file? The material library that travels with an OBJ model. The .obj holds the geometry; the .mtl beside it, in plain text, says what each surface looks like — its colours, its shininess, its transparency — and which image files to use as textures. Open either one in a text editor and you can read it.
OBJ itself is a plain-text geometry format from the 1980s. It carries very little and every tool ever written can read it.
What it carries
- Vertex positions, normals and texture coordinates
- Faces, including n-gons
- Groups and object names
- A reference to an MTL file for materials
What it does not
- Animation. None at all.
- Skeletons or skinning. None.
- PBR materials. MTL describes a pre-PBR model — diffuse, specular, ambient. Some extended conventions exist and are not universally supported.
- Scene hierarchy, beyond flat groups.
- Units. There is no unit information whatsoever.
Inside an MTL file
Each material starts with newmtl and a name, followed by one line per property:
| Line | What it sets |
|---|---|
| newmtl | Starts a material and names it |
| Kd | Diffuse colour, as red, green and blue from 0 to 1 |
| Ka, Ks | Ambient and specular colour |
| Ns | Shininess, roughly 0 to 1000 |
| d (or Tr) | Opacity — d 1 is solid; Tr is its inverse |
| illum | Which lighting model to use |
| map_Kd | The colour texture's file name |
| map_Bump or bump | A bump or normal map's file name |
How usemtl links the OBJ to its MTL
Two lines in the .obj do it. mtllib near the top names the material file — mtllib chair.mtl. Then usemtl with a material name appears before a run of faces, and every face after it uses that material until the next usemtl. A model with three materials has three usemtl lines and one mtllib.
There is no converting an MTL into an OBJ: they are two halves of one model, not two formats. To get a single file, convert the pair to GLB, which carries the geometry, materials and textures together — Blender does it by importing the OBJ and exporting glTF.
Why the textures go missing
Materials live in a separate .mtl file, which itself references texture images as separate files. So a "model" is three or more files that must travel together, and the paths inside them are frequently absolute — which is why an OBJ arrives with no textures more often than any other format.
The fix is nearly always the same:
- Keep the .obj, the .mtl and the images in one folder.
- Open the .mtl in a text editor and change every map_ path to the bare file name — no drive letters, no folders.
- Match the names exactly, including capitals: many tools and every Linux server treat Chair.png and chair.png as different files.
- Avoid spaces in file names, which some readers split on.
Where it is still right
- Simple static geometry going somewhere old
- 3D printing workflows that want colour, where STL cannot carry it
- Point-cloud-adjacent and scanning tools
- Anywhere human-readable output is genuinely useful
Why generated OBJ output is usually zipped
Because it is never one file. An OBJ export is the .obj, the .mtl, and one image per texture — so distribution bundles them, and a manifest listing "OBJ" typically means an archive rather than a single mesh file.
Practical advice
If something reads GLB, send GLB. Every model in Zetta 3D downloads as GLB, FBX, OBJ or STL, so the choice is yours rather than the generator's. OBJ is a compatibility fallback, and choosing it deliberately usually means the destination is old or the pipeline is simple enough that losing materials does not matter.