Tools / 7 Days to Die

7 Days to Die Corrupted Region Repair

World won't load since 3.0? It's almost always a corrupted region - the game wrote a chunk over a .7rg file's header mid-save. Point this page at your save's Region folder: it runs the same structural check our hosting uses server-side (header magic, 4096-byte sectors, chunk table), rebuilds the clobbered header to recover every surviving chunk, or drops a single torn chunk so only that 16×16 area regenerates.

Your save never leaves your browser. It reads and repairs the region files locally, builds the repaired zip on your machine, and never touches your originals - the zip keeps every damaged file under .corrupt/ as a backup.

Your save never leaves your browser Structural .7rg check - magic, sectors, chunk table In-place rescue; originals kept as .corrupt

Pick your Region folder

Your world's regions live in the save's Region folder - on Windows under %APPDATA%\7DaysToDie\Saves\<World>\<Game>\Region\, on a dedicated server under the save path you set. Pick that Region folder (or the save folder above it). Stop the server first - repairing under a live server just re-corrupts it.

This runs entirely in your browser and needs JavaScript - without it nothing here can read the folder (there's no upload either way). The manual steps below explain the same fix.

Want this on a real server? Supercraft hosts 7 Days to Die →

What "corrupted region" means since 3.0

A 7 Days to Die world is split into .7rg region files, one per 512×512-block area, in your save's Region folder. Each is a container of 4096-byte sectors: sector 0 is a header that begins with the bytes 7rg, sector 1 is a table of where each of the region's 1024 chunks lives, and the rest is chunk data.

Since 3.0, an interrupted save can write a chunk record straight over sector 0 - the header magic vanishes and the server refuses to load the world, usually with an "incorrect region file header" style error. The important part: the chunk table in sector 1 usually survives intact. So restoring sector 0 to a clean header - four magic bytes and zeros, exactly what a healthy header holds, and a byte a region never points at - brings back every chunk the table still tracks. When a single chunk instead has a broken entry, zeroing just that entry makes the game regenerate that one 16×16 chunk and keeps the other 1023.

This is a structural repair - it never decodes your blocks, only fixes the container - which is why it's safe and why it's exactly what our own server-side auto-repair does to the same files.

Manual repair (what the tool automates)

Stop the server so nothing writes to the region files.
Back up the whole Region folder.
If the world still won't load, restore the affected r.X.Y.7rg from an earlier backup copy (an older save, or your host's backups) - the reliable manual fix.
Start the server and confirm the world loads before deleting the backup.

This tool does the in-place rescue a manual backup-restore can't: it recovers the current region (and everything built since the last backup) by repairing the file itself. Need a fresh world instead? Generate a quality-checked 7DTD world. Prefer it hosted with automatic region repair and backups? Run a 7 Days to Die server with Supercraft.

FAQ

Is my save really not uploaded?

Really - there's no upload endpoint on this page. Reading the folder, checking each region, and building the repaired zip all happen in your browser.

Can it fix a region with no good data left?

No tool can rebuild data that isn't on disk. If a region's header is gone and its chunk table didn't survive, or the file is truncated, it says so and points you to a backup restore for that one region instead of handing you a broken file.

Does it work for both single-player and dedicated servers?

Yes - the .7rg format is the same. Pick the Region folder from either, and drop the repaired files back into the same place.

My 7 Days to Die world won't load since 3.0 - is it a corrupted region?

Almost always. Since the 3.0 update the game intermittently writes a corrupt region file - a chunk record gets written over the region header when a save is interrupted, and the world fails to load. This tool reads your Region folder, finds the region file whose header was destroyed, and rebuilds the header so every chunk the file still tracks comes back. It uses the same structural check and rebuild our hosting runs server-side.

What is a .7rg region file?

A .7rg file stores one 512x512-block region of your world as 4096-byte sectors: sector 0 is a header that starts with the bytes 7rg, sector 1 is a table listing where each of the region's 1024 chunks lives, and the rest is chunk data. Corruption breaks that structure - the header magic goes missing, or a chunk's entry points nowhere - and this tool checks and repairs exactly those things without ever decoding your actual blocks.

Will I lose my base?

Usually not. Rebuilding a corrupted header recovers every chunk whose table entry survived - typically the whole region minus whatever the bad save had already dropped. If a single chunk is torn beyond repair, only that one 16x16 chunk is regenerated from the seed; every other chunk, including your base if it's elsewhere, is preserved. The tool keeps your original files as a .corrupt backup either way.