Cheat Sheets / Cookie Clicker / Save editor
Cookie Clicker save editor
This Cookie Clicker save editor runs entirely in your browser: paste the code from Options, Export save, change your cookies, buildings, heavenly chips, sugar lumps or bakery name, then copy the new code into Import save. Your save never leaves your device, because the page reads and writes it with no network call. Every kind of change it offers was loaded by the game's own import code in version 2.058 and showed exactly the numbers that were set.
Save editor
Works on this device only: nothing you paste is sent anywhere, stored, or put in the address bar.
Buildings (20)
- In Cookie Clicker, open Options and press Import save (or press Ctrl+O).
- Paste the new code into the box.
- Press Load. The game wipes the current bakery and loads this one, so keep your old code too.
How Cookie Clicker saves work
A save code is your whole bakery written as one line of text, then scrambled into base64 so it is safe to copy. Unscrambled, it is ten parts split by |: the game version, an empty part, your run (start dates, bakery name, a random seed, your appearance), 27 settings switches, 55 numbers about the game (cookies, chips, sugar lumps and the rest), one row for each of the 20 buildings, a 0 or 1 pair for each of the 876 upgrades (unlocked, bought; the Stats menu counts 717 of them, and 129 are heavenly upgrades), a 0 or 1 for each of the 643 achievements, the boosts running right now, and add-on data. The code ends in %21END%21, which is !END! written the safe way.
There is no password, checksum or signature in it. The game reads whatever the code says, cleans your bakery name, and works a few things out again as it loads: your prestige level (from the cookies you baked in past ascensions), your cookies per second, how many buildings, upgrades and achievements you own, and what you earned while the game was closed. The same code is what the game keeps in your browser's storage every time it autosaves.
How to export and import a save
- Export: open Options, press Export save, and copy everything in the box. On the web version, Save to file gives you the same code as a .txt file, which the editor above can open.
- Import: open Options, press Import save (or Ctrl+O), paste the code and press Load.
Keep your old code. Importing replaces the bakery you have open. If the game says "Error importing save", the code was cut short when you copied it: export it again and copy all of it.
What is safe to edit
The editor only changes the fields below, and writes every other character of your code back exactly as it was. With no change at all it gives you back the identical code.
| Field | What the game does with it |
|---|---|
| Cookies in the bank | Loads it as it is. If it ends up bigger than your cookies baked this ascension, the game's 5 second check gives you the shadow achievement Cheated cookies taste awful (see below). |
| Cookies baked this ascension | Loads it as it is. The game then gives the cookies baked achievements and upgrades it qualifies for, checking every 5 seconds, and it counts toward the heavenly chips of your next ascension. |
| Prestige level | The game never trusts the saved level: every load works it out from the cookies you baked in past ascensions. So the editor sets that number to the smallest amount that gives exactly your level. It does not add heavenly chips. |
| Heavenly chips | Loads them as they are. No check: the line that once compared chips with prestige is switched off in the game's code. |
| Sugar lumps | The editor also raises "sugar lumps harvested" by the same amount, the way the game's own lump gain does, because a bakery that has not started lumps yet would otherwise reset them to 0 the moment lumps unlock. |
| Buildings | As it loads, the game runs each building's own buy check, so you get the achievements and store upgrades the new counts qualify for. Past about 4,000 of one building, the price of the next is too big for the game to show and reads Infinity. |
| Bakery name | The game keeps only letters, digits, spaces, ', - and _, turns anything else into a space and cuts the name at 28 characters. The editor shows you that cleaned name before you copy. |
| Every normal achievement | Sets the 622 normal achievements as won, the same state as winning them, without the pop-ups. Milk follows: one milk flavor per 25. |
Not offered, on purpose: unlocking every upgrade in the save. Many upgrades do their real work when they are bought (seasons, the elder pledge, switches with two sides), and setting them in the save skips that, which leaves your bakery in a state the game never makes. Use the game's own Game.SetAllUpgrades(1); from the cheats page instead. The editor also leaves the minigames (garden, pantheon, grimoire, stock market), the dragon, Santa, wrinklers and settings exactly as they are.
Does editing a save count as cheating?
The game does not know your save was edited: there is nothing in the code that checks it. What it does check, all of it, straight from its script:
- Your bank against your cookies baked. Every 5 seconds of play, if you have more cookies in the bank than you baked this ascension, you win the shadow achievement Cheated cookies taste awful. That is the only check on numbers. "Keep it clean" above avoids it by raising cookies baked to match your bank.
- The dev tools name. A bakery name that ends in
saysopensesameopens the game's hidden dev tools as the save loads (web version only), which gives the cheat achievement at once. The editor warns you if your new name does that. - Add-ons. Loading a mod gives the shadow achievement Third-party.
Cheated cookies taste awful is a shadow achievement: it gives no milk, does not count in your achievement total and changes nothing else in the game. If you already have it, tick "Remove Cheated cookies taste awful" with "Keep it clean" on, and it stays gone. The cheats page lists which console cheats trigger it.
Phones and Steam
- Web version in a phone browser: the same game and the same save code as on a computer, so the editor works the same, and this page is built for phone screens. Export save opens the code in a box with all of it already selected by the game, so on a phone you only need to copy.
- Steam: the desktop app runs the same save code, but it adds its own add-on data and reports achievements to Steam as you win them. The editor was checked against the web version 2.058 only, so a Steam save is not covered here. A save that says a different version number is refused rather than guessed at.
- The Cookie Clicker phone app is a separate game with its own saves. Nothing on this page was checked against it.
Questions people ask
Is there a Cookie Clicker save editor?
Yes, this page: paste your save code, change cookies, buildings, heavenly chips, sugar lumps, prestige level or your bakery name, and copy the new code back into Options, Import save. It runs in your browser and sends nothing anywhere.
How do I edit my Cookie Clicker save?
Export it from Options, paste it into the editor, change the numbers you want and copy the new code. Then open Options, press Import save, paste and press Load.
Is it safe to paste my save code here?
The page reads and writes your code in your own browser with no network call, does not store it and never puts it in the address bar. Keep a copy of your old code anyway, since importing replaces the bakery you have open.
Will editing my save give me the cheat achievement?
Only if your bank ends up bigger than your cookies baked this ascension, or your bakery name ends in saysopensesame. The game checks the first every 5 seconds; Keep it clean raises cookies baked so that check never fires.
How do I get more sugar lumps in Cookie Clicker?
Type the number you want in Sugar lumps and import the new code. The editor raises your sugar lumps harvested total by the same amount, as the game's own lump gain does, so the count stays when lumps unlock.
Can I change my prestige level?
Yes. The game works out prestige from the cookies you baked in past ascensions every time it loads, so the editor sets that number to give exactly the level you type. It does not add heavenly chips, which you can set separately.
Why does the editor say my save is not valid?
Either the code was cut short when you copied it, or it says a version other than 2.058. The editor reads only the layout it was checked against: export the save again from the web version and paste all of it.
How this was checked
Cookie Clicker's own script, main.js, as published at orteil.dashnet.org/cookieclicker (version 2.058), was read line by line: the code that writes a save, the code that reads it back, and everything a loaded value touches. Then the real game was run in a locked-down browser with no network:
- the game made six saves of its own: a new bakery, mid-game, a bakery with the cheat achievement, after an ascension, a long bakery name with accents and Chinese letters, and one with all four minigames running;
- for each, reading and writing with no change gave back the identical code, and the game loaded the rewritten code exactly as the original;
- for each kind of change, the game loaded the edited code and showed exactly the edited values, and nothing else changed except what the game itself works out on load (achievements and upgrades for new building counts, prestige, cookies per second), which matched the same change made inside the running game;
- played for 6.5 seconds: a bank above cookies baked won the cheat achievement, and the same change with Keep it clean did not.
- main.js and the four minigame scripts from orteil.dashnet.org/cookieclicker (version 2.058), checked on 2026-11-15.
- Where each fact lives:
Game.WriteSaveandGame.LoadSave(the save layout),Game.ImportSaveCode(import),Game.bakeryNameSet(name cleaning),Game.HowMuchPrestige(prestige),Game.gainLumpsandGame.doLumps(sugar lumps) and the 5 second check that awards Cheated cookies taste awful. - Saves longer than 500,000 characters are refused; the game's own saves were about 4,000 to 5,000.
Cookie Clicker is made by Orteil and Opti of DashNet; play it at orteil.dashnet.org/cookieclicker. GardenFlouer is a fan site and is not connected to them.
Read next
- Cookie Clicker cheats: every console command, the cheat name and what each one does to your save.
- Every Cookie Clicker achievement: the full list with a checklist that reads your save code.
- Cookie Clicker ascension guide: a prestige calculator, when to ascend, and every heavenly upgrade in buying order.
- Cookie Clicker garden guide: every seed and mutation, with a seed finder that draws the layout for your plot.
- Cookie Clicker Grandmapocalypse: the stages, a wrinkler calculator and the real odds of every wrath cookie.
- Cookie Clicker sugar lumps: lump types and their odds, a lump calculator, and what to spend lumps on first.
- Cookie Clicker name cheat: the saysopensesame rule, a name checker and every button of the dev tools panel.
- Cookie Clicker shadow achievements: all 17 with the check behind each and the quickest honest way.
- Cheat Sheets: codes and secrets for more games, each one checked.