Where Deskrawl stores saves, how cloud save and hourly backups work, and a step-by-step stop-loss checklist for when your gear vanishes mid-session.
Deskrawl Save File and Lost Items: What to Do When Your Gear Vanishes
There is no restore button anywhere in Deskrawl. Ask in the forums and the answer you get is "start over". What the game actually ships with is quieter than that: your whole run lives in one plain-text save file, and the game quietly keeps the 5 most recent copies, one written every 3600 seconds. Those five hourly copies are the only version of your progress that still exists after a bad write. So this page runs in two halves — what to do in the first five minutes after something goes wrong, then how to make sure you never have to use the word "start over" at all.
It covers where your save lives on your own platform, whether cloud save is real (it is — patch 0.1.9, June 16, 2026), whether deleted chests can be brought back, what the 409 in those threads actually means, and the exact order to run when your inventory comes back empty. The disappearance itself is labelled throughout as an unconfirmed player report, because that is what it is.
Four things drive every loss report in this game:
- Your save is rewritten, not appended to. Level, gear, stash and character list all land in one file that gets overwritten. A write that gets cut off halfway is the whole reason things can disappear.
- Backups run on a timer, not on milestones. One every 3600 seconds, 5 copies kept. Nothing you do in game triggers an extra copy, so a bad hour costs you a whole hour.
- Local and online characters save down different roads. 4 slots per mode, and since the September 28 launch-day hot fix new characters start on Online Mode, which goes through the servers and can fail for reasons that have nothing to do with your PC.
- No restore feature exists. The words "restore" and "rollback" appear 0 times across all 26 official announcements from May 18 to September 29, 2026.
The first five minutes

- Stop entering maps. A second failure while the first is unrecovered doubles what you stand to lose.
- Quit the game properly — from its own menu, not by killing the process. The game finishes writing your save when you quit or when you switch away; force-close the window and that step never runs, which is the single cheapest way to turn a glitch into a wipe.
- Copy your whole save folder out before you launch anything again. Before, not after. It is a folder inside the game's install directory — confirm the exact path on your own platform, because the developer has never published one. At minimum, copy every hourly backup copy: they all share your save file's name with the word
backupin front of it. - Write down the moment: clock time, which zone you were in, what was lying on the ground, and whether you were on a local or an online character. That last detail decides which of the two failure paths you were on.
- Transcribe the error text exactly as it appears. A player in the lost-items thread read his own screenshot out loud as
error : invalid_save ; ??? : save references item instances the server did not issue, duplicates one, or contains local-origin equipment (no server instanceid). That string is worth more in a bug report than any paraphrase of it.
Every loss report so far, and what it points at
Six reports, all from the June–August 2026 demo and beta period. The quotes are the players' own words from the linked threads; the second column is our reading of which stage each symptom points at, and that column is inference, not fact.
| What you see | Stage it points at | Stop-loss action | Field report |
|---|---|---|---|
| Kicked to the main menu while in town, chest contents gone on re-entry | The save write got interrupted by a connection loss during a town save | Do not re-enter a map. Quit, copy the folder, then come back | Items poofing...need a FIX: at town everything goes onto the ground, I check the legendaries in my inventory, the game crash, I reconnected, I lost everything on the ground + the items I had in inventory |
| A 409 while sorting chests in town, thrown straight to the main menu | Your save upload was rejected, then an older state got reloaded on top | Stop playing immediately. Copy the folder before launching anything | A Chinese-language thread titled roughly "the servers are pretty bad", translated: a 409 wiped out a level 25 weapon and ancient legs; standing in town sorting chests, the 409 went straight to the main menu, and going back in a big pile of stuff was gone — 100+ runs left only 5 or 6 chests |
| You come back from a long AFK session and half your equipment is missing | A rollback to an earlier state that had been committed | Check the backup window before you play another minute | Bug Report — Equipped Items Vanishing: I load my save fully equipped, go to grind, and when I come back to my PC half my equipment is just gone |
| A whole inventory of unopened golden chests deleted, and it keeps happening | Whole blocks of chest contents being dropped when the save reloads | Copy the folder, then stop opening chests in bulk | Nevermind I take back that I said the game is awesome: a full inventory of golden chests just got deleted AGAIN... this is like the 6th inventory of golden chests that has been deleted. I didn't even open any |
| Save gone entirely after a hard PC crash and reboot | A save file that never finished being written | Grab the hourly backup copies before anything else touches the folder | A Chinese-language thread asking whether a lost save can be recovered, translated: after the PC froze and rebooted, the save is just gone — can I get it back? |
| Loot on the ground vanishes at the end of a map run | Not a save bug — the round rolls over before your cart reaches it | Walk it forward before the run ends | Loot is lost at the end of a round: the new round begins straight away, the vehicle hasn't moved far enough forward yet, so anything still lying on the ground at that point is lost |
That last row is the one players misdiagnose most. The loudest thread in this cluster — fifteen posts, ending with a player saying he would stop playing — mixes two completely different failures. Ground loot at the end of a run is a designed round rollover and nothing was lost from your save; a chest inventory deleted on a 409 is a real one. Nobody has said which is which in that thread, so assume nothing until you have copied the folder.
The four questions people actually arrive with
| Question | Answer |
|---|---|
| Where is my save file? | A plain-text save file plus two folders, one for the save and one for its hourly copies, sitting inside the game's install directory. The exact layout is community-reported — confirm the path on your own platform rather than trusting a stranger's |
| Is there cloud save? | Yes — patch 0.1.9, June 16, 2026, and the store page still carries the Steam Cloud category. If you have Steam Cloud enabled, that copy runs alongside your local one |
| Can deleted chests be restored? | No. No restore feature has ever been published. The 5-deep hourly rotation is the only copy that exists, which is why step 3 of the stop-loss order is copy the folder, not open a chest |
| Why did my gear vanish? | Unconfirmed. No developer statement addresses 409, invalid_save or item loss. Every case is a player report, and "409" appears in none of the 26 official announcements |
What that means for you: your only recovery tool is a folder copy you make yourself. Nobody can restore anything for you after the fact, so the whole page reduces to one habit — copy the folder before you relaunch, not after.
Before it happens: what the game backs up for you
| What the game does | Number | What it means for you |
|---|---|---|
| Writes an automatic backup on a fixed interval | Every 3600 seconds — one hour | A bad hour can cost you a full hour of progress, and nothing you do in game shortens that window |
| Keeps a rotating set of backup copies | 5 copies | Your worst recoverable window is roughly five to six hours of play — and only if a copy actually landed and you go and get it |
| Stores the save in a folder beside the game's files | One save folder | Your save travels with the install, not with your documents. Confirm the path yourself on your platform |
| Puts the hourly copies in a second, separate folder | One backup folder | The "more secure folder" the developer moved backups into during beta. If your main save folder looks empty, look here |
| Writes your run into a single readable file | One file, plain text, not an encrypted blob | You can copy it, back it up, or open it in a text editor to see what the game thinks you own |
| Names the hourly copies after your save | Every backup file's name starts with your save file's own name plus the word backup |
You can spot them by name in any folder view — no tooling needed |
| Remembers when the last backup ran | A stored timestamp | The game knows how long is left until the next copy; you do not get told |
| Keeps a 5-second timer next to the in-town autosave setting | 5 seconds, and the interval it belongs to is not labelled | The only autosave timing you cannot work out from outside the game. Assume in-town saving happens more often than once an hour, but do not count on a specific number |
| Stores which mode and which slot you last played | Last played mode, last played slot | The game reopens you where you left off — which is also why a bad reload drops you straight back into the state it saved, not the one you wanted |
Read those as a promise the build keeps, not a guarantee. The rotation is automatic, so the dangerous window is not "the game forgot to back up" — it is the five hours between your last good copy and now, plus the part where you launch before copying.
The developer has acknowledged this area twice, both times in beta:
Official source: 0.1.13f — Bug Fixes, July 17, 2026
Fixed crashing during save sometimes cause corrupted save files.Moved backup saves to a more secure folder.
Official source: 0.1.9 — Resizable/Draggable Window, Cloud Save, Buybacks and More, June 16, 2026
Cloud Save
What that means for you: save corruption is a failure mode the developer has already patched once, so it is a real thing and not a story. Cloud save being genuine is the good news — but it copies the same file, so it protects you from losing the file, not from the file being rewritten wrong.
What your save holds, and why a deleted chest is gone forever
Three layers, and the third one is the reason a lost chest never comes back.
| Layer | What it holds | What that means for you |
|---|---|---|
| Your account | The character list on this install — local slots and online slots separately — your shared stash, and which expansions you own | Two characters, one local and one online, do not see each other's gear and do not back each other up. Your stash is shared, so a bad write hits everything at once |
| Your character | Level, XP, health, mana, your unlocked abilities, four separate item lists (inventory, equipped gear, carriage, runes), talents, Paragon, the quests and maps you have finished, and when your last session ended | Everything that makes the run yours sits in one record. Roll that record back and you lose the run's progress too, not just the items — that is why the 409 report above cost a player 100+ runs down to 5 or 6 chests |
| Each individual item | One record per item: a unique id, its level, its rarity, its modifiers, its upgrade level, and its socketed gems | Each item is its own row. Lose the rows and the item is not "somewhere else" — it does not exist anymore |
A golden chest is not stored as one chest. It is stored as a list of what is inside it plus how much gold it holds, so when a player says a chest was deleted they mean entire rows of that list stopped coming back. There is no partial recovery: either those rows returned or they did not.
Two character modes, local and online, with 4 slots per mode. Since the September 28 launch-day hot fix, new characters default to Online Mode, which routes through a different path than a local one. So the same chest can fail on two completely different roads depending on which mode you made it in — one fails because your disk, one fails because someone else's server.
The game records that it moved saves into the install directory, which is why the community answer is a folder next to the game executable, and Windows treats Data and data as the same folder. Treat the exact on-disk layout as community-reported: no developer has ever published an absolute path, and this guide will not invent one. Open the folder yourself on your own platform, confirm it holds your save, and copy it somewhere safe before you ever need it — a 10-second job that has to happen before the bad day, not after it.
The 409 error, line by line
One player transcribed his own screenshot, and what he wrote lines up with the checks the game ships. That matters: it is something you can hand a developer instead of a guess.
| What the game checks | What it means when you see it |
|---|---|
| A refused save comes back with an error string plus three revision numbers — one for your save, one for your economy, one for your stash | All three have to match what the server has on record. If any one of them is out of step, the whole save gets refused rather than partly accepted |
| Every item the server accepts carries a server-issued id beside the item's drop id and its chest contents | The server needs to recognise each item as one it actually handed you |
| The server's reply lists which items it committed, how many, the new economy revision, the new save revision, and whether it rejected the upload | "Committed" is the word for items that survived. Anything not on that list did not make it |
| Your own save stores that same server id on every item row, next to the chest contents | If the id sitting in your file does not match the server's copy, that row is the problem the server tripped over |
| The game ships 13 server-side save-validation messages, including the save contained unauthorized or duplicated items, the save claimed more gold than the server recorded, and character progression exceeded server records | These are the sentences the server can throw at a save. None of them has ever appeared in a lost-item thread — which is exactly why the cheat angle is not the answer here |
The vocabulary in that error — items the server did not issue, duplicates, no server instance id — is the vocabulary the game's own text uses. So it is an observation about two artifacts, not an explanation of what went wrong.
The cause has never been confirmed by First Day Games. No announcement, store page or in-game string explains 409, invalid_save or item loss — those terms appear zero times across all 26 official announcements from May 18 to September 29, 2026, and nobody at the developer replied in any thread cited here. Three causal theories circulate in the thread (blame the early online server, blame the duplicate check firing false positives, blame duplicate loot seeds). None is evidence, and this guide will not pick a winner.
What is officially confirmed about lost progress is narrower and far more useful — it tells you where you can afford to take risks:
Official source: 0.1.13b — Improve stability & various fixes, June 27, 2026
[Online mode] Fixed treasure chests causing various disconnections and lost save. Treasure chests now also can only be open in town.
Official source: 0.1.13e — Stability and Fixes, June 30, 2026
[Online Mode] Added auto save while in town[Online Mode] Reduced redundant saves that increased risk of disconnection[Online Mode] Fixed occasionally revive in town causing save loss.
Chests are town-only by official rule, and town autosaves exist. So the map runs are where you are exposed, and the town is where the game is actively protecting you — that is the closest thing to a cause the developer has published, and it is enough to plan around.
What patch 1.0.0g actually fixed
The first post-launch patch shipped September 29, 2026 and is still the latest release as of this writing.
Official source: Patch 1.0.0g — Various Improvements and Fixes, September 29, 2026
Added Stash All/ Take All button in storage panel.Fixed a few cases where cheat detection handed false bans.Loot drop system now guarantees even chance per equipment slot
| Change | Bearing on lost items | What it does not say |
|---|---|---|
| Stash All / Take All in the storage panel | Bulk movement between stash and slots in one click | Nothing about the deletions themselves |
| False-ban fixes | The save validation is not perfectly tuned | Nothing about rejected saves being wrongly rejected |
| Even chance per equipment slot | Fewer surprise quality spikes in one chest | Nothing about chest rows surviving a reload |
Read the absence carefully: 1.0.0g does not mention save corruption, 409, invalid_save or item loss. Full archive in Deskrawl Patch Notes. Item loss and a cheating flag are separate systems — 1.0.0g fixed several false bans, so false positives are real in this codebase, but no lost-item report in the threads above contains a ban message. Appeals go through deskrawl.com/support, which authenticates via Steam OpenID.
One habit shrinks the blast radius. Loose inventory items are rows in a file rewritten on every save, and the auto-sell, auto-salvage and auto-dump-to-carriage nodes move drops out of your bag while you are not there — so a bad write can take more than what you were holding at that instant. It is not a fix, but it is the cheapest way to reduce what one bad write drags down with it. Unlock order in Deskrawl Life Skills Tree; first-hour sequence in Deskrawl Beginner Guide.
FAQ
Where exactly is the Deskrawl save file? The community answer is a folder next to the game executable, and the game does record that it moved saves into the install directory. No absolute path has ever been published and this guide will not write one for you. Check the community answer against your own install, then copy the whole folder before you need it.
Can I get my deleted chests back? There is no published restore feature; "restore" and "rollback" appear zero times in all 26 official announcements. Your only lever is the rotating backup — one copy every 3600 seconds, 5 copies retained, in the folder next to the game. If the deletions are recent, check those backup copies before launching again.
What is the 409 error in Deskrawl?
A number players report, nothing more. The string appears in no official announcement, no store page text, and no in-game message. The one legible error a player transcribed reads error : invalid_save, with a second line about item instances the server did not issue. Until the developer explains it, "409" labels a symptom, not a diagnosis.
Will starting a new game delete my save? Yes, and the game still ships a confirmation line that reads exactly Starting a new game will erase your existing save. Continue? A June 2026 player reported seeing that prompt when trying to start a second character, back when the game was single-character per account. The current build allows 4 slots per mode so that constraint is gone, but the prompt is still there — click it deliberately. That total wipe is a different failure from the item loss here; covered in Deskrawl Demo vs 1.0.
Is it worth playing if saves are this fragile? A buyer's call, depending on your tolerance for hours of AFK progress riding on one file. The honest inputs are the backup numbers above, the fifteen-post thread where a player decided to stop, and the fact that the game has been out three days. Rest of the picture in Is Deskrawl Worth It; the adjacent connectivity problem in Steam Deck and connectivity.
Where these numbers come from
Every folder name, file name, the 3600-second interval, the 5-copy retention, the 4 slots per mode, the 13 save-validation messages and the layer breakdown above were read from the game's own shipped data files (1.0 launch build, September 28, 2026) and its interface text. Read them as that build; the live build is on 1.0.0g as of 2026-09-30. Steam category data came from the store API on 2026-09-30, and announcement text is quoted verbatim from the Steam news API. Player reports are community reports dating from the June–August 2026 demo and beta period rather than the retail launch. The official save path and the cause of the item loss remain unconfirmed. For anyone checking the numbers themselves: the save and backup names and timings sit on lines 297, 299, 301, 333, 335, 337, 339 and 341 of the game's save code, the last-played mode and slot on 255 and 257, and the 5-second timer next to the in-town autosave setting on 271 and 273.
Related Guides
- Deskrawl Patch Notes: All 26 Official Updates, Full Archive — every version that touched saving, with dates.
- Deskrawl Demo vs 1.0: What Changed and Do You Keep Your Save — the total-wipe case, a different failure from item loss.
- Deskrawl Life Skills Tree: What to Unlock First (85 Nodes) — the automation nodes that empty your inventory.
- Deskrawl Beginner Guide: What to Unlock in Your First Hour — the first-hour order, including character mode.
- Deskrawl Steam Deck: The Player Setup That Actually Works — the other way a connection fails.
More Deskrawl: Idle ARPG Guides
All 20 Deskrawl bosses and minibosses in progression order, each with its official zone, level band, exact map and live unlock rate from 91.8% down to 1.1%.
Deskrawl class builds compared without a tier list: talent counts, weapon pools, socket limits and the exact gold each class should spend first.
Demon Skulls are the only entry currency, and the rule is odd: entry only checks your balance, and the skull is deducted after you clear the stage.
Deskrawl has exactly three difficulties. Inferno multiplies enemy HP sixfold and is the only tier that drops Divine gear, rune sets and Mythic content.
The real Deskrawl loot table from the 1.0 build — 87-95% no-drop rolls on trash mobs, chest contents, and what patch 1.0.0g actually changed.
The verified Deskrawl +10 upgrade table: four guaranteed levels, then 75%, 50%, 40%, 30%, 20% and 10% — plus the material each slot needs.
Locates the final boss, lists entry needs and gives a clear plan to beat him without wasted runs.
All three Deskrawl fishing lakes, all 12 catches in each, the 50 percent empty rate, and the one Rein that only comes out of water.
