Start on mobile. Finish on desktop.

1. 1

   Sign in on device A and play into a slot

   Play Fridge Simulator signed in and save into any slot 0-3. The slot payload carries your fridges, inventory, budgets, and day — up to 1 MiB of plain game state.
2. 2

   Sign in with the SAME account on device B

   Guests have no saves: three free loads a day and nothing persists. The account is the bridge — same login, same slots.
3. 3

   Load the same game + slot

   Open the same game (fridgesimulator) and the same slot number. The server returns the most recently written save for that account, game, and slot.
4. 4

   Keep playing — the slot stays yours

   Every later write upserts the same slot, so bouncing phone → desktop → phone just works. There is no merge: latest write wins, per slot.

• Keep your real run on slot 0: any cheat marker the client sends is stripped on write, and the database enforces the same invariant — slot 0 stays clean no matter what.
• Experiment on a throwaway slot: cheats brand slots 1-3 permanently. The mark survives overwrites, so never test cheats in the slot holding a run you care about.
• You cannot delete your way out: save deletes are refused, so a branded slot cannot be laundered by recreating it. Pick the slot before you play.

• Active-slot rule: the autosave companion belongs to the slot you are playing, so bouncing phone → desktop → phone keeps both copies per slot.
• Kind + device key: cloud ?kind=manual|auto (omitted = both), PUT defaults to manual; the device auto mirror uses the -auto suffix.
• Corrupt-manual recovery: if a manual copy fails to load, Load-autosave restores the same slot's auto companion — same day counter, same fridges, one minute older at most.

Back to the Fridge Simulator guide · plan meals with the foods table · slot mechanics in full in Playing games.