🍪 Cookie Clicker New

Cookie Clicker cheats and console commands

Every command on this page was run against the version 2.058 build that this site serves, not copied from another list. Anything that no longer exists in the game has been left out.

These are console commands, not a download. Cookie Clicker keeps its whole state in one JavaScript object called Game, and the browser lets you edit that object directly. There is nothing to install, no extension to add, and no site that needs your save file. Anyone offering you a "Cookie Clicker cheat .exe" is offering you something else.

On this page
  1. Opening the console
  2. The one thing that permanently marks your save
  3. Cookies and buildings
  4. Upgrades, achievements and unlocking everything
  5. Golden cookies and buffs
  6. Sugar lumps, dragon and prestige
  7. Auto-clicker in one line
  8. Backing up and undoing
  9. Mods are not cheats
  10. FAQ

1. Opening the console

The console has to be open on the tab where the game is actually running — this site's game page. Commands typed into a console on some other page do nothing, which is the single most common reason people report that "the cheats don't work".

If the console asks you to type "allow pasting" before it accepts anything, that is a browser safety prompt, not an error. Type it once and it stops asking.

2. The one thing that permanently marks your save

Cookie Clicker checks a single condition every few seconds:

if (Game.cookiesEarned < Game.cookies) Game.Win('Cheated cookies taste awful');

That is the entire cheat detector. It fires when the cookies in your bank exceed the cookies you have ever earned — which is exactly what happens if you set Game.cookies by hand. It awards a shadow achievement that cannot be removed without wiping the save, and shadow achievements do not count toward your milk.

The practical consequence is worth knowing before you start: Game.Earn() does not trip it, and Game.cookies = … does. Game.Earn() adds to both counters, so the check never sees an imbalance. Every cookie command below uses Game.Earn() for that reason.

Three other things set the flag directly rather than through that check: opening the game's own debug menu, Game.RuinTheFun(), and Game.SetAllAchievs(1) — the last one because the shadow achievement is itself an achievement, so awarding them all awards that one too.

3. Cookies and buildings

Game.Earn(1e12)

Adds a trillion cookies to both your bank and your lifetime total, so the cheat check stays happy. 1e12 is shorthand for a 1 with twelve zeroes — swap in 1e9, 1e15, 1e24, whatever you need.

Game.Objects['Cursor'].getFree(100)

Grants 100 free cursors without charging you and without inflating the price of the next one you buy normally. Replace the name with any building below.

The twenty building names, spelled exactly as the game stores them — the capitalisation matters and only the first word is capitalised:

CursorGrandmaFarmMineFactoryBankTempleWizard towerShipmentAlchemy labPortalTime machineAntimatter condenserPrismChancemakerFractal engineJavascript consoleIdleverseCortex bakerYou
for (var i in Game.Objects) Game.Objects[i].getFree(200);

200 of every building at once. This is the fastest way to a large CpS without touching the cookie counters at all.

Game.Objects['Farm'].level = 10;

Sets a building's sugar-lump level directly. Levels are what unlock the minigames — Farm level 1 opens the Garden, Wizard tower opens the Grimoire, Temple opens the Pantheon, Bank opens the Stock Market.

4. Upgrades, achievements and unlocking everything

Game.SetAllUpgrades(1)

Unlocks and buys every upgrade in the game. Pass 0 instead to take them all away again.

Game.SetAllAchievs(1)

Awards every achievement, which also maxes your milk. Again, 0 reverses it. Note that "every achievement" includes the shadow ones, so this command hands you "Cheated cookies taste awful" by itself — tested, it comes back set even when your cookie counters are perfectly balanced.

Game.Win('Neverclick')

Awards one specific achievement by its exact name. Useful for the handful that are genuinely tedious rather than for clearing the board.

Game.RuinTheFun()

The nuclear option, and it is named honestly. It buys every upgrade, awards every achievement, earns a trillion trillion cookies, maxes your specials and pushes every building to level 9. There is no way back short of a hard reset, and the game marks the save. If you want to see the endgame content once, this is the command; if you want to keep playing, it is not.

5. Golden cookies and buffs

new Game.shimmer('golden')

Spawns a golden cookie immediately. It behaves like a normal one — you still have to click it, and it still rolls a random effect, so this is a way to farm combos rather than to choose them.

Game.gainBuff('frenzy', 60, 7)

Applies a buff directly: the name, how many seconds it lasts, and its strength. This one is a 60-second ×7 Frenzy. Stacking frenzy with click frenzy and dragon harvest is how the enormous combo screenshots are made.

Every buff name the v2.058 build accepts:

frenzyclick frenzyblood frenzydragon harvestdragonflightcookie stormsugar frenzysugar blessingbuilding buffbuilding debuffclotcursed fingerdevastationeverything must gogifted outhaggler luckhaggler miserymagic adeptmagic ineptpixie luckpixie miseryloan 1loan 2loan 3
Game.elderWrath = 0;

Calls off the Grandmapocalypse without spending anything on an Elder Pledge. 1, 2 and 3 set the three escalating stages if you would rather turn it up.

Game.SpawnWrinkler()

Drops a wrinkler onto the cookie. Wrinklers eat your CpS but hand back more than they took when popped, so a screen full of them is worth farming — this only works while the Grandmapocalypse is active.

6. Sugar lumps, dragon and prestige

Game.lumps = 100;

Sets your sugar lump count. Lumps are the slowest resource in the game — one per day at best — so this is the command that saves the most real time of anything on this page.

Game.dragonLevel = 25; Game.ToggleSpecialMenu(1);

Jumps Krumblor to a chosen level — 25 is fully grown. The second half reopens the dragon panel, which is what makes the new level and its auras actually show up; without it the interface keeps drawing the old one.

Game.heavenlyChips = 1e6; Game.prestige = 1e6;

Sets both prestige currencies. Set them together: heavenlyChips is what you spend in the heavenly upgrade tree, prestige is what your CpS bonus is calculated from, and changing one without the other gives you a shop you cannot afford or a bonus you did not buy.

Game.Ascend(1)

Ascends straight away, skipping the confirmation screen. The 1 is the bypass flag — call it with no argument and you get the normal prompt.

7. Auto-clicker in one line

window.auto = setInterval(function(){ Game.ClickCookie(); }, 10);

Around fifty to a hundred clicks a second depending on what your browser can keep up with, using the game's own click function so every click bonus and click achievement counts it properly. It stops when you reload the page.

clearInterval(window.auto);

Stops the auto-clicker without reloading. It is hung on window deliberately: a plain var auto disappears the moment you paste the starter inside a function or a devtools snippet, and then nothing can stop it but a reload.

Ten milliseconds is about as fast as is worth going. Lower intervals do not click faster in practice, they just compete with the game's own rendering and make the whole page stutter.

8. Backing up and undoing

Do this before you experiment, not after. Your save lives in this browser's storage for this site only — it is not on our server, so if you overwrite it there is nothing on our end to restore.

Game.ExportSave()

Opens the game's export dialog with your save as a text string. Copy it into a file somewhere. This is the same thing as Options → Export save, just quicker to reach.

Game.ImportSave()

Opens the import dialog. Paste a backup back in to roll everything back to that point — including undoing a RuinTheFun(), as long as the backup predates it.

Game.WriteSave()

Forces an immediate save. Worth running after a batch of commands, because the game otherwise saves on its own schedule and a reload in between loses the lot.

If a command does not seem to have changed anything on screen, the value has usually been set and only the display is stale. Game.RefreshStore(); Game.upgradesToRebuild = 1; Game.recalculateGains = 1; forces the interface to catch up.

9. Mods are not cheats

Worth separating, because they get lumped together in every search result. Cookie Monster and Frozen Cookies are add-ons that show you information the game already has — which building is the best value right now, how long until an upgrade pays for itself, what a golden cookie is worth. They do not give you anything you have not earned, they do not touch the cookie counters, and they do not flag your save.

If your actual problem is "I do not know what to buy next", a mod solves it properly and the game stays a game. The commands above solve a different problem, which is wanting to see the late game without the two hundred hours.

10. FAQ

Will cheating ban me or delete my save?

No. Cookie Clicker is entirely single-player and runs in your browser; there is no server, no account and no ban. The only lasting consequence is the shadow achievement described above.

Do these work on the Steam version?

No. The Steam build has no browser console. Steam players use the game's own mod support instead, which is a different mechanism entirely.

Do they work on a phone?

No — mobile browsers do not expose a console, and no bookmarklet gets around that reliably. This is a desktop-only exercise.

Can I remove the "Cheated cookies taste awful" achievement?

Only by restoring a save from before you triggered it, or by wiping and starting over. There is no command that takes it back — it is deliberately one-way.

Why does my command say "Game is not defined"?

The console is attached to a different page than the one running the game. Open the game page, press F12 there, and try again. If the game is inside a frame, pick that frame in the console's context dropdown first.

Is there a cheat that gives infinity cookies?

You can set a number so large that JavaScript rounds it to Infinity, and the game will then display Infinity everywhere and stop calculating properly. It is not a state you can play from, and it survives a save, so it is the one thing here worth not doing.

← Back to the game