Watch the video:
Steps to fix the map glitch in Rust:
- Go to Steam > Right Click on Rust > Properties
- Go to the LOCAL FILES tab
- Click BROWSE LOCAL FILES…
- Open maps
- Select everything
- Delete
- The map will be redownloaded, and there should be no more issues
What causes the map glitch in Rust?
The “falling through the ground” map glitch in Rust is almost always the result of a corrupted or out-of-date map cache on your local machine. Rust streams world data from Facepunch’s servers as you explore, and stores what it has downloaded in the maps folder under your Rust install directory. When those files get out of sync with what the server is serving - for example, after a major update, a forced wipe that left leftover files behind, a partial download, or a hard crash mid-stream - your client tries to render geometry that no longer matches the server’s version of the world. The result is the classic “I can see the rock, but I’m walking through it” effect, missing terrain textures, floating objects, or being stuck in a “loading” limbo when you move between areas.
A failed or interrupted Steam download can also leave behind files that look complete to Steam but are actually truncated. Rust doesn’t always validate every chunk on launch, so a single bad sector can cause recurring fall-throughs even after a relaunch.
Why deleting the map files works
The maps folder is a client-side cache - it doesn’t contain anything the server doesn’t already have. By deleting it, you’re forcing Rust to redownload a clean copy of the world the next time you join a server. Steam doesn’t always know to do this on its own, especially if Steam’s “Verify integrity of game files” check passes even though the actual file content is wrong. The fastest path back to a working game is to wipe the cache and let Rust re-pull fresh data.
You can think of it like clearing a browser cache. The actual content lives on the server. You’re just throwing away your local copy of it so a clean one can replace it.
How long does the redownload take?
The redownload size depends on which map you play on. Procedural maps (the standard Rust map) are the largest - typically 2-4 GB of map data. Custom maps from the community are usually smaller. At a typical home internet speed the actual download is just a few minutes, but Rust processes and unzips those files when you join a server, so the first load after deletion can take noticeably longer than usual - sometimes 5-10 minutes the first time you load in, depending on your disk and CPU. Subsequent joins are fast because the files are already cached.
A small tip: if you’re on a slow connection, start the redownload overnight, or right after queueing into the server, so the delay doesn’t eat into your playtime.
How to verify the fix worked
After the maps are redownloaded and you’ve joined a server, check a few things to confirm the glitch is gone:
- Walk across multiple monuments and transition between biomes. The classic fall-through glitch usually appears when moving between areas, so if you can cross the map without falling, you’re good.
- Check the rock and tree geometry near your base. Glitches often cluster around heavy-build areas where a lot of objects are being streamed.
- Watch for the “loading chunks” indicator in the corner of the screen. If it pops up constantly even when you’re standing still, the cache is still rebuilding.
- If the glitch returns after a server restart, the issue is more likely on the server side than yours. Try a different server to confirm.
Other things to try if the glitch persists
If deleting the map files didn’t fix it, work through these in order:
- Verify game files in Steam (Rust → Properties → Local Files → Verify). This catches any other corrupted files outside the maps folder.
- Reinstall the Rust client entirely. A last resort, but it works when nothing else does.
- Check your disk health. Falling-through-the-map glitches that come back every wipe can be a symptom of a dying hard drive that’s silently corrupting small files.
- Update your GPU drivers. A small number of “map glitch” reports on the Facepunch forums turn out to be GPU driver crashes presenting as terrain issues.
