Probably Stolen Save Editor and Save File Location

Saves are the one part of a shop sim you cannot rewind. A bad purchase is a lesson; a corrupted save is a lost run. This page covers the folder, the backup routine and the realistic options if you want to edit.

The save folder

The default Windows path is:

C:\Users\<name>\AppData\LocalLow\Questing Goose Studio\Probably Stolen

<name> is your Windows user name. The AppData folder is hidden by default; paste the path into File Explorer's address bar or enable hidden items.

Inside the folder you will usually find:

• One or more save slots.
• A settings file.
• Logs or cache files created by the game.

The exact file names depend on the build. Do not rename files unless you are restoring a backup with the same name.

Mac and wrapper paths

On a Mac wrapper, the same Windows path exists inside the bottle:

C:\Users\<name>\AppData\LocalLow\Questing Goose Studio\Probably Stolen

Use CrossOver's Open C: Drive or Whisky's bottle directory to reach it. The Mac install guide covers the wrapper setup.

Steam Cloud

Steam Cloud may sync the save. Before you edit or restore:

1. Open Steam.
2. Right-click Probably Stolen → Properties → General.
3. Temporarily disable Steam Cloud for the game.
4. Edit or restore the save.
5. Re-enable Cloud only after you have verified the run.

If you skip this step, Steam may overwrite your restored save with the cloud version.

The backup routine

Do this before every major decision, not just before editing:

1. Close the game. A save written during a backup can be half-finished.
2. Copy the whole Probably Stolen folder to a dated folder, for example Probably Stolen backup 2026-11-02.
3. Zip it. A zip is harder to overwrite by accident.
4. Keep two copies. One on the same drive, one on another drive or cloud storage.
5. Label the run. "Day 12, water, 8k credits" is more useful than "backup2".

A backup is only a backup if you have restored it once. Test the restore on a throwaway save before you need it.

Restoring a save

1. Disable Steam Cloud.
2. Close the game.
3. Rename the current save folder to Probably Stolen broken.
4. Copy the backup folder into the original location.
5. Launch the game and load the save.
6. If it works, re-enable Cloud.

Do not delete the broken folder until the restore is confirmed. It may contain a recoverable file.

Is there a save editor?

No official editor. The developer has not shipped one. Community save editors are third-party tools, and their compatibility depends on the save format of the current build.

Before you use one:

• Check the version. A 1.0.0.6 save may not load in an editor built for 1.0.0.5.
• Check the source. A random executable from a video description is a security risk.
• Run it offline. Disable Cloud and disconnect if you do not trust the tool.
• Back up first. Twice.
• Test on a copy. Never edit your only save.

The safer route is a cheat mod from the Workshop, not a save editor. Mods run inside the game's mod system and can be removed; a save editor writes files directly.

What a save editor can change

A typical editor can change:

• Credits.
• Day.
• Reputation values.
• Inventory items.
• Perks.
• Machine states.

A typical editor cannot reliably change:

• Quest flags.
• Ending triggers.
• NPC schedules.
• Mod-added items.
• Anything the editor's version does not know about.

Changing credits is easy. Changing a quest flag can break the ending chain. If you only want money, use a cheat mod or edit the smallest possible value.

Version and mod risks

• Game updates can change the save schema. An old editor may write fields the new build does not expect.
• Content mods add item IDs. A save with Brewing Expansion items may not load without the mod.
• Removing a mod can orphan items and crash the save.
• 1.0.0.6 changed the modding system; save-editing tools that rely on mod DLLs may need an update.

The modding basics guide explains why mod-added content is version-sensitive. The Brewing Expansion guide is the most common cause of modded saves.

A safer alternative: duplicate the run

If you want to experiment without risking the main save:

1. Back up the save.
2. Start a new run with the same start and perks.
3. Experiment there.
4. Keep the main run clean.

This is slower than editing, but it preserves the achievement flags and the ending chain. Achievements are tied to the save; an edited save may not count.

Achievements and edited saves

The game does not advertise an anti-cheat, but achievements may not unlock correctly if a save is edited in a way the game did not expect. If you care about From Nothing, the Hard Way or Clean Hands, do not edit that save.

Use a separate save for sandbox edits. The achievements guide lists the runs that need a clean save.

A toolbox mod interface. Save editing carries the same risk: a backup is mandatory.

FAQ

Where is the save file?

%USERPROFILE%\AppData\LocalLow\Questing Goose Studio\Probably Stolen.

Is there an official save editor?

No. Community tools edit the JSON save at your own risk.

Can I back up my save?

Yes. Copy the folder and disable Steam Cloud before editing.

Sources and version notes

• Save path from the game's LocalLow folder and community reports, checked 2 November 2026.
• No official save editor is listed on the Steam store or in the game's menus.
• Community editor compatibility is version-dependent; no specific tool is endorsed here.
• Build 1.0.0.6.

Official source: Steam store ↗ · Steam guides ↗ · Workshop ↗, checked 2 November 2026.