Custom Map Hosting: How to Upload Massive Custom Worlds Without Timeouts
Custom maps are one of Minecraft's killer features for server monetisation and community building. Adventure maps, survival islands, build competitions on custom terrain — they draw players in ways that vanilla generation cannot. But getting a 2 GB custom world from your hard drive onto your server without corruption or timeout is where many admins struggle. Here is the correct process for reliable transfers.
Understanding the World Folder Structure
A Minecraft Java world consists of three dimensions stored in separate folders:
world/ ← Overworld
world_nether/ ← Nether (folder name: DIM-1)
world_the_end/ ← End (folder name: DIM1)
When you download a custom map, it may be structured differently. Before uploading anything, verify:
- Where the
level.datfile is located - Whether the nether/end are included or separate
A level.dat in the root of the zip means that folder IS the world folder and uploads to world/.
Method 1: SFTP Upload (Recommended for Files Under 5 GB)
Use a proper SFTP client — FileZilla or WinSCP — not the browser-based file manager in most panels. SFTP clients handle large transfers reliably with automatic retry on timeout.
Configuration:
- Protocol: SFTP
- Host: your server IP
- Port: 22 (or your host's SFTP port)
- Login: your server's SFTP credentials from Space-Node panel
Transfer your world folder directly to the /home/container/ directory (Pterodactyl path), replacing the existing world folder after stopping the server.
Method 2: Compressed Upload + Server-Side Extraction
For worlds over 2 GB, compress them locally first:
# On Linux/Mac
tar -czf myworld.tar.gz world/
# On Windows (PowerShell)
Compress-Archive -Path world -DestinationPath myworld.zip
Upload the single compressed file (much faster, fewer individual file requests), then extract server-side via the panel's console or an SSH connection:
tar -xzf myworld.tar.gz
This avoids the timeout issues caused by uploading thousands of individual chunk region files (.mca) one at a time.
Common Upload Problems and Solutions
"Level.dat is corrupt" — Usually caused by an incomplete upload. Delete everything and re-upload from a fresh stop. Never upload to a running server.
World loads but looks like void — The world folder name does not match level-name in server.properties. Set level-name=world (or whatever your folder is named).
Old world still loading after upload — The server cached the old world in memory. Full stop, not restart. Then start fresh.
Chunks missing after upload — The region folder structure is wrong. Each dimension's chunks are in region/ inside the world folder. Verify the structure matches: world/region/*.mca.
Pre-Generation After Upload
After uploading a custom map, run a chunk pre-generation pass to cache the terrain before players arrive:
/chunky radius 3000
/chunky start
The Chunky plugin pre-generates all chunks within 3,000 blocks, ensuring the first players to explore don't trigger world-generation lag. On Space-Node's NVMe storage, a 3,000-block radius generates in under 5 minutes.