Convert OBJ to MDL

A game mod or legacy 3D application may require an MDL asset even when the source model is available only as an OBJ. Conversion is therefore needed to make the mesh loadable in a specific engine, editor, or Animation:Master project.

What the OBJ format is

OBJ is a plain-text interchange format for static 3D geometry. It can store vertices, texture coordinates, normals, polygon faces, smoothing groups, and references to named materials.

Material definitions normally reside in a separate .mtl file, and the referenced image textures remain separate files such as PNG, JPG, or TGA. OBJ does not reliably contain bones, skin weights, animations, collision geometry, engine shaders, attachment points, or level-of-detail data.

Blender, Maya, 3ds Max, Cinema 4D, ZBrush, MeshLab, and many CAD and game-content applications can import or export OBJ. It is commonly used to exchange a static mesh when the original application project is unavailable.

What the MDL format is

MDL is a family of unrelated, application-specific formats rather than one universal standard. The target program or game must be identified before choosing a converter.

In GoldSrc and Source-engine games, MDL is a compiled model asset. Depending on the engine and version, it is accompanied by files such as .VVD, .VTX, .PHY, material files, and engine-specific metadata. A compiled model can connect the mesh with bones, animations, collision data, hitboxes, material references, and engine settings. It is often more efficient for runtime use than a text OBJ, but it is not simply a renamed OBJ.

Quake-family games use another MDL variant with different limits and tools. Hash Animation:Master also uses an application-specific .mdl format; that file is not interchangeable with a Quake, GoldSrc, or Source model.

How to convert the mesh

First determine the exact target: Source, GoldSrc, Quake, Animation:Master, or another application. A Source compiler cannot create a GoldSrc or Animation:Master MDL, and a file extension change does not perform conversion.

1. Keep the OBJ, its matching .mtl, and all referenced texture images together. In Blender, use File → Import → Wavefront (.obj). Reassign materials if texture paths are broken.
2. Inspect the imported mesh and remove hidden geometry, duplicate vertices, non-manifold sections, and unsupported modifiers. Apply scale and rotation, recalculate normals, verify UVs, and triangulate if the target compiler requires predictable triangles.
3. Check the model's dimensions and axis orientation against the target application. OBJ files do not enforce a universal unit, up-axis, or coordinate convention.
4. For Source, install Blender Source Tools, assign materials and, for animated models, create a skeleton with vertex weights. Export a reference mesh as .SMD or .DMX. A static prop needs a reference mesh; an animated model also needs bones, animations, and usually a physics mesh.
5. Create a Source compiler script, normally a .qc file. It defines the output path, mesh, material directory, surface properties, sequences, collision model, and other options. A minimal static example is:

$modelname "props/example.mdl"
$body "Body" "example.smd"
$staticprop
$surfaceprop "metal"
$sequence "idle" "example.smd" fps 1
$cdmaterials "models/props"

6. Compile the script with Crowbar's Compile tab or the matching Source SDK studiomdl.exe. The compiler produces the MDL and the companion files required by the selected Source branch.
7. Copy the compiled files and engine material assets into the game's required directories, then test the model in the target game. Correct errors involving material paths, bone names, vertex limits, missing sequences, or collision data at the source or compiler-script level.

For GoldSrc, use a GoldSrc-compatible exporter and studiomdl version, because its skeleton, limits, QC commands, and output files differ from Source. For Quake MDL, use a tool that explicitly supports the required Quake revision; Noesis can handle some Quake model variants when the relevant import and export plugins are installed, but plugin support and animation handling vary.

For Animation:Master, use Animation:Master's supported OBJ import command and save the imported model in its native MDL format if that version supports the required OBJ features. Blender, Crowbar, and Source Tools do not produce Animation:Master MDL files.

Online and desktop options

Desktop conversion is usually the correct choice because game MDL creation requires a specific compiler and often requires rebuilding materials, skeletons, animations, and collision geometry. Blender with Blender Source Tools plus Crowbar is a practical Source workflow; the target engine's own exporter and compiler are preferable for other MDL variants.

CloudConvert, Convertio, and similar reputable online services can be useful for ordinary OBJ interchange or for producing an intermediate format, but they generally do not create a valid Source, GoldSrc, Quake, or Animation:Master MDL. Use an online service only when its format list names the exact MDL variant and its documented output includes the required companion files. Do not upload proprietary models or textures unless the service's privacy and retention terms are acceptable.

Quality and compatibility limits

Most OBJ files contain only a surface mesh. Bones, weights, animations, hitboxes, physics meshes, attachment points, engine shaders, and compile metadata must be created separately, so conversion cannot preserve information that was never present in the OBJ.

Missing .mtl files, absolute texture paths, unsupported material parameters, and incorrect case in material directories commonly produce an untextured model. Rebuild materials using the target engine's material scripts instead of assuming OBJ material names become usable shaders.

Apply transforms before export and verify scale with a known dimension. Check the target engine's polygon, vertex, bone, texture, UV, and material limits; a valid OBJ can still fail compilation or display incorrectly after conversion. Preserve the compiler logs and source files, because the generated MDL is normally a derived binary asset rather than an editable master model.