What is SFM compile?

Source Filmmaker (SFM) is Valve’s free animation tool built on the Source engine. The engine never reads raw Blender, Maya or FBX files. Every model in SFM’s Model Browser is a compiled .mdl file, every texture is a .vtf file and every map is a .bsp file. Turning source files into those formats is what people mean by “SFM compile”.

The phrase covers two jobs:

• Asset compiling: turning meshes, textures, animations and maps into MDL, VTF and BSP files with studiomdl, VTFEdit and the Hammer map compilers.
• Render compiling: exporting a finished animation as a movie or image sequence, then joining the frames and sound into one file.

Compiling is worth learning even if you only use Workshop assets. Once you can compile, you can fix broken downloads, change skins and bodygroups, port your own characters and props, and share clean, lightweight assets with other animators.

The SFM compiler and the tools you need

The actual SFM compiler is studiomdl.exe, which ships with Source Filmmaker in its bin folder. It is a command-line program: it reads a QC file, follows every path inside it and writes the compiled model into the game’s models folder. Valve documents every QC command on the Valve Developer Community wiki.

Crowbar is a free community tool that wraps studiomdl in a simple window. It remembers your game setup, shows the compile log in a readable form and can decompile existing MDL files back into SMD and QC, which is the fastest way to learn how a working model was built.

How SFM compile works, step by step

Every model compile follows the same five steps, whether it is a simple crate or a fully rigged character.

A minimal QC file for a static prop with collision looks like this:

$modelname      "props/my_folder/my_prop.mdl"
$body           body "my_prop_ref.smd"
$cdmaterials    "models/props/my_folder/"
$surfaceprop    "metal"
$sequence       idle "my_prop_ref.smd"
$collisionmodel "my_prop_phys.smd" { $concave }

QC file commands explained

The QC file is where most compile problems start and end. These are the commands you will use in almost every SFM model:

Compiling textures for SFM: VTF and VMT

A texture in Source Filmmaker is always two files. The .vtf file holds the image, and the .vmt file is a small text material that tells the engine which shader to use and where the image is.

1. Save your texture as PNG or TGA with power-of-two dimensions, such as 1024 x 1024 or 2048 x 2048.
2. Open it in VTFEdit, choose Import, and save it as VTF inside materials/models/your_folder/.
3. Create a VMT file with the same name in the same folder, using the template below.
4. Make sure the $cdmaterials line in your QC points at that same folder.

"VertexLitGeneric"
{
    "$basetexture"  "models/props/my_folder/crate_diffuse"
    "$bumpmap"      "models/props/my_folder/crate_normal"
}

VertexLitGeneric is the standard shader for models. Leave the .vtf extension out of the path, and keep folder names lowercase.

Compiling animations for SFM

Animations are exported from your 3D software as separate SMD or DMX files, one per action, using the same skeleton as the reference mesh. Each one becomes a $sequence line in the QC:

$sequence idle  "anims/idle.smd"  fps 30 loop
$sequence wave  "anims/wave.smd"  fps 30
$sequence walk  "anims/walk.smd"  fps 30 loop

Recompile, then check each sequence in HLMV before opening SFM. Most animators keyframe inside SFM itself, so baked sequences are most useful for loops, idle poses and reusable actions.

Compiling maps for SFM

Maps are built in the Hammer Editor that comes with Source Filmmaker and saved as .vmf files. Compiling turns a VMF into a playable .bsp in three passes:

• VBSP builds the geometry and the world structure.
• VVIS works out what is visible from each area, which keeps the map fast.
• VRAD calculates the lighting, and is usually the slowest pass.

Hammer runs all three when you press F9. Save the result in game\usermod\maps so it appears in SFM’s map list. A map with leaks will fail VVIS, so seal the level before a full compile.

Compiling a render: video, image sequences and sound

When an animation is finished, open File, Export, Movie. SFM can write a video file directly or save every frame as an image sequence. For anything longer than a few seconds, an image sequence is the safer choice: if SFM crashes halfway, you keep every frame already rendered.

• Resolution and frame rate: match the export to your session settings so motion stays smooth.
• Sound: export the audio as a separate WAV file, then join it with the frames in a video editor or with ffmpeg.
• GIFs and short clips: export a short image sequence and convert it, rather than exporting video and cutting it down.
• Render quality: depth of field and motion blur samples add realism but multiply render time.

Optimization tips for a faster, cleaner compile

• Keep polygon counts sensible for the shot. Hero characters can be detailed; background props should be light.
• Use 2048 textures only where the camera gets close, and 1024 or 512 everywhere else.
• Add $lod meshes to heavy models used in wide shots.
• Remove unused bones and materials before exporting.
• Keep file and folder names lowercase with no spaces, and give each model its own folder.
• Compile small changes often instead of one large change, so you always know what broke.

Common SFM compile errors and how to fix them

Most failed compiles come down to a wrong path. Read the last lines of the compile log first, then match the symptom below.

SFM export corrupted

A corrupted or unplayable export usually comes from writing straight to a video format and hitting a codec or memory problem mid-render. Export an image sequence instead, then encode it into MP4 afterwards.

SFM keeps crashing

Crashes during work or export are most often caused by a broken custom model, too many high-poly models and lights, or very high render samples. Save often, remove the last model you added, and lower sample counts to find the cause.

SFM compile download: getting the tools safely

There is no single “SFM compile” program to download. You need a few free tools, and each has one official source:

• Source Filmmaker: free on Steam, Windows only. studiomdl and Hammer come with it.
• Blender: blender.org.
• Blender Source Tools, Crowbar and VTFEdit: their developers’ official pages.

Avoid sites offering an “SFM compile download” as a bundled installer or EXE. Those files are not needed for compiling and are a common way malware spreads.

Is SFM compile safe?

Compiling itself is safe. The tools are free, widely used and run on your own computer. The risks are unofficial downloads, covered above, and look-alike websites.

Some adult video sites use “SFM compile” in their names, such as sfmcompile.com and SFM Compile Club. SFM Compile (asfmcompile.com) is not one of them, has no connection to them and does not link to them. Everything on this site is safe for work, and it is not affiliated with Valve Corporation.

SFM compile FAQ