Convert STL to MDL

A game engine or specialist 3D application may require an MDL asset when an STL mesh is the only available model file. For Valve games, the conversion is a compile workflow that creates an engine-ready model and its companion files, not a simple file extension change.

What the STL format is

STL stores a surface as a triangle mesh in ASCII or binary form. It is widely used by 3D-printing slicers, CAD systems, 3D scanners, and mesh-repair tools; applications such as SolidWorks, Fusion 360, FreeCAD, Blender, MeshLab, and many slicers can import or export it.

STL normally contains only triangle geometry. It does not reliably preserve materials, textures, UV coordinates, bones, animation, object names, units, or scene hierarchy. Check the mesh for holes, inverted faces, duplicate triangles, non-manifold edges, and excessive polygon counts before conversion.

What the MDL format is

MDL is a family of unrelated formats, not one universal specification. Valve GoldSrc and Source use different MDL structures, while other software may use MDL for its own model, material, or data format. An MDL made for Half-Life 2 or Garry's Mod is not automatically readable by a program that expects another MDL variant.

For Valve engines, MDL is generally a compiled game asset. Depending on the engine and model type, it works with geometry, material references, collision data, skeletal information, animations, and engine metadata. Source models normally require companion files such as .vvd and a version-specific .vtx; collision output may include .phy. The complete output set must remain together.

MDL can reduce runtime loading work and package engine-specific rendering and animation data, but it is not a good interchange format. Keep the Blender, SMD, DMX, QC, texture, and source-mesh files for later editing.

How to convert STL to MDL

For a Source-engine model

1. Install Blender, the Blender Source Tools add-on, and a Source-compatible version of studiomdl.exe. Crowbar can provide a graphical interface for compiling and inspecting Source models, but it does not make compilers from different Source branches interchangeable.
2. Import the mesh with File → Import → STL. Confirm the intended units because STL has no mandatory unit declaration; a millimetre model can otherwise appear 25.4 times too large when interpreted as inches. Apply scale, rotate to the target engine's coordinate convention, and repair non-manifold geometry using Blender's 3D Print Toolbox or MeshLab.
3. Reduce the triangle count if the target game has vertex or polygon limits. Create UV coordinates and assign materials. STL supplies neither texture coordinates nor usable material definitions, so create the required material files separately; Source commonly uses VMT and VTF assets.
4. For a static prop, export an SMD or DMX reference mesh with Blender Source Tools. For a rigged or animated model, create an armature, bind the mesh, and export the reference and animation files required by the selected Source branch.
5. Create a QC compile script. A minimal Source static-prop example is:

$modelname myprops/example.mdl
$body studio example.smd
$staticprop
$surfaceprop plastic
$cdmaterials models/myprops
$sequence idle example.smd fps 30

Add a correctly built $collisionmodel when the prop needs physics, and use the QC commands required by the target game for body groups, skin families, animations, or flexes.

6. Compile with the matching tool, either through Crowbar or a developer command prompt:

studiomdl.exe example.qc

Copy the generated .mdl, .vvd, applicable .vtx files, optional .phy, and referenced material and texture files into the directory expected by the game. Test the model in that exact engine rather than relying only on a successful compile.

For GoldSrc models

Use a GoldSrc-specific exporter and compiler, such as a toolchain designed for the particular Half-Life or GoldSrc game. GoldSrc commonly uses SMD input and a GoldSrc QC script, but its compiler, limits, coordinate conventions, and output files differ from Source. Source Tools and Source studiomdl.exe are not substitutes for a GoldSrc pipeline.

For another MDL specification

Identify the application, product version, and exact MDL variant before choosing software. Import the STL into Blender, 3ds Max, MeshLab, or the application's own modeling tool, then use an exporter that explicitly names that MDL specification. Generic online services such as CloudConvert or Convertio may support some ordinary 3D formats, but they do not produce a usable Valve MDL compile and should not be treated as universal MDL converters. Do not upload proprietary meshes unless the service's storage and deletion terms are acceptable.

Quality and compatibility limits

This conversion is usually a reconstruction and compilation workflow. Triangle geometry may transfer, but textures, materials, UVs, rigging, animation, collision geometry, scale, smoothing, and metadata must be rebuilt or configured separately.

Inspect normals and shading after import because STL normal data is often incomplete or ignored. Check smoothing, sharp edges, duplicate vertices, and the model's origin and scale. A dense scanned STL may exceed engine vertex, bone, draw-call, or collision limits even after it compiles.

Compile with the tool supplied for the target engine branch and read every warning. Missing material paths, invalid collision meshes, unsupported bone weights, incorrect QC paths, and missing companion files can produce an MDL that compiles but renders incorrectly or fails to load.