Text-save field test · September 30, 2026

Best incremental games with portable saves: can Candy Box 2 move a run?

Yes, under the conditions we tested. A Candy Box 2 text save exported from Chrome while the game displayed 78 candies loaded in a separate browser environment and displayed 78 candies there. The destination had opened as a new run with empty local slots. This is a same-computer transfer test, not a promise about every device or browser version.

Before text loadThe separate environment began at zero candies. Its local save slots were empty; its counter had reached 27 while we prepared the import.

After text loadWe pasted the exported text into the game's Text load field and selected Load. The displayed count became 78 candies.

Question: Can the text state move?
Route: Chrome to a separate browser environment
Limit: One game version, one short test

Original screenprint of a paper ribbon carrying abstract marks between two separate worktables — Conceptual illustration of moving a text save; not gameplay footage or a game interface.

Method: on September 30, 2026, we used version 1.2.3 of the linked game on the same Windows computer. We copied a generated text save from one Chrome profile and loaded it in a separate in-app browser environment with its own initially empty save slots. We did not test a physical second device, another game version, deleted source data, or long-term storage.

What we exported

We reopened the Chrome run through its saved Slot 1 link. That earlier local save initially showed 41 candies; the counter kept moving while the tab was open. In the Save tab, we selected Get the current game as text when the display read 78 candies. The resulting text field contained 8,241 characters, including a field recording the current candy count as 78. We copied that text rather than sending the Slot 1 link to the destination.

The game's Save page describes its browser slots as local to the current browser and its text route as the option for continuing elsewhere. We treated that explanation as a reason to test, not as proof that this specific transfer would work. The earlier Slot 1 return test had only checked the same Chrome profile.

What happened in the separate environment

The ordinary game address opened with zero candies in the separate browser environment. After unlocking the Save tab, its five browser slots displayed as empty. While those controls were being opened, its own counter rose to 27 candies. No Chrome Slot 1 state appeared there automatically.

We pasted the 8,241-character export into the Text load field and selected Load. The status then displayed 78 candies—the count captured in Chrome's export—not the destination's pre-load count of 27. In this run, the text save replaced the fresh destination state with the exported one.

Original screenprint still life of matching candy jars connected by a folded paper ribbon beside a separate empty jar — Conceptual comparison of exported, restored and fresh states; not a screenshot or a claim about game graphics.

What the result does and does not prove

For this version and these two browser environments on one computer, Candy Box 2's text export and Text load controls moved the observed state. A local Slot 1 link alone was not our transfer method. The useful distinction is between a browser-specific slot and a portable block of save text that the game can load.

Players also discuss losing locally stored progress when browser data is cleared, and one community discussion specifically raises text-copy backups. Another player thread describes trouble pasting exports on a Chromebook. Those reports are reasons not to assume universal success; they are not results of our Candy Box 2 test. We did not clear browser data or test that Chromebook problem. If the save matters, retain the full exported text and verify it loads before relying on it as a backup.