On this page

What a save editor changes

A Cookie Clicker save editor decodes an exported save into editable fields, then produces an import string. Cookies, buildings, upgrades and achievements are connected state: changing one value does not guarantee every dependent field remains consistent. This page is a guide, not an embedded editor.

Use a browser editor that explicitly supports your game version and names its maintainer. Do not upload your only backup or assume an editor for the official game understands Cookie Lab’s practice format. Editing a local single-player save is distinct from a mod that runs each time the game loads.

A controlled editing workflow

Export the official game through Options and keep that string untouched in a dated file. Load a copy into your chosen version-compatible editor, change one field and export the edited result to a different file. In the game, use Import save to load the edited string only after confirming you have the original backup.

Verify the bakery name, bank, building counts and affected upgrades. Reload and check that the state persists. If the result is inconsistent or fails to load, restore the original. A save from a future version can be rejected by an older game even when the text itself is complete.

An imported “OP” save replaces your progression; it is not a code that safely layers rewards onto your current run. Infinity can break calculations, so finite test balances are easier to inspect. If you only want a test amount in the browser game, the documented console commands avoid hunting for an anonymous save file.

Keep edited experiments separate from achievement challenges and speedrun records. For ordinary device transfers you do not need an editor at all: follow the export and import guide.