STL Viewer: Convert a Multi-File glTF to OBJ With Textures

STL Viewer: Convert a Multi-File glTF to OBJ With Textures

STL Viewer, Gltf to Obj, Supavoxel

For readers who arrived via stl viewer, this guide covers a related workflow: gathering a complete multi-file glTF, converting it to OBJ with textures, and checking which materials survive.

Many glTF downloads are not one file: they contain a JSON scene, a binary buffer, and a texture folder. This guide shows how to provide that complete set, export an OBJ package, and verify which materials survived the conversion.

How to Convert a Multi-File glTF to OBJ With Textures

The short version

  • A separate glTF needs the .gltf, its .bin, and any texture images. Select them together, or zip the complete export folder.
  • Use the glTF to OBJ converter with Include materials & textures enabled to receive an OBJ, MTL, and PNG texture files.
  • Keep the downloaded files in one folder. The OBJ refers to the MTL, and the MTL refers to the PNGs by filename.
  • Base color and normal information can carry over. Metallic, roughness, occlusion, emissive data, animation, cameras, and lights do not.

Know what kind of glTF you have

glTF commonly arrives in one of three layouts.

A GLB is a single binary file containing the scene and its supporting data. An embedded glTF is a single JSON file with geometry and images stored inside it as base64 text. Those two formats can be supplied as one file.

The multi-file version is different. It has a .gltf JSON file, a .bin file containing geometry data, and often a folder of images. Blender exports, Sketchfab downloads, and other asset packages often use this arrangement. The JSON file contains references to the other files, so handing over only the .gltf is incomplete.

This matters because a browser tool can only read files that are actually selected or dropped into the page. The converter matches side files by name. It does not require the original folder path inside the package to remain unchanged.

glTF to OBJ converter showing the file drop area and conversion controls

The converter accepts a complete multi-file glTF selection or a zip of the export folder.

Step one: gather the complete export

Before opening the converter, find the folder containing the glTF scene. A typical package has:

  • The scene file, such as character.gltf
  • The binary buffer, such as scene.bin
  • One or more PNG, JPEG, or WebP texture images
  • Optional subfolders containing those images

Do not rename the texture images after downloading the package. The MTL created later will point to the exported PNG names, so changing filenames makes the material references harder to resolve.

There are two reliable ways to prepare the files:

  1. Select the .gltf, .bin, and texture images together in the file picker.
  2. Zip the entire export folder and use the zip as the input.

A folder can contain subfolders, and the converter can read those files from a zip. Dragging the folder itself is not supported, so select its contents or create the zip first.

If the package contains a missing .bin, the converter stops and identifies the file it needs. Missing images do not prevent the model from opening, but the result will be untextured and the page will note which files were not included.

Step two: supply the files and choose textures

Open the converter and add the files in one of these ways:

  1. Click the file picker and multi-select the .gltf, .bin, and texture images.
  2. Drag all of those files into the drop area at the same time.
  3. Drop one zip containing the whole export folder.
  4. If the source is a GLB or embedded glTF, add that single file.

Once the scene is read, leave Include materials & textures enabled if the goal is a textured OBJ package. The download will contain the geometry plus the material and image files. Turn the option off only when a geometry-only OBJ is more useful. In that case, the result contains the mesh, normals, and UV coordinates without the material package.

Press Convert to OBJ and wait for the download to finish. Each file supplied to the converter can be up to 200 MB. The conversion runs in the browser, so the model is not uploaded.

A multi-file conversion does not turn the OBJ into a self-contained asset. OBJ is a geometry format that normally uses a companion MTL file, while the MTL points to external image files. That is why the downloaded package should stay together.

Step three: unpack the result correctly

If the converter downloads a zip, extract all of it into one folder. Do not scatter the files across separate locations.

The result should include:

  • An .obj file containing the mesh geometry, groups, normals, and UV coordinates
  • An .mtl file containing material definitions
  • PNG files representing the texture maps that were carried over

The OBJ references the MTL by name. The MTL then references the PNG files by name. This chain is simple, but it breaks if the files are renamed or separated.

If the model opens gray in another application, first check that the MTL sits beside the OBJ and that the PNG files have their original names. A gray model does not necessarily mean the geometry is damaged; it often means the application could not find the material library or images.

The conversion keeps the model’s mesh and node transforms, with transforms baked into the OBJ. If the glTF contains several meshes, the exported OBJ preserves them as separate OBJ objects. The scene’s UV coordinates are retained for texture placement.

Which materials carry over?

OBJ and MTL are older formats than glTF, so they do not provide a direct home for every glTF material property. The useful way to think about the conversion is that basic surface appearance carries over, while much of the physically based shading setup does not.

Base color

The glTF base color factor is written to the MTL as Kd. If the material uses a base color image, that map is written as a PNG and referenced with map_Kd.

This is the main texture to preserve when moving an asset into an older renderer, sculpting package, or a workflow built around OBJ. It generally carries the visible color and pattern that viewers expect to see.

Normal detail

A glTF normal texture is linked from the MTL with map_Bump and written as a PNG. This can preserve surface detail such as grooves, panel lines, or small bumps, provided the destination application reads that MTL entry correctly.

A normal map changes how light appears to react to a surface; it does not add physical thickness or change the mesh silhouette. If the next stage is 3D printing, the normal map will not create raised detail in the exported geometry.

Alpha

Alpha information is written to the MTL as d. Support for transparent materials varies between applications, so check the result in the target software instead of assuming that every renderer will interpret it identically.

Properties that are dropped

Metallic, roughness, occlusion, and emissive information do not have standard OBJ material slots in this conversion and are dropped. glTF extensions such as texture transforms, clearcoat, and transmission are also dropped.

Skins, morph targets, and animation are not exported. The mesh is written in the pose it has when loaded. Cameras and lights are not included because OBJ describes mesh geometry and its basic material references, not a complete animated scene.

This is why OBJ is a good handoff for mesh-focused work but a poor replacement for glTF when the asset still needs animation, physically based shading, or scene lighting.

Step four: inspect the OBJ package

After extraction, open the OBJ with the OBJ Viewer before importing it into a larger application. Add the OBJ, MTL, and PNG files together, or drop the zip containing them.

The viewer can show the model with its materials, orbit the camera, switch to wireframe, and display triangles, vertices, meshes, and bounding-box dimensions. If a side file is missing, the model can still open, but an amber note identifies what was not included.

Wireframe inspection is useful for confirming that the model has the expected parts and that the conversion did not leave you with an empty or partial scene. The mesh count also helps distinguish a scene made from several objects from a single object containing loose pieces.

Pay attention to scale at this stage. glTF uses meters, while OBJ has no unit field. The converter keeps the glTF values, so an asset authored in meters remains numerically expressed in meters. A destination application that assumes another unit system may display an unexpected size even though the geometry itself is correct.

The viewer also helps separate a material problem from a geometry problem. A correctly shaped gray model with a missing-file note usually needs its MTL or texture images supplied. A damaged silhouette or missing mesh needs investigation in the source glTF.

OBJ Viewer showing a textured model, wireframe controls, and model statistics

The viewer is useful for checking the extracted OBJ package before sending it to another application.

When OBJ is not the right output

If the goal is a portable web or game asset, use the glTF to GLB converter instead. GLB packs the JSON, binary geometry, materials, textures, and animation into one file, so there are fewer side files to lose. It also keeps skins and animation that an OBJ conversion drops.

For a print workflow, OBJ is usually an unnecessary intermediate format. The glTF to STL converter converts meters to millimeters, changes the orientation to Z-up, and places the model on the build plate. STL discards color, textures, UVs, and materials, but that is often appropriate for a single-filament print.

Use OBJ when the next application specifically expects Wavefront geometry, MTL materials, or external texture maps. Use GLB when the scene needs to remain a complete real-time asset. Use STL when the destination is a slicer and only the shape matters.

FAQ

Can I upload only the .gltf file?

Only if it is an embedded glTF with its geometry and images inside the JSON, or if it is a single-file GLB. A separate glTF needs its .bin and any images as well. Select them together or zip the complete folder.

Why did the OBJ download without visible textures?

The material package may be incomplete. Check that Include materials & textures was enabled, then extract the OBJ, MTL, and PNG files into one folder without renaming them. If an image was absent from the source package, the model can still convert but will open without that texture.

Does OBJ keep the original glTF material?

It keeps the base color factor, base color texture, normal texture, and alpha reference where those values are present. Metallic, roughness, occlusion, emissive, and several glTF extensions are dropped. The mesh and UV coordinates remain, but the destination application may interpret the older MTL material differently.