Manual-save field test · September 29, 2026

Best incremental games to save before closing: does Candy Box 2 return?

Yes—in our short test in the same Chrome profile, a manually saved Candy Box 2 run returned with 41 candies when we reopened its Slot 1 link. Opening the plain game address instead began at zero. This shows a saved return under these conditions, not candy earned while the tab was closed.

Saved slot: Save on Slot 1, close the tab, then reopen ?slot=1 in the same browser. The display returned at 41 candies.

Plain address: opening the base game URL in a separate tab displayed zero candies at first, despite the saved slot existing.

Conceptual illustration of an empty candy jar beside one laptop and a saved candy box beside another — Original conceptual illustration of the two return paths; not game footage.

Method: on September 29, 2026, we used the linked browser game in one Chrome profile. We unlocked its save control, saved a small run to the first local slot, closed that tab, and opened both the slot-specific and plain addresses shortly afterward. We did not clear browser data, change devices, or leave the game closed for a long interval.

How we reached the save control

The page identified itself as version 1.2.3 and initially displayed zero candies. The counter increased while the page stayed open. At 31 candies, a request for a new feature cost 30 candies and revealed the status bar. Further five-candy feature requests revealed configuration and then the Save tab. The save control was therefore something we unlocked during play, not a button visible on the fresh opening screen.

The Save tab offered five browser slots. It showed both a one-time save for Slot 1 and an option to save to that slot every ten minutes. It separately offered a text save for moving to another browser or device, or for keeping a copy before browser data is cleared. We used the one-time browser-slot button; we did not test the recurring-save or text-save paths.

Conceptual illustration of placing a blank save card into the first compartment of a storage tray — Original illustration of the manual-save step; it does not reproduce the game's interface.

What happened when we returned

After we selected “Save on slot 1,” the game's slot label recorded 41 candies. We closed the game tab. Opening the slot-specific address in the same Chrome profile then displayed 41 candies and retained access to the Save tab. A separate opening of the ordinary game address displayed zero candies before its counter started moving again.

That result resolves the narrow question left open by our earlier unsaved closed-tab test: in this browser, a deliberate Slot 1 save did bring the run back. It also explains why merely returning to the homepage is not a reliable check of that saved slot. We did not measure candy production while closed, so the difference between 41 and zero must not be called offline earnings.

What should you do before closing?

If you want to resume this browser run, unlock Save, save to a slot, and keep the slot-specific return link. If you plan to switch browsers or devices, the game offers a separate text-save route, but we have not tested its import process. Do not assume either route survives deleted browser data without a backup.

This is one short browser test of one game version, not a promise about every incremental game or every storage setting. The useful distinction is simple: a running counter, a local save, a portable backup, and offline production are four different things.