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.

1. 1

   Friday night: start the run on a tablet

   Sign in, open Fridge Simulator, and save the opening stock into slot 1. Say the run reads day 4, two fridges in Osaka, a budget of 620 coins, and a backpack of rice, eggs, and spinach. Press Save, then confirm the slot timestamp updated.
2. 2

   Saturday: continue on a laptop

   Sign in with the same account on the laptop, open the same game, and load slot 1 manual. The day counter, both fridges, the pantry inventory, and the budget match the tablet exactly. Play through day 5, restock milk and tofu, then press Save again before closing the lid.
3. 3

   Sunday: recover a mistake on a phone

   On the phone, load slot 1 manual and accidentally sell the wrong fridge. Do not panic. Use Load-autosave to restore the same slot's auto companion from about a minute earlier, then replay the sale correctly and press Save.
4. 4

   Monday: verify the chain

   Load slot 1 on any device and check four things: day counter advanced, budgets consistent, inventory quantities plausible, and no cheat mark on a slot you never cheated in. If one value looks stale, you loaded the wrong slot number or the wrong game slug.

• Guest progress vanishes: signed out play never writes to the cloud. If the slot list looks empty on a second device, confirm both devices show the same username in the account menu.
• Wrong slot number: slot 0, 1, 2, and 3 are independent runs. A day 2 kitchen in slot 0 and a day 9 market in slot 2 can coexist. Compare timestamps before assuming data loss.
• Manual versus auto: Load reads the manual copy, Load-autosave reads the companion. After a crash, try the companion first, then resume manual saves so the two copies stay close together.
• Payload ceiling: saves larger than 1 MiB are rejected. Trim stored screenshots, prune ancient pantry logs, and consolidate half empty fridges, then save again.
• Cheat mark surprise: a branded slot 1, 2, or 3 keeps its flag through overwrites and cannot be cleared by delete and recreate. Move serious runs to slot 0 and reserve one slot for modded experiments.

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