What happens to PBR materials?

They are reduced to a diffuse colour, an opacity value and a flattened base-colour texture in the .mtl. Normal, metallic/roughness, occlusion and emissive maps are dropped.

Will the download be a ZIP?

Yes when the model has materials, because the .obj, .mtl and texture images need to stay in one folder. A model with no materials comes out as a single .obj file.

Can an OBJ in a ZIP keep its own materials?

Only if the .mtl is in the archive. The converter looks for a companion .mtl inside the package, and reports in the conversion notes when it cannot find one.

OBJ Converter from ZIP Package

Unpack a ZIP archive and convert the model inside to Wavefront OBJ with a matching .mtl and textures. Runs in your browser.

Drag & drop your ZIP file here

or click to browse

Supported Formats

.glb.gltf.obj.fbx.stl.ply.3mf.off.zip

Format Information

Source Format

ZIP.zip

ZIP (archive)

A ZIP archive is not a 3D format — it is how most multi-file assets actually arrive. A glTF with its .bin and images, or an OBJ with its .mtl and texture files, is a folder, and a folder travels as a ZIP.

What it carries: Whatever the model inside the archive supports. The converter unpacks the archive, identifies the root model file and resolves that model's companion files by name.

Target Format

OBJ.obj

OBJ (Wavefront)

The Wavefront OBJ format is a plain-text mesh description that has been the default interchange format for computer graphics since the 1990s. Geometry lives in the .obj file; colour and texture references live in a companion .mtl file.

What it carries: Vertex positions, normals, texture coordinates and polygon faces, plus what MTL can express: a diffuse colour, opacity, shininess and a single diffuse texture map. There are no PBR metal/roughness values, no normal maps, no vertex colours and no animation.

Open a OBJ file in the viewer

About this conversion

The archive is unpacked and the model inside is written as a Wavefront .obj, with a matching .mtl and flattened textures when the source has materials. Delivered as a ZIP when there is an .mtl to include.

Why convert ZIP to OBJ

Get everything in a multi-file asset into a single OBJ plus material folder for a legacy tool.
Package a glTF or FBX asset as OBJ, which many older DCC tools still require.
Produce a self-contained materialised OBJ you can hand to a supplier.

What happens during the conversion

Geometry

The geometry is read from the model inside the archive and written to .obj, with faces triangulated. Node transforms are baked into the positions, since OBJ has no scene graph, and every mesh in the scene is included — including hidden ones, because OBJ cannot record a hidden state.

Materials and textures

Materials are reduced to what MTL can express: a diffuse colour, an opacity value and a flattened base-colour texture. Metallic, roughness, normal, occlusion and emissive maps are dropped, and vertex colours are not written.

Animation

Animation depends entirely on what is inside the archive, and OBJ has no field for any of it. An FBX or glTF inside the ZIP that carries a rigged, animated model loses its rig here: the .obj is a single static pose of the scene as it stood.

Common use cases

Meeting a legacy tool's OBJ-only intake requirement.
Packaging a glTF or FBX asset as a single materialised OBJ folder.
Producing a supplier-ready mesh with a .mtl and textures.

Limitations of this conversion

The archive must contain a model this tool can open. An .obj inside keeps its own .mtl and textures; a .gltf, .glb or .fbx inside has its materials reduced to what an .mtl can express.
PBR material fidelity is lost. Only the diffuse colour and a flattened base-colour map survive.
Vertex colours and animation cannot be represented in OBJ at all.
Every mesh in the scene is written, hidden or not, because OBJ has no hidden state.
If the archive holds a PLY that is a point cloud, the conversion stops with an error rather than writing an .obj, because OBJ needs faces and a point cloud has none.

How to convert ZIP to OBJ

Three steps in the browser. Nothing is uploaded to a server, so an unwieldy file is limited only by your own device's memory.

STEP 1

Zip your model and its textures

Include the .mtl with an OBJ, or the .bin and images with a glTF.

STEP 2

Upload the .zip

The archive is unpacked and the model inside is loaded with its companion files, then written as a .obj with an .mtl where materials were found.

STEP 3

Unpack the downloaded ZIP

A materialised model is .obj + .mtl + PNGs in one folder — keep them together.