Where Sephiria Saves Its Files

%USERPROFILE%\Saved Games\Sephiria\

TEAM HORAY gives this path twice in their own pinned technical support FAQ — once under 'When Game Doesn't Run Smoothly on First Launch' (written there as \%USERPROFILE%\Saved Games\Sephiria\, with a stray leading backslash) and again under 'When Progress Disappears'. This is the Windows 'Saved Games' shell folder (C:\Users\<you>\Saved Games), NOT a subfolder of Documents. The Korean-language original of the same FAQ carries the identical string, so the English is not a translation artifact. Paste it into Win+R or the Explorer address bar.

• Sephiria Technical Support FAQ — pinned, posted by MegurinE with Steam's [developer] tag (TEAM HORAY)“Save file location \%USERPROFILE%\Saved Games\Sephiria\”
• Sephiria 기술 지원 FAQ — Korean original of the same pinned developer post“세이브 파일 위치 \%USERPROFILE%\Saved Games\Sephiria\”

[USERPROFILE]/Saved Games/Sephiria — reached in Finder via Go. On macOS that resolves to your home folder, i.e. ~/Saved Games/Sephiria.

Quoted exactly as TEAM HORAY wrote it. They reused the Windows-style token [USERPROFILE] in the Mac instruction; the expansion to ~/Saved Games/Sephiria is our reading of it, not a string the developer published. Note this is unusual for a Mac app — it is NOT ~/Library/Application Support. Do not confuse it with the macOS LOG path, which the same FAQ puts at Library/Logs/TEAMHORAY/Sephiria. The Korean original uses the same [USERPROFILE] token, so it is deliberate wording, not an English-only slip.

• Sephiria Technical Support FAQ — pinned developer post, 'When Progress Disappears' section“Mac OS Finder → Go to [USERPROFILE]/Saved Games/Sephiria folder”
• Sephiria 기술 지원 FAQ — Korean original“Mac OS Finder → [USERPROFILE]/Saved Games/Sephiria 폴더로 이동”

No. That is the log folder. Saves are in Saved Games.

TEAM HORAY prints the LocalLow path at the bottom of nearly every patch note, which is why it gets copied around as if it were the save path. In the FAQ they label it explicitly: it holds Player.log (current session) and Player-prev.log (previous session), and only two sessions are kept. Attach these when you email team.horay.game@gmail.com — do not go looking for .sav files there.

• Sephiria Technical Support FAQ — pinned developer post, 'For Other Issues'“Log file location Windows: C:/Users/{Your_PC_Name}/AppData/LocalLow/TEAMHORAY/Sephiria macOS: Launch Finder -> Click the Options button then click Go -> Library Library/Logs/TEAMHORAY/Sephiria”
• 1.0.30 Update (20 Aug 2026) — same log path repeated in the patch footer“Log file path C: / Users / {Your_PC_Name} / AppData / LocalLow / TEAMHORAY / Sephiria”

Three — Slot1, Slot2, Slot3. The developer spells the filename SLOT1.sav.

TEAM HORAY names exactly three slots and writes one filename verbatim: SLOT1.sav. They never spell out SLOT2.sav or SLOT3.sav — those follow the obvious pattern but are not published strings, so do not quote them as the developer's words.

• Sephiria Technical Support FAQ — pinned developer post“find the backup_date.sav file corresponding to the save slot you're using (Slot1, Slot2, Slot3)”

SLOT1backup_20250822_184201.sav — that is SLOT{n}backup_ then a date and a time.

This exact filename is the developer's own worked example. It reads as SLOT + slot number + 'backup_' + YYYYMMDD + '_' + HHMMSS + '.sav', though TEAM HORAY never states the format spec — they just give the one sample. The game therefore writes timestamped backups of its own accord; you do not have to make them.

• Sephiria Technical Support FAQ — pinned developer post“(Example: SLOT1backup_20250822_184201.sav)”

Yes — 1.0.24 fixed backup saves occasionally failing to load when the main save data was corrupted.

From TEAM HORAY's 1.0.24 patch notes (7 August 2026). This matters for the restore procedure: if you are on a build older than 1.0.24 and a restore fails, the restore itself may be the bug. Update first.

• 1.0.24 Update (7 Aug 2026)“Fixed a bug where backup saves could occasionally fail to load properly when save data was corrupted”

Open the save folder, sort by modified date, find the backup file for your slot, and rename it to SLOT1.sav.

The developer's full procedure, verbatim and in order: go to the save folder (Windows path or Mac path above); sort by modified date; find the backup_date.sav file matching the slot you use; rename it to SLOT1.sav. TEAM HORAY does not tell you to move the broken file aside first — that is a sensible extra step, but it is ours, not theirs, so present it as advice rather than instruction. Quit the game before touching any of these files.

• Sephiria Technical Support FAQ — pinned developer post, 'When Progress Disappears'“Sort by modified date, then find the backup_date.sav file corresponding to the save slot you're using (Slot1, Slot2, Slot3). (Example: SLOT1backup_20250822_184201.sav) Change the file name to SLOT1.sav.”

Quit the game fully, then copy the whole Saved Games\Sephiria folder somewhere dated.

TEAM HORAY's restore instructions assume the game is closed but never say so. They did say so once, in a different context, and it is the same advice: before opting into the Unity 6 public beta they told players to back the save folder up first. Given that Sephiria syncs its own cloud copy and asks you to choose between local and cloud at launch, a hand-made dated copy outside the folder is the only version nothing can overwrite.

• 0.901.0 Beta Update (30 Apr 2026) — TEAM HORAY telling players to back saves up“As a precaution, please back up your existing save data before participating in the beta.”

Folder permissions — and TEAM HORAY names OneDrive sync as the usual cause.

The developer's stated fix: right-click the Sephiria folder, Properties, Security tab, and check your user account has full or modify permission. This is the officially documented explanation for the game running badly on a first launch, and for the symptom where slots come up empty every time you relaunch.

• Sephiria Technical Support FAQ — pinned developer post, 'When Game Doesn't Run Smoothly on First Launch'“This may be a problem caused by the inability to create save files. For Windows, check if the game save folder security permissions are set correctly. OneDrive synchronization may prevent proper permission settings.”

At the start of the floor you were on. The run is not lost.

Three independent reports agree, across two years of builds: a player who quit to desktop came back 'at the first room of the current dungeon'; another summarised it as being 'reset to the start of the floor'; an Early Access answer said the same in April 2025. A crash produces the same result — a player stuck by a mid-floor crash returned to the start of that floor with the run intact. So the game is writing at floor boundaries, not continuously: anything you cleared on the current floor is redone, and the floor's rooms can be re-entered. TEAM HORAY has never documented when the game writes, so the trigger is inferred from where you land, not stated.

• Steam discussion: "Resume session?" — Squeezit, after quitting to desktop“Though it looks like you restart at the first room of the current dungeon which is a little inconvenient, but oh well.”
• Steam discussion: "No mid-run saves? (Demo)" — sawyergrubert“yeah in the main game you just get reset to the start of the floor”
• Steam discussion: "Mid Run Save a thing?" — Unxiah (Early Access, Apr 2025)“If you quit a game, it'll return at the start of the latest area.”
• Steam discussion: "A Bug for Sapphire duping" — Bone_Reaper, on a mid-floor crash“When i came back i was at the start of the floor, happy to know my run didn't actually end because of a crash”

Yes — Steam Cloud is listed on the store page for appid 2436940.

Read straight from Steam's own store data for the app, alongside Single-player, Online Co-op, Steam Achievements, Full controller support and Family Sharing. That is all the store listing tells you — it says the feature exists, not which machines it will move a save between.

• Steam store data for appid 2436940 (appdetails API)“{"id": 23, "description": "Steam Cloud"}”
• Sephiria on Steam — store listing

Through the game's own code, not through Steam Auto-Cloud file rules.

Valve's app configuration for 2436940 carries a cloud quota (1 GB, 100 files) but no Auto-Cloud path rules — the block Steam uses when it is told to sync a named folder on your behalf. That means Sephiria uploads and downloads its own save files from inside the game. It explains the behaviour players describe: the game itself puts a local-versus-cloud choice on screen at startup, which an Auto-Cloud title would never do. Sourced from a public mirror of Steam's app metadata, which is Valve data rather than a TEAM HORAY statement — hence community, not official.

• Steam app metadata for 2436940, via the public SteamCMD API mirror“"ufs": {"maxnumfiles": "100", "quota": "1000000000"}”

It resolves save conflicts itself instead of letting Steam do it — and the menu defaults to local.

A player who moves between a Steam Deck and a PC describes the prompt appearing after the cloud save has already downloaded, with local pre-selected. Because it can appear during the company logo, a stray button press picks local and discards the newer cloud copy with no confirmation. Their stated recovery: go back to the other machine, pick that machine's local save, let it re-upload. One first-hand report, no developer statement — treat as a warning to press nothing until the prompt is on screen, not as documented behaviour.

• Steam discussion: "Cloud Saves" by BrickScrap“the Deck loads the cloud save (expected), but the game then for some reason asks if I want to use local or cloud. Obviously you'd always want to use the most recent, but the game menu defaults to local.”

Reported working — a player found their save already present on a laptop's first ever launch.

Two independent reports point the same way: one player found existing save data waiting on a laptop the first time they installed and launched there, and another had a run counter go backwards because an older cloud copy came down. Both are Windows-to-Windows. A Steam Deck counts as Windows here — Steam lists Sephiria's Deck runtime as Proton, so the Deck is running the Windows build.

• Steam discussion: "Save data and settings are not being saved after closing the game" by Radock“I also tried installing and launching the game for the first time on my laptop, and there my previous save data was already available, even though it was the first time I had installed and launched the game on that computer.”
• Steam discussion: "Losing save progress during full game" by funkyboer“Sounds like your game downloads your old save file from the steam cloud for whatever reason which is why your runs go back from 11 to 8.”

Nobody has established this, and we are not going to guess it.

We could not establish this and we are not going to guess it. Steam listing Steam Cloud for an app is not a promise that a save crosses operating systems — Valve controls that per app, and the setting is not public. Sephiria does its cloud work in its own code rather than through Steam's folder rules, so the outcome depends entirely on choices TEAM HORAY made that they have not published. What is suggestive but not proof: the developer's Windows and macOS save paths sit at the same place relative to your home folder (Saved Games/Sephiria), which would make a shared cloud container coherent. Back up the folder by hand before switching machines.

• Steam app metadata for 2436940 — cloud quota present, no Auto-Cloud path rules

1,000,000,000 bytes across at most 100 files.

Valve's per-app cloud allowance for 2436940. Generous next to three .sav slots plus timestamped backups, so a full cloud quota is not a plausible cause of a lost save. Valve data via a public mirror, not a TEAM HORAY statement.

• Steam app metadata for 2436940, via the public SteamCMD API mirror“"maxnumfiles": "100", "quota": "1000000000"”

No. The run ends and you are returned to town.

TEAM HORAY states this in the 1.0 launch announcement itself. Read the sentence closely, because it is narrower than it looks: it is about mid-run save data — the expedition you were part-way through — and says nothing about your town progression, unlocks or settings.

• 1.0 Update — the launch announcement (31 Jul 2026)“Mid-run save data from the Early Access version cannot be continued in the official version; the run will end and you will return to town.”

Reported yes — the save file itself carries; only the in-progress run is dropped.

TEAM HORAY never said progression carries — they only said what does not. Players filled the gap by reading the same announcement the same way, and by playing: one finished the game to 100% on a carried-over file with no softlocks. Also official: Early Access owners were told the game would update itself into 1.0 at launch, and everyone who bought before release got a multiplayer badge — neither of which implies a wipe. So the honest shape of the answer is: the developer ruled out the run, said nothing about the rest, and nobody has reported the rest being lost.

• Steam discussion: "kept demo save into main game" — Bone_Reaper reading the 1.0 notes“the change logs for 1.0 only mentioned in progress Runs would not transfer, but save files would”
• We have a full release date for Sephiria! (8 Jul 2026)“If you've been an Early Access player, the game will automatically update into 1.0 for you at launch.”

Yes — multiple players loaded a demo save in the full game and played it to the end.

Three separate players report it working, one of them all the way to a 100% finish with no softlock. The mechanism they describe is that the demo and the full game write to the same place, which is consistent with the folder being named after the game rather than the appid. There is corroborating evidence in Steam's own app data: the demo's cloud storage is redirected to the full game's appid 2436940, so Valve is deliberately pointing both products at one cloud container. TEAM HORAY has never published a statement about demo carry-over, so nothing here is official.

• Steam discussion: "Demo to Full" by Subtumaka“they use the same place for save files … but all progress should always transfer seamlessly.”
• Steam discussion: "kept demo save into main game" — kwsn“I did the same thing, started with a demo and transferred the save. Just beat the game 100% with no softlocks or any problems associated with the save, so you should be good.”
• Steam app metadata for the Sephiria Demo (2686970), via the public SteamCMD API mirror“"ufs": {"appidredirect": "2436940", "maxnumfiles": "100", "quota": "1000000000"}”

No re-run reported. The one player who hit greyed-out achievements fixed it by reinstalling the game.

A single first-hand report: achievements appeared greyed out after playing a demo save through Chapter 1 in the full game, and resolved after an uninstall and reinstall — no replaying required. That is one person, and the explanation offered alongside it was explicitly a guess. Worth pairing with something better sourced: TEAM HORAY documents a completely different cause for achievements not recording, namely the game failing to connect to the Steam client at launch, which also shows up as multiplayer room names reading ERR. Check that first, because it has a developer-written fix and the demo-save theory does not.

• Steam discussion: "When using a demo save in the full version you cannot get achievements" by Tbott“Can close. Seems to have resolved itself after uninstalling and reinstalling the game.”
• Sephiria Technical Support FAQ — pinned developer post, 'When Multiplayer Does Not Work'“Achievements not being recorded on Steam may appear together with this symptom. The game failed to connect to the Steam client at launch, so it cannot read your Steam account information.”

No. There is no chapter select — old chapters are unreachable except on a new save file.

The clearest statement comes from a player answering exactly this question on the Steam forum in August 2026, and nobody in the thread's thirteen replies disputed it — the thread moves straight on to Hard Mode as the alternative. TEAM HORAY has never announced a chapter select, and no such feature appears anywhere in the thirty Steam announcements from Early Access through 1.0.30, including the launch notes that describe the finished game. That is absence of evidence rather than a denial, so the label stays community. Two consequences worth stating plainly: starting a fresh save is the only route back to Chapter 1, and Steam's achievement list is chapter-gated — CHAPTER_1_COMPLETE through CHAPTER_5_COMPLETE and ENDING are separate achievements — so anything missed on a chapter is gone for that file. The intended post-ending loop is Hard Mode levels, not revisiting chapters.

• Steam discussion: "Once we complete the game" — scayman223 answering AwkwardMoose64“Previous chapters cannot be accessed in singleplayer or host outside of a new save file. I doubt it's their intention to allow players to cheese the hardmode rewards by cutting off large portions of a run.”
• Steam global achievement percentages for appid 2436940 — chapter-gated achievement IDs

Hard Mode. TEAM HORAY raised its ceiling to level 60 at 1.0.

The 1.0 notes say only that Hard Mode now extends up to level 60 and that six new Hard Mode elements were added. What the rewards are at each tier is not in that announcement, and this page does not extend it into one.

• 1.0 Update“Hard Mode now extends up to level 60”