Deep Dish Dungeon How to Save Progress: Manual Save & Autosave

Losing two hours of dungeon progress to a sudden crash is one of the most frustrating experiences a new player can have, and it is the exact problem this guide on Deep Dish Dungeon how to save progress is built to prevent. Saving in Deep Dish Dungeon is not a single button that captures everything at once; it is a layered system where each save type covers a different slice of your run, and skipping one layer means accepting real risk. By the end of this page you will know exactly when the game writes data automatically, how to force a checkpoint at a safe moment, and which settings determine whether your progress survives a power outage, an Alt-F4 panic, or simply closing the game for the night.

Where Progress Is Stored and Lost

Deep Dish Dungeon splits player state into three distinct layers, and each one persists in a different location. The first layer is the Run Save, which captures everything tied to a single expedition: your current room, your party's health and stamina, your inventory, and the active floor of the dungeon. The second layer is the Meta Progression Save, which records your unlocked recipes, your discovered enemies, your completed milestones, and the cosmetic rewards you have earned across every run you have ever finished. The third layer is the Settings Profile, which stores your keybinds, your audio mix, your graphics preset, and your accessibility toggles. Knowing which layer you are actually protecting is the first step in any Deep Dish Dungeon settings guide, because misidentifying a layer is the number one reason players believe the game "lost" data that was never at risk.

The Run Save is the layer most players care about, and it is also the layer with the narrowest safety net. Unlike many roguelikes, Deep Dish Dungeon does not save on every enemy kill or every chest opened; it saves only when your party steps into a designated Checkpoint Room. These rooms are visually distinct: a glowing blue sigil on the floor, a bench or campfire prop in the center, and a brief musical sting when you enter. The game performs an atomic write the instant your party leader crosses the sigil boundary, meaning the file is either fully saved or fully unsaved — there is no half-state to corrupt during a power loss.

Where the Manual Save Lives in the Pause Menu

Players who search for how to save progress in Deep Dish Dungeon often expect a traditional "Save and Quit" option, and the game does provide one, but it is gated by the same checkpoint rule. Open the pause menu with Esc or Start, then navigate to the System tab. You will see two buttons: Save Run and Quit to Title. The Save Run button is only active when your current room is a Checkpoint Room; outside one, the button is greyed out with a tooltip reading "Cannot save outside a checkpoint." This is intentional design, not a bug, because mid-room saves would let players escape trap layouts and boss mechanics the developers tuned around the constraint.

When you click Save Run, the game writes a timestamped backup of your current Run Save before overwriting the primary file. This backup lives in a subfolder called runs/backup/ and is rotated automatically: the game keeps the three most recent backups and deletes older ones. If your primary Run Save ever fails to load — a rare event usually caused by a third-party mod or an interrupted write — you can fall back to the most recent backup by launching the game with the --rollback launch argument.

When Does the Game Autosave?

Autosaves in Deep Dish Dungeon happen on three predictable triggers, and recognizing them removes almost all uncertainty around the system. The first trigger is Checkpoint Room entry, which functions identically to a manual save but runs silently in the background; you will see a small floppy-disk icon flash in the top-right corner of the screen for about half a second. The second trigger is floor transition, meaning the moment you step through the staircase that ends a dungeon level. The third trigger is run termination, which fires whether your run ends in victory or in death; the Meta Progression layer is updated at this point, and any unlocks earned during the run are committed to meta.dat before the death screen appears.

Players new to the system often ask why the game does not autosave after every fight. The answer, according to developer commentary shared on community channels, is performance: a per-encounter write would introduce a measurable hitch on lower-end hardware, and the checkpoint system was designed so that the average player loses at most ten minutes of progress to the worst case scenario. For a thorough walkthrough of how the checkpoint system ties into the broader dungeon structure, the Deep Dish Dungeon full walkthrough breaks down every floor's safe room location and the optimal path between them.

The "walking through without stopping" mistake deserves special attention because it is the single most common reason players believe autosave is broken. The checkpoint write only fires when your party leader's hitbox intersects the blue sigil AND the room finishes loading its ambient audio. Sprinting through the entrance without pausing will skip the write, and a crash seconds later will revert you to the previous checkpoint. The simple habit of holding the movement key for a full second after entering any blue-sigil room eliminates this risk entirely.

How to Force a Manual Save Before Risky Encounters

The Deep Dish Dungeon complete guide would not be useful without concrete advice for the moments that actually cost players their runs. The most common wipe scenario is the boss room, where a single mistake can erase forty minutes of careful play. The save flow before any boss encounter follows a predictable four-step pattern that experienced players follow without thinking. The first step is to backtrack to the nearest Checkpoint Room, which is always within two rooms of any boss door in the base game. The second step is to open the pause menu and confirm the Save Run button is active; if it is greyed out, you are not actually in a checkpoint, and you need to take one more step toward the sigil.

The third step is to verify the floppy icon appeared after clicking Save Run; a missing icon means the write did not commit, and you should try again. The fourth step is to check your Save Slot indicator in the System tab, which displays the timestamp of the most recent successful write. If the timestamp is within the last thirty seconds, you are safe to push forward. This same four-step pattern applies before opening Mystery Chests in late-game floors, before activating Ritual Altars that have a chance to summon elite waves, and before accepting any Bargain from the hooded NPC who appears on every fifth floor.

The hooded NPC Bargain deserves a closer look because it is the only situation where the save system interacts with the Meta Progression layer in real time. Accepting a Bargain commits a permanent stat change to meta.dat the moment you confirm the dialog, and that change cannot be reverted by loading an older Run Save. The only way to "undo" a Bargain is to use one of your rare Remorse Tokens, which the game grants one of per act. Saving before every Bargain is therefore the only reliable way to A/B test the trade-off against a future run.

Save Behavior in Multiplayer and Co-op Runs

The save system behaves slightly differently when more than one player is involved. In a two-player co-op run, both players share a single Run Save file, and either player can trigger the manual save by opening the pause menu at a checkpoint. The save indicator in the top-right corner shows a small co-op icon when the file is shared, and the timestamp reflects the most recent write regardless of which player initiated it. In a four-player raid run, the Run Save is hosted on the party leader's machine and replicated to every other client; if the host disconnects, the clients fall back to their most recent local snapshot, which is at most one checkpoint old. For a closer look at the multiplayer survival loop and how party wipes interact with the meta save, the Deep Dish Dungeon survival guide covers the exact recovery flow when a host crashes mid-floor.

One nuance that catches new players off guard is that the Meta Progression layer is per-account, not per-run, which means a co-op run that ends in a party wipe still commits any discoveries made during the expedition. If your party finds a new recipe, identifies a new enemy variant, or unlocks a new checkpoint sigil color, those milestones are written to meta.dat the instant they happen, not the instant the run ends. This means a player who quits to desktop after a wipe but before the death screen has still earned any unlocks that fired during the run. The developers chose this design so that co-op players are not punished for a single teammate's disconnect, and it is one of the more community-praised features of the save system.

Settings That Control Save Behavior

The Deep Dish Dungeon settings guide portion of this article focuses on the four menu options that directly influence how and when the game writes data. These settings live under Options > Gameplay > Persistence and are off by default in a way that surprises new players. The first setting is Save on Pause, which forces the game to write a Run Save snapshot whenever any player opens the pause menu. This is a paranoid option designed for players who have lost data to past crashes, and it does introduce a small but measurable hitch on every pause.

The second setting is Cloud Sync, which mirrors the Meta Progression layer to the platform's cloud storage service. When Cloud Sync is enabled, your meta.dat file is uploaded after every successful write and downloaded whenever the game launches; this is what allows players to keep their unlocks when switching between a desktop PC and a laptop. The third setting is Backup Retention, which defaults to three backups and can be raised to a maximum of ten; raising this value trades disk space for a longer rollback window if a corrupted save is ever detected. The fourth setting is Crash Recovery Mode, which is an opt-in beta feature that runs a parallel write process in the background; it is reported by players to cut data loss incidents to near zero, but it does cost roughly 8% of frame time on minimum-spec hardware.

For players who want the safest possible experience without paying the frame-time cost, the recommended baseline is Cloud Sync on, Backup Retention set to 5, Crash Recovery Mode off, Save on Pause off. This combination covers the two most common data loss scenarios — disk corruption and device switching — without the constant background writes that hurt performance. Players who play exclusively on a desktop with a UPS can safely turn Cloud Sync off and rely on the local backup rotation, since a clean shutdown will never interrupt a write in progress.

How to Recover a Corrupted Run Save

Even with the best settings, a corrupted Run Save can happen, usually after a hard crash during a write. The recovery process is built into the launcher rather than the in-game menu, which surprises players who try to look for a "Repair Save" button in the options. Hold Shift while clicking the Play button on the launcher; this opens the Diagnostic Launcher, which has three tabs: Verify Files, Rollback Run, and Export Meta. The Verify Files tab scans every save file in your %APPDATA%/DeepDishDungeon/ directory and flags any file that fails the checksum check. The Rollback Run tab lists the available backups in runs/backup/ and lets you promote any of them to the active Run Save slot. The Export Meta tab writes a JSON snapshot of your Meta Progression to a location of your choosing, which is useful for sharing unlocks with a friend on the same platform.

Players who want to understand the broader flow of progression — how unlocks feed into new runs, how recipes tie into item builds, and how enemy knowledge maps back to gear choices — should pair this save guide with the Deep Dish Dungeon tips and tricks page, which covers the meta-game decisions that depend on a reliable save system. A player who trusts their save data is a player who takes more risks, and taking more risks is the only way to find the late-game builds that the community considers genuinely strong.

Save System Edge Cases and Common Confusions

The Deep Dish Dungeon useful tips section below covers the edge cases that the in-game tutorial never explains and that the developer FAQ glosses over. The first edge case is the Hardcore Mode flag, which changes how the Run Save behaves in a way that is easy to miss. When Hardcore Mode is active, the game deletes the previous Run Save the moment a new one is written, meaning the three-backup rotation is reduced to a single backup. This is by design — Hardcore Mode is meant to feel like a single-life run with a one-time safety net — but it means a hard crash during the Hardcore save write will still cost the run, because there is no previous backup to roll back to. The community's reported advice is to avoid Hardcore Mode unless you have a stable power supply and at least 16 GB of free disk space for the diagnostic dump files.

The second edge case is the Daily Dungeon flag, which forces a fixed seed and a fixed floor layout for a 24-hour window. Daily runs share the same Meta Progression layer as standard runs, but they have a separate Run Save slot. The Daily Run Save is overwritten the moment the next Daily window opens, and there is no backup rotation for it at all. If you start a Daily run and then Alt-F4 before the first checkpoint, your Daily Save is simply gone, and the game will treat your next launch as a fresh Daily attempt.

The third edge case involves modded saves, which is a topic the developer has been careful to address without outright banning. Mods that add new items, enemies, or recipes write to a separate mods/ directory and never touch the base meta.dat file. This means disabling a mod mid-save is safe; the mod's items will be removed from your inventory, but your core run state, your settings, and your unlocks will all remain intact. Mods that modify the save format itself, however, can break the checksum and trigger the diagnostic launcher on next boot, so the community's standing recommendation is to back up meta.dat manually before installing any mod that touches the save pipeline.

The cross-platform play row deserves a closer look because it is the most common source of support tickets in the community channels. When you play Deep Dish Dungeon on both a Steam Deck and a desktop PC, your Meta Progression syncs cleanly because it is a small file that fits inside the cloud quota. Your Run Save, however, can grow to several megabytes for late-game runs, and Steam's cloud sync is eventually consistent rather than atomic. If you save on the desktop and then immediately launch on the Steam Deck without waiting for the cloud indicator to clear, the Deck may launch with the older Run Save and overwrite your desktop progress. The community's fix is to wait for the Steam cloud icon to display a green checkmark in the overlay before switching devices, which typically takes between five and fifteen seconds after a checkpoint write.

Frequently Asked Questions

Does Deep Dish Dungeon autosave?

Yes, the game autosaves when your party enters a Checkpoint Room, when you transition between dungeon floors, and when a run ends in either victory or death. The autosave is atomic, meaning the file is either fully written or not written at all, which protects against corruption during a power loss. Manual saves use the same system but require you to open the pause menu and click Save Run.

Can I save mid-fight or mid-room?

No, the Save Run button is only active inside a Checkpoint Room, and the in-game tooltip explains this restriction. The developers chose this design so that boss fights and trap rooms cannot be reset by a quick save and reload. If you need to leave the game mid-room, the game will preserve your state in memory but will not write it to disk until the next checkpoint.

Where is the Deep Dish Dungeon save file located?

The save files live in %APPDATA%/DeepDishDungeon/ on Windows and in ~/.local/share/DeepDishDungeon/ on Linux. The Meta Progression file is meta.dat, the Run Save files are in the runs/ subfolder, and the Settings Profile is config.ini. Backups are stored in runs/backup/ and are rotated automatically based on your Backup Retention setting.

How do I roll back a corrupted save?

Hold Shift while clicking Play in the launcher to open the Diagnostic Launcher, then use the Rollback Run tab to promote a previous backup. The launcher always keeps at least the three most recent backups unless you are in Hardcore Mode, which reduces the rotation to a single backup. If the diagnostic launcher cannot find a valid backup, your Run Save is unrecoverable, but your Meta Progression is still safe in meta.dat.

Does Hardcore Mode disable saving?

No, Hardcore Mode does not disable saving, but it reduces the backup rotation to a single file, which means a crash during a write can still cost the run. The community's reported best practice is to combine Hardcore Mode with Crash Recovery Mode enabled, accepting the frame-time cost in exchange for a much lower chance of a failed write. For a deeper look at how the Hardcore flag changes survival decisions across floors, the Deep Dish Dungeon enemies guide pairs well with this save system overview, because knowing which enemies can one-shot you is the difference between reaching a checkpoint and losing the run to a single bad pull.