Prerequisites
Before you begin, ensure you have:- BSPSource installed (see installation guide)
- A Source engine BSP file to decompile
- Basic familiarity with Source engine maps
Using the GUI
The graphical interface is the easiest way to get started with BSPSource.Launch BSPSource GUI
Run the appropriate launcher for your platform:
- Windows: Double-click
bspsrc.bat - Linux: Run
./bspsrc.shin terminal - JAR: Run
java -jar bspsrc.jar(with no arguments)
Select your BSP file
Click Browse next to the input field and select the
.bsp file you want to decompile.You can also drag and drop BSP files directly into the window.Configure options (optional)
Common options to consider:
- Extract embedded files - Essential for workshop maps with custom content
- Brush mode - Choose decompilation method (default: BRUSHPLANES)
- Debug mode - Adds extra information to output (useful for learning)
Start decompilation
Click Decompile to begin the process.Progress will be shown in the output window. The VMF file will be created in the same directory as the BSP file.
Using the CLI
The command-line interface offers more control and is ideal for batch processing.Basic Decompilation
Decompile a single BSP file:map.vmf in the same directory as the input file.
Common Options
- Extract Embedded Files
- Custom Output Path
- Brush Mode
- Selective Decompilation
Extract materials, models, and sounds embedded in the BSP:Creates a
map/ folder with extracted content. Essential for workshop maps.Debug Mode
Enable verbose output and extra VMF data:- Shows detailed processing information
- Adds comments to VMF with source data
- Helps diagnose decompilation issues
Batch Processing
Decompile all BSP files in a directory:Complete Example: Workshop Map
Here’s a complete workflow for decompiling a Steam Workshop map:Decompile with embedded file extraction
workshop_map.vmf- The decompiled mapworkshop_map/- Folder with extracted materials/models
Using BSPInfo
BSPSource includesbspinfo, a tool for inspecting BSP files without decompiling:
- BSP version and game
- Lump statistics
- Entity count
- Embedded files
- Protection detection
Next Steps
CLI Reference
Explore all command-line options and flags
Decompilation Modes
Learn about different brush decompilation strategies
Configuration
Deep dive into configuration options
Troubleshooting
Solve common decompilation issues
Common Issues
Gray textures or ERROR models
Gray textures or ERROR models
The map contains embedded materials/models that weren’t extracted.Solution: Re-run with
--unpack_embedded and move the extracted files to your game directory.Decompilation fails with error
Decompilation fails with error
The map may be protected or use an unsupported BSP version.Solution:
- Check BSP version with
bspinfo map.bsp - Try
--no_protto skip protection checks - See protection detection for details
VMF won't open in Hammer
VMF won't open in Hammer
The VMF may be too large or contain invalid data.Solution:
- Try selective decompilation (exclude entities with
--no_*flags) - Use
--brushmode ORIGFACEfor a smaller file - Enable debug mode (
-d) to see what’s failing
How do I know which game to specify?
How do I know which game to specify?
BSPSource auto-detects the game from the BSP header.To see all supported games:To override detection: