Neon Abyss 2 Save File Location: Backup & Fix Guide

Where are Neon Abyss 2 save files stored on PC? How to find your save folder, back it up safely, and handle the stuck-floor bug that corrupts saves.

Looking for your Neon Abyss 2 save file location on PC? Neither the developers nor the community have published an exact save folder path in the material we reviewed, so the reliable method is to search Windows for the save data: check the game's installation folder first, then search %APPDATA% for the game's folder name. Details for both methods are below, marked where verification is still pending.

This guide covers three things: how to locate and back up your saves on Windows, the "stuck in the same floor" bug reported after the 1.0 launch that can corrupt saves, and what version 1.0 changed about save backups and recovery. Nothing here invents registry paths or folder names — if a detail is unverified, it is labeled "To be confirmed."

Neon Abyss 2 save file location and backup guide

Finding Your Save Files on Windows (No Confirmed Path Yet)

Here is the honest starting point: we could not verify an exact Neon Abyss 2 save file path from official documentation or community threads, so we will not print a fabricated one. What we can do is walk you through the two standard places roguelite save data lives on Windows, both of which you can check in under a minute.

Method 1: the game's installation folder. In Steam, right-click Neon Abyss 2 in your library, choose Manage → Browse local files. Look for a folder with a name like "Saves", "SaveData", or "SaveGames" inside. The exact subfolder name for Neon Abyss 2 is To be confirmed.

Method 2: the %APPDATA% search. Press Win+R, type %APPDATA% and hit Enter. In the window that opens, look for a folder named after the game, the studio, or the game's internal project name. You can also type %APPDATA% into File Explorer's address bar. If nothing matches there, repeat the search in %LOCALAPPDATA%. Which of these locations Neon Abyss 2 actually uses is To be confirmed — do not assume; check both.

Method 3: Windows search. If the folder names are not obvious, open File Explorer, search your user profile for terms like "NeonAbyss" or "Neon Abyss", and filter by modification date around the last time you played — the save data will have been written then. Whichever folder you find, note that these instructions are Windows-specific; console saves (PS5, Xbox, Switch) are managed by the platform and are not user-accessible files.

Once you locate the folder, back it up by simply copying it somewhere safe — a second drive or cloud storage. Do this while the game is closed.

The Stuck-Floor Bug That Corrupts Saves

There is an urgent reason to back up right now if you play on PC. Shortly after the 1.0 launch, a Steam thread titled "[BUG] Being stuck in same floor after finishing it" reported that "there is a bug were ppl get stuck on the same floor and it corrupts saves," linking to multiple Reddit threads — one describing being stuck facing the same boss over and over, another stuck on floor 1. In other words, the bug traps you repeating a floor you have already cleared, and repeated exposure can corrupt the save itself.

The developers' 1.0 patch notes show they are aware of the underlying failure modes and have been fixing them. Among the listed fixes: direction lock residue after first room entry, resuming a save, or failed door transitions; getting stuck in the air when flying into the next floor; multiplayer progress leaking into personal saves; single-player runs being wrongly wiped when returning to the main menu; and the inability to continue a run after a disconnect converted it to single-player. The patch notes also mention historical save reading compatibility and dynamic level recovery checks — the machinery behind exactly this class of bug.

If you are currently stuck on a floor: first update the game to the latest version, since several stuck-floor causes were patched in 1.0's bug fix list. If the stuck state persists on the current version, do not keep force-closing and restarting the same corrupted run — that is precisely the repetition pattern the community linked to save corruption. Report it on the Steam thread with your platform and what floor you are stuck on.

What 1.0 Changed About Backups and Recovery

Version 1.0 shipped meaningful protection for exactly this scenario. The official patch notes state that Steam backup and recovery now handles both the main save and its corresponding progress data, and — critically — that when a corrupted save is detected, the game "preserves the scene first" rather than letting mismatched content keep overwriting your data. That last part is the difference between a bad save you can recover from and a run silently wiped.

That said, in-game safeguards are not a substitute for your own backup, and there are two gaps worth knowing about. First, whether Neon Abyss 2 uses Steam Cloud save synchronization — and how it interacts with the backup system — is To be confirmed; check the game's Steam Cloud status in its Properties → General tab before relying on it. Second, the backup system protects you going forward, but it cannot restore a save you already corrupted during Early Access.

Practical backup routine for a roguelite like this: copy the save folder (once you have located it) before every patch or hotfix, before trying bug workarounds, and any time the stuck-floor bug first appears. Saves are tiny; there is no cost to being paranoid.

Save problems in Neon Abyss 2 have not been limited to corruption. During Early Access, a widely reported issue involved character-unlock achievements (James, Lucia, R7, Xuan) and other achievements failing to unlock on both existing and brand-new saves. The developers acknowledged it and stated that current achievement issues would be automatically fixed after version 1.0 went live on October 8, with completed conditions unlocking retroactively. If your save shows characters unlocked but achievements missing, update first before assuming the save is at fault.

The 1.0 notes also fixed the flip side of save trouble: multiplayer progress bleeding into personal saves, and single-player returns to the main menu being misread as a reason to wipe the run. Both are exactly the kinds of bugs that make players believe their save "randomly died," so if you lost progress before October 8, there is a decent chance one of those was the culprit rather than simple corruption.

If your issue is performance rather than data — cursor stuttering, 60 FPS caps, or hitches — our other troubleshooting guides cover those known problems separately.