Custom maps transform the Rust experience. Instead of procedural generation, you get hand-crafted terrain, unique monuments, and designed gameplay flows. Here's how to host them.
Where to Find Custom Maps
RustMaps.com
The largest collection of both procedural map previews and custom maps. Filter by size, biome distribution, and features.
RustEdit Community
MapMakers share their creations in Discord communities. Quality varies - stick to well-reviewed maps from known creators.
Commission a Map
For a unique server identity, hire a RustEdit map maker. Custom maps create a distinctive server experience that can't be replicated.
Uploading Your Map
Step 1: Download the Map File
Custom maps come as .map files, typically 50-200MB depending on complexity.
Step 2: Upload via FTP
- Connect to your server via FTP (credentials in your hosting panel)
- Navigate to the server root directory
- Upload the
.mapfile
Step 3: Configure Server Startup
Add to your startup parameters:
+server.levelurl "file:///serverdata/custom.map"
Or if hosting the map file externally (HTTP):
+server.levelurl "https://yoursite.com/maps/custom.map"
Step 4: Restart
Restart the server. It will load the custom map instead of generating procedurally.
Performance Considerations
Custom maps can be more or less demanding than procedural maps:
Potentially better performance:
- Map maker can optimize entity placement
- Known terrain means better pre-caching
- No dynamic terrain generation needed
Potentially worse performance:
- Over-decorated maps with thousands of custom entities
- Complex terrain meshes (mountains with lots of detail)
- Too many custom monuments or prefabs
Map Size Guidelines
| Players | Recommended Map Size | |---------|---------------------| | 20-50 | 3000-3500 | | 50-100 | 3500-4000 | | 100-200 | 4000-4500 | | 200+ | 4500-5000 |
Bigger isn't always better. A 5000-size map with 80 players feels empty. Match map size to your expected population.
Wipe Considerations
Custom maps persist across wipes differently:
Buildings wipe, terrain stays: When you wipe, player constructions are removed but the custom terrain remains. No regeneration needed - the same map loads instantly.
Map rotation: Some servers rotate through multiple custom maps each wipe. Upload all maps and change the server.levelurl parameter each wipe.
Map updates: If the map maker releases an update, you need to re-upload and restart. Player buildings will be lost (same as a wipe).
Testing Your Map
Before deploying to your live server:
- Set up a test server instance on Space-Node
- Load the custom map
- Fly around in admin mode checking for:
- Missing or floating monuments
- Water level issues
- Resource spawning (ore nodes, trees)
- Performance in dense areas
- Run a simulated load test if possible
Common Issues
Map doesn't load:
- Verify the file path in
server.levelurlis correct - Check that the map was made for your Rust version
- Ensure the file uploaded completely (compare file sizes)
Missing resources:
- Custom maps need spawn points defined for resources
- Contact the map maker if nodes/trees are missing from areas
Performance drops in specific areas:
- The map likely has too many prefabs/entities in that area
- Report to the map maker or avoid using that section
Custom maps are one of the best ways to differentiate your Rust server. They create unique experiences that players can't get elsewhere, building loyalty and community identity.
