Deltarune’s save system looks deceptively simple on the surface, but under the hood it’s doing some extremely specific bookkeeping that directly affects how progress carries between chapters, how choices are remembered, and why certain routes lock you out permanently. If you’ve ever wondered why a dialogue line changes hours later, why Chapter 2 refuses to recognize a fresh file, or why a save breaks after a manual edit, this is where it all clicks.
Toby Fox designed Deltarune’s saves to behave more like a long-running RPG campaign than a traditional chapter-based game. Every action feeds into a growing web of flags, and the game is ruthless about enforcing them. Understanding this structure is essential if you plan to back up saves, transfer progress between PCs, or experiment with alternate routes.
Chapters Are Modular, But Not Isolated
Each chapter of Deltarune is technically its own executable experience, but they are absolutely not self-contained. When you complete Chapter 1, the game writes persistent data that Chapter 2 actively reads and reacts to. This includes party composition outcomes, key story decisions, and even subtle behavioral flags tied to optional interactions.
That’s why Chapter 2 doesn’t simply ask for a save file. It scans your existing Deltarune save data and checks for valid Chapter 1 completion markers. If those markers are missing or corrupted, Chapter 2 treats you like a fresh player, regardless of what you remember doing.
Save Slots Are Shared Across Chapters
Deltarune uses a small number of global save slots rather than per-chapter slots. When you load a slot in Chapter 2, you’re not creating a new file from scratch. You’re extending an existing data chain that already contains Chapter 1 state.
This is critical for modders and save scummers. Overwriting a slot doesn’t just reset one chapter, it can wipe flags that later chapters expect to exist. That’s why blindly copying files between machines can lead to soft-locks, missing NPCs, or broken cutscenes.
Game Flags Are the Real Save File
The most important part of Deltarune’s save system isn’t your visible progress, it’s the internal flags. These are boolean and numeric values that track everything from major route decisions down to whether you checked a random object in a side room.
These flags determine dialogue branches, shop inventories, boss behavior, and even how characters perceive Kris. Some flags persist across chapters permanently, while others are chapter-scoped and safely reset. Editing or losing the wrong flag can permanently alter a playthrough in ways the game never explains.
Why Save Location and Backups Matter
On PC, all of this data is stored outside the game’s install directory, inside your user profile. That design choice allows updates and chapter releases without nuking progress, but it also means uninstalling the game does not delete your saves. Conversely, moving to a new PC without copying that folder means starting from zero.
If a save goes missing or becomes unreadable, it’s almost always because the game can’t find or parse those flag files. Cloud sync conflicts, manual edits, or OS-level permission issues are the usual culprits. Knowing how the system is structured is the difference between a clean restore and losing dozens of hours to RNG, boss retries, and route experimentation.
Deltarune Save File Locations on Windows (Steam, GameMaker Structure, and AppData Breakdown)
Now that you understand why Deltarune’s flags matter more than your visible progress, the next step is knowing exactly where those flags live on a Windows PC. This is where most players get tripped up, especially when Steam Cloud, reinstalls, or multiple Windows accounts enter the picture. Deltarune doesn’t store saves where you think it does, and it definitely doesn’t care where you installed the game.
The Exact Windows Save File Path
On Windows, Deltarune stores all save data inside your user profile, not the Steam install directory. The default path is:
C:\Users\[YourUsername]\AppData\Local\DELTARUNE\
This folder contains every save slot, every chapter flag, and every persistent variable the game uses. If this directory is missing or unreadable, Deltarune will behave like you’ve never played before, even if Steam says you have dozens of hours logged.
Why AppData Is Used Instead of the Steam Folder
Deltarune is built using GameMaker Studio, and this structure is standard for GameMaker-based games. GameMaker writes saves to AppData\Local by design to avoid permission issues and to survive updates or reinstalls. That’s why uninstalling Deltarune from Steam does not delete your progress.
For modders, this separation is huge. You can freely verify files, swap branches, or even move between Steam and non-Steam builds without touching your saves, as long as that AppData folder stays intact.
Steam Version vs Non-Steam Version on Windows
Here’s the key detail most guides miss: both Steam and non-Steam Windows versions of Deltarune use the same AppData\Local\DELTARUNE folder. There are no duplicate save directories. Launching the Steam build and the itch.io build will read from the same pool of save data.
This is great for testing mods or older builds, but dangerous if you’re experimenting with save edits. One bad flag edit can break every version of the game on your system instantly.
Breaking Down the Save Files Inside the Folder
Inside the DELTARUNE folder, you’ll see multiple files with simple names, usually starting with filech1_, filech2_, or similar variations depending on your progress. These are not separate “chapter saves” in the traditional sense. They are segments of a shared data structure.
There is also a config file that stores settings like keybinds and resolution. Deleting that won’t reset your story progress, but deleting or corrupting the chapter files absolutely will. For save scummers, this means you can back up individual decision states, but only if you know which file corresponds to which slot.
How to Safely Back Up or Transfer Saves on Windows
To back up your progress, fully close Deltarune first. Then copy the entire DELTARUNE folder from AppData\Local to another location, like a USB drive or cloud storage. Do not copy individual files unless you know exactly which slot and chapter state you’re targeting.
When transferring to a new PC, paste that folder into the exact same AppData\Local path under your new Windows username. Launch the game after the transfer, not during. If the folder is placed correctly, Deltarune will instantly recognize all slots and flags without any extra steps.
Common Windows-Specific Save Problems and Fixes
If your saves suddenly vanish, the first thing to check is whether Windows is logged into the same user profile as before. AppData is per-user, and switching accounts is functionally the same as switching PCs. Steam Cloud conflicts can also overwrite local files, especially if you launch the game on two machines without syncing properly.
If a save becomes corrupted, restoring a backup of the DELTARUNE folder is the only reliable fix. Verifying game files through Steam won’t help, because the issue isn’t the executable, it’s the flag data. When Deltarune can’t parse a file, it doesn’t crash, it silently treats the slot as empty, which is why these problems feel so brutal and unexplained.
Deltarune Save File Locations on macOS (Library Paths and Version Differences)
If Windows hides saves behind AppData, macOS takes that philosophy and cranks it to nightmare difficulty. Apple tucks Deltarune’s saves inside the user Library, a folder that exists but is deliberately hidden from casual browsing. Once you know where to look, though, macOS save management is just as controllable as on PC.
Default macOS Save File Path
On modern macOS versions, Deltarune stores its save data in your user Library, not the system-wide one. The full path is:
~/Library/Application Support/DELTARUNE/
The tilde represents your macOS user account, so this path is unique per user, just like AppData on Windows. If you’re missing saves after a reinstall or device swap, nine times out of ten you’re logged into a different macOS account.
How to Access the Library Folder on macOS
Finder won’t show the Library folder by default, which is why many players assume their saves are gone. In Finder, click Go in the top menu bar, then hold the Option key to reveal Library in the dropdown. From there, navigate into Application Support and you’ll see the DELTARUNE folder sitting alongside other indie titles.
Alternatively, you can hit Command + Shift + G in Finder and paste the full path directly. This is the fastest method if you’re doing repeated backups or testing save edits and don’t want to fight macOS UI friction every time.
Steam vs DRM-Free Versions on macOS
For most players using Steam, the save path above is consistent across macOS versions. Steam does not sandbox Deltarune saves the way it does on iOS-style environments, so everything stays in Application Support. Steam Cloud can sync these files, but it can also overwrite them if two machines disagree on progress.
If you’re using a DRM-free build, the save location is typically identical, but older experimental builds have been known to create duplicate DELTARUNE folders. When saves appear to “reset,” check for multiple folders with similar names and confirm which one is actually being updated when you launch the game.
macOS Version Differences and Edge Cases
On older macOS versions, especially pre-Catalina systems, some players report saves appearing under:
~/Library/Containers/com.tobyfox.deltarune/Data/Library/Application Support/DELTARUNE/
This usually happens if the game was run in a sandboxed environment or migrated during an OS upgrade. If your saves vanish after a macOS update, search your Library for “filech” to locate orphaned chapter data before assuming it’s gone for good.
Backing Up and Transferring Saves on macOS
Just like on Windows, the golden rule is to fully quit Deltarune before touching anything. Copy the entire DELTARUNE folder, not individual files, and store it somewhere safe. This preserves all flags, chapter states, and slot data without risking desync issues.
When transferring to another Mac, paste the folder into the same Application Support path under the new user account. Launch the game after the transfer, not during. If the folder structure is correct, Deltarune will instantly recognize every save slot with zero setup.
Common macOS Save Issues and Fixes
The most common macOS issue is Steam Cloud winning a bad RNG roll and overwriting local progress. If your saves disappear, immediately disable Steam Cloud for Deltarune and restore your backup before relaunching. Opening the game first can permanently sync an empty state.
Another frequent problem is macOS permissions. If the game can’t write to Application Support, saves won’t update even though the game appears to run normally. Checking folder permissions and ensuring your user account has read and write access can prevent silent save failures that feel unfairly punishing.
Deltarune Save File Locations on Linux & Steam Deck (Native Linux and Proton Paths)
If macOS feels strict about permissions, Linux adds another layer of complexity thanks to native builds, Proton compatibility, and Steam Deck’s custom file system. The upside is full control. The downside is that Deltarune can store saves in entirely different places depending on how you launched the game.
Understanding which runtime you’re using is critical before you start copying files or rolling back progress. Native Linux and Proton do not share save paths, and mixing them without realizing it is one of the most common causes of “lost” saves on Deck and desktop Linux.
Native Linux Save File Location
If you’re running the native Linux version of Deltarune, either from Steam or a DRM-free build, saves are stored in your local config directory. The default path is:
~/.config/DELTARUNE/
Inside that folder you’ll find the familiar save structure, including filech0, filech1, and associated flag data. This behaves almost identically to Windows and macOS, just hidden behind Linux’s dot-folder convention.
Some desktop environments or custom setups may redirect config paths. If the folder isn’t there, search your home directory for “filech” while the game is fully closed to locate the active save directory.
Steam Proton Save File Location (Desktop Linux)
If you’re running Deltarune through Proton, Linux treats it like a Windows game inside a compatibility layer. That means the save files live inside Steam’s Proton prefix, not the native config folder.
The default path looks like this:
~/.steam/steam/steamapps/compatdata/1671210/pfx/drive_c/users/steamuser/AppData/Local/DELTARUNE/
The number “1671210” is Deltarune’s Steam App ID. If you don’t see that folder, double-check the game’s properties and confirm Proton is enabled.
Steam Deck Save File Location
On Steam Deck, the rules are the same, but the file system is deeper. In Gaming Mode, saves are invisible, so you must switch to Desktop Mode to access them.
For Proton-based installs, the save path is:
/home/deck/.local/share/Steam/steamapps/compatdata/1671210/pfx/drive_c/users/steamuser/AppData/Local/DELTARUNE/
If you’re running a native Linux build on Deck, the saves instead appear under:
/home/deck/.config/DELTARUNE/
Knowing which one exists tells you instantly how the game is running under the hood.
Native vs Proton Conflicts and “Missing” Saves
Switching between native Linux and Proton is where things get dangerous. Each runtime uses a different folder, so the game can appear to wipe your progress when it’s really just reading from an empty directory.
If your save vanishes after toggling Proton, don’t panic. Check both locations and compare timestamps to see which one was last updated. Copying the entire DELTARUNE folder from one path to the other can fully restore progress if done while the game is closed.
Backing Up and Transferring Saves on Linux and Steam Deck
As with every platform, never copy files while Deltarune is running. The game writes save data aggressively, and interrupting that process can corrupt flags or chapter states in subtle ways.
For backups, copy the entire DELTARUNE folder, not individual files. This preserves chapter unlocks, slot metadata, and hidden state values that aren’t obvious at a glance.
When transferring between Linux PCs or a Steam Deck, paste the folder into the correct runtime path before launching the game. If the directory matches the build you’re using, Deltarune will load your saves instantly with no extra configuration.
Linux-Specific Save Issues and Fixes
The most common Linux issue is file permissions. If Deltarune can read saves but can’t write them, progress won’t update even though everything looks fine in-game. Ensuring your user account owns the DELTARUNE folder and has write access fixes this instantly.
Steam Cloud can also cause silent rollbacks on Linux, especially when switching between Desktop Linux and Steam Deck. If you notice saves reverting, disable Steam Cloud, restore your local backup, and relaunch once to lock the correct state.
When in doubt, trust timestamps, not assumptions. Linux gives you full visibility into what the game is doing, and with the right path, no save is ever truly gone.
Identifying the Correct Save Files (filech0, filech1, config, and What Each File Does)
Once you’ve found the right DELTARUNE folder for your operating system and runtime, the next step is understanding what you’re actually looking at. Deltarune’s save system is deceptively simple on the surface, but each file plays a specific role in tracking progress, flags, and global state.
If you’re backing up, modding, or save scumming, knowing which file does what is the difference between a clean restore and a broken chapter select.
filech0, filech1, filech2: Chapter Save Data Explained
The files named filech0, filech1, and filech2 are the core chapter save files. Each one corresponds directly to a chapter slot, not a save slot in the menu. If filech1 exists, Chapter 1 has been completed at least once on that profile.
These files store story flags, NPC states, item inventory, party composition, and combat-related variables. Choices that affect future chapters, including secret routes and hidden conditions, are locked into these files the moment they’re written.
If a chapter isn’t appearing in-game, check whether its corresponding filech file exists. No file means the chapter hasn’t been unlocked or the save was never written.
Understanding Save Slots vs Chapter Files
This is where many players get confused. Deltarune’s visible save slots in the menu are metadata layered on top of the chapter files, not separate save files per slot like traditional RPGs.
Multiple slots can reference the same chapter state internally. That’s why copying only one filech file without the rest of the folder can cause slots to load but crash, reset, or behave inconsistently.
For transfers or backups, always treat the chapter files as a linked set rather than independent progress points.
config: Global Settings, Flags, and Hidden State
The config file is not a save slot, but it’s just as important. This file stores global data like volume settings, control bindings, screen mode, and most critically, hidden progression flags that persist outside individual chapters.
Some secret conditions, unlock checks, and one-time events reference values stored here. Deleting or mismatching config while keeping chapter saves can cause odd behavior, including missing unlocks or altered dialogue triggers.
If you’ve ever wondered why a fresh install “feels” different despite identical chapter files, config is usually the reason.
Why Partial Copies Break Saves
Copying only filech0 or filech1 might seem logical, but it’s risky. Deltarune cross-references chapter files with config and slot metadata to validate progression.
When those references don’t line up, the game may silently overwrite data, reset flags, or fail to load a chapter entirely. This is especially common when moving saves between devices or mixing Steam Cloud with manual backups.
That’s why every safe transfer method involves copying the entire DELTARUNE folder as a single unit.
Quick Verification Before Launching the Game
Before launching Deltarune after any manual edit or transfer, do a quick sanity check. Make sure all filech files you expect are present, config exists, and timestamps match your most recent play session.
If something looks off, fix it now while the game is closed. Once Deltarune boots, it will happily rewrite saves based on whatever state it detects, and at that point, RNG isn’t on your side.
Understanding these files gives you full control over your progress. At this level, you’re not just backing up saves, you’re managing the game’s internal state exactly how the engine expects it.
How to Safely Back Up, Restore, and Transfer Deltarune Saves Between PCs
Once you understand how tightly Deltarune links its save data, backing it up stops being guesswork and starts feeling like proper state management. The goal here is simple: preserve the entire internal snapshot the game expects, not just your visible progress.
Whether you’re save scumming, moving to a new rig, or syncing progress between a laptop and desktop, the rules don’t change. Copy everything, move nothing while the game is running, and verify before launch.
Step 1: Locate the Deltarune Save Folder on Each OS
On Windows, Deltarune stores saves in AppData, not the Steam install directory. Navigate to C:\Users\[YourName]\AppData\Local\DELTARUNE. This is the folder that matters, not anything under Program Files.
On macOS, the save data lives in ~/Library/Application Support/DELTARUNE. You’ll need to use Finder’s Go to Folder option to access Library, since it’s hidden by default.
On Linux, including Steam Deck, look under ~/.config/DELTARUNE. If you’re using Proton, this is still the native location, not the Wine prefix.
If you’re not seeing the folder, launch the game once, create a save, exit cleanly, and check again.
Step 2: Perform a Clean Backup the Right Way
Before copying anything, fully close Deltarune. Alt-F4 mid-session is risky because buffered writes can leave files half-updated.
Copy the entire DELTARUNE folder as a single unit. That includes all filech entries, config, and any metadata files present, even if you don’t recognize them.
Paste the folder somewhere safe like a cloud drive, external SSD, or a versioned backup directory. If you’re save scumming, date-stamp each backup so you can roll back without guessing which state you’re restoring.
Step 3: Restoring Saves Without Triggering Resets
When restoring, the destination PC should not have Deltarune running. If the target machine already has a DELTARUNE folder, delete or rename it first to avoid file collisions.
Paste your backed-up DELTARUNE folder directly into the same path on the new system. The folder name must be exact, including capitalization on Linux.
Do not cherry-pick files or merge folders. This is how hidden flags desync and chapters mysteriously revert.
Step 4: Transferring Progress Between PCs or Steam Deck
For PC-to-PC transfers, manual copy beats Steam Cloud every time. Steam Cloud can lag behind or overwrite local data if it detects a mismatch, especially after reinstalls.
If Steam Cloud is enabled, disable it temporarily before launching on the new machine. Verify the transfer works locally first, then re-enable cloud syncing once you’re confident the save loaded correctly.
For Steam Deck, desktop mode makes this trivial. Copy the DELTARUNE folder to a USB drive or cloud service, then drop it into ~/.config on the Deck. Switch back to gaming mode only after verifying the files are in place.
Step 5: Post-Transfer Sanity Checks Before Playing
Before hitting Continue, check that your expected chapters are selectable and that settings like volume and controls match your old setup. Those are config-driven and confirm the transfer stuck.
If dialogue, unlocks, or chapter access feels wrong, quit immediately and re-check the files. Launching and saving again can lock in bad state and overwrite your clean backup.
At this point, you’re not just protecting progress. You’re controlling Deltarune’s internal logic on your terms, which is exactly how the game wants experienced players to handle it.
Using Saves with Mods, Demos, and Chapter Updates (Compatibility and Risks)
Once you’re confident your saves survive clean transfers, the next real test is throwing mods, demos, and new chapter updates into the mix. This is where Deltarune’s otherwise forgiving save system starts enforcing rules behind the scenes. Knowing how those rules work is the difference between seamless progress carryover and a soft-lock that looks random but isn’t.
How Mods Interact with Deltarune Save Files
Most Deltarune mods hook directly into the same DELTARUNE save folder rather than creating a sandboxed profile. That means modded runs often write extra flags, altered values, or experimental variables into your existing save slots.
If you load a heavily modded save in vanilla Deltarune, the game may ignore unknown data, but it can also misread progression flags. The result is missing dialogue, chapters unlocking early, or NPCs acting like you skipped major beats.
Best practice is brutal but effective: separate folders. Duplicate your DELTARUNE directory before launching any mod, rename it clearly, and only swap it back when you’re done. Treat modded saves like a different character file in an RPG with unstable balance.
Using Demo Saves with Full Chapter Releases
Deltarune’s demos and early chapter builds store saves in the same OS-level location, but the internal structure has evolved. Chapter 1 demo saves were never guaranteed forward-compatible, especially after Chapter 2 rewired progression checks.
When you drop an old demo save into a newer build, the game usually attempts a conversion pass on first launch. If it succeeds, you’ll see a brief pause before the title screen loads. If it fails, the save may appear but refuse to advance, or worse, silently reset chapter access.
Always back up demo-era saves separately before importing them. If the new build doesn’t recognize the file cleanly, don’t keep relaunching and hoping RNG fixes it. Each failed load risks overwriting the original data.
Chapter Updates and Save Flag Mismatches
Chapter updates are the most dangerous moment for save scummers and long-term players. New chapters often introduce additional global flags that check what you’ve done previously, not just which chapter you reached.
If you’ve ever restored an old backup mid-playthrough, those flags might not line up the way the update expects. That’s when you get locked doors, missing events, or characters reacting as if choices never happened.
Before installing a new chapter, archive your entire DELTARUNE folder and keep it untouched. Let the updated game create its own converted version first. If something breaks, you can revert without contaminating your clean pre-update state.
Steam Cloud, Mods, and Cross-Device Conflicts
Steam Cloud does not understand modded logic. It only sees timestamps and file size, which means a modded save can overwrite a clean one across devices without warning.
This is especially risky if you mod on a desktop and play vanilla on a laptop or Steam Deck. One auto-sync at the wrong time can propagate broken flags everywhere.
Disable Steam Cloud before any modded session, and only re-enable it when you’ve confirmed your active save folder is vanilla-safe. Manual control beats automation every time here.
Troubleshooting Missing or “Corrupted” Saves
If your saves don’t show up, the first thing to check is whether the game created a fresh DELTARUNE folder somewhere else. This often happens if the game runs under a different user profile or compatibility mode.
On Windows, confirm you’re in the correct AppData\Local path. On Linux and Steam Deck, capitalization matters in ~/.config, and a single typo creates a ghost directory the game happily uses instead.
If a save loads but behaves wrong, assume flag desync, not corruption. Restore a backup from before the issue appeared, launch once, and verify chapter access before saving again. Deltarune is resilient, but it trusts your files completely, so the burden of consistency is on you.
Fixing Missing, Reset, or Corrupted Saves (Permissions, Cloud Sync, and Recovery Tips)
When Deltarune “forgets” your progress, it’s almost never RNG or bad luck. It’s usually a permissions issue, a cloud sync conflict, or the game quietly writing to a different save directory than the one you’re checking.
The key is understanding that Deltarune doesn’t verify save integrity. It loads whatever it finds and assumes it’s correct, even if the data came from the wrong device, OS profile, or mod state.
Check File Permissions First (Especially After Updates or OS Changes)
If Deltarune launches but can’t see your saves, permissions are the silent killer. On Windows, right-click the DELTARUNE folder in AppData\Local and make sure your user account has full read and write access.
Linux and Steam Deck users should double-check ~/.config/DELTARUNE. If the folder was copied from another device, it may be owned by root or another user, causing the game to fail saves without throwing an error.
If saves reset every launch, the game is likely failing to write new data. Fix permissions first before touching cloud sync or backups.
Steam Cloud Desync and Save Rollbacks
Steam Cloud doesn’t know which save is “correct.” It only compares timestamps, and that’s where things go wrong. Launching Deltarune on a secondary device can overwrite dozens of hours if that machine has an older local save.
If your progress suddenly rolls back, immediately exit the game without saving. Disable Steam Cloud, then manually restore your most recent local backup before relaunching.
For long-term stability, treat Steam Cloud as a transport tool, not a safety net. Keep manual backups and only allow sync when both devices are confirmed to be in the same state.
Recovering Saves That Appear Corrupted or Incomplete
True corruption is rare. Most “broken” saves are actually flag mismatches caused by restoring partial files or mixing chapters from different versions.
Deltarune stores multiple save slots and system data together. Restoring only one file can desync global flags that control chapter access, NPC states, and locked interactions.
If something behaves wrong, restore the entire DELTARUNE folder from a known-good backup. Launch the game once, confirm chapters and menus behave correctly, then save fresh to re-stabilize the data.
When the Game Uses the Wrong Save Folder
Sometimes Deltarune creates a brand-new save directory without telling you. This usually happens when running the game as admin, in compatibility mode, or under a different OS user profile.
On Windows, confirm you’re in AppData\Local\DELTARUNE, not a duplicate under another user. On Linux, watch for lowercase or misspelled config folders, which the game will happily treat as valid.
If two folders exist, the most recently modified one is usually the active directory. Merge carefully, never overwrite blindly.
Last-Resort Recovery and Future-Proofing
If all else fails, copy every DELTARUNE folder you can find and archive them. Then let the game generate a clean save, and selectively reintroduce old files one launch at a time until the issue reappears.
Going forward, back up before mods, chapter updates, or device switches. One zipped folder can save dozens of hours and prevent irreversible flag damage.
Deltarune rewards long-term play and careful choices, but it expects the same discipline from your file management. Control your saves, don’t trust automation, and the game will never steal your progress again.