How to Enable Cookie Clicker Mods (Steam + Web)

Cookie Clicker mods extend the game with new buildings, calculators, autoclickers, and entire game systems Orteil never shipped. Enabling them is straightforward on Steam (subscribe in the Workshop, restart the game) and slightly more involved on the web version (install the CCSE mod loader via the browser console). This how-to-enable-Cookie-Clicker-mods guide covers both paths, the most useful starter mods, and the gotchas that can corrupt your save if you’re not careful.

Steam Workshop method

The Steam version of Cookie Clicker launched in 2021 with full Steam Workshop support. This is the easiest mod path by a wide margin.

1. Open Cookie Clicker on Steam.
2. Click the Workshop button from the main menu, or navigate to the Cookie Clicker Workshop page in your Steam browser.
3. Browse available mods. Click Subscribe on any you want to install.
4. Quit Cookie Clicker and reopen it. Subscribed mods load automatically on launch.
5. The mods menu now appears inside the game. Each loaded mod can be enabled, disabled, or configured individually without uninstalling.

Unsubscribing in the Workshop removes the mod. If a mod misbehaves, disable it first via the in-game menu before unsubscribing — that avoids any save-state issues from sudden removal.

Web (free version) method

The free web version of Cookie Clicker at orteil.dashnet.org/cookieclicker doesn’t have a built-in mod system. The community solution is CCSE — the Cookie Clicker Script Extender — built by Klattmose. CCSE acts as a mod loader and exposes a menu for installing individual mods.

Install CCSE

1. Open Cookie Clicker in your browser at orteil.dashnet.org/cookieclicker.
2. Open the browser developer console. F12 on most desktops, or right-click → Inspect → Console tab.
3. Paste the official CCSE installer script. The current script is published on Klattmose’s GitHub — the canonical source is the CCSE repository. The script is a one-line Mod.loadScript or similar.
4. Press Enter. CCSE loads and adds a menu entry to Cookie Clicker’s Options panel.

The script runs only for that page load. If you refresh the browser, CCSE is gone and you’ll need to re-paste. Persistent loading requires either a browser extension that injects scripts on page load or a bookmarklet that runs the install on click.

Install individual mods through CCSE

Once CCSE is loaded, mods can be installed in two ways:

• Via CCSE’s mod menu: Options → CCSE → Mod Manager. Each available mod has a load button. Click and the mod activates in the current session.
• Via console for one-off mods: Paste the mod’s install script in the console the same way you installed CCSE. Many community mods publish single-line installers.

The session-only persistence problem applies to mods loaded through CCSE just as it does to CCSE itself. The browser doesn’t preserve injected scripts between refreshes.

Making mods persist across sessions

Tampermonkey or Greasemonkey

The standard solution is a userscript manager. Tampermonkey (Chrome, Edge, Firefox) or Greasemonkey (Firefox) lets you write a script that runs every time you visit orteil.dashnet.org/cookieclicker. The script can load CCSE and any mods you want.

A simple Tampermonkey userscript:

• Name the script “Cookie Clicker CCSE Loader”
• Set the match pattern to https://orteil.dashnet.org/cookieclicker/*
• In the script body, include the CCSE loader URL and optionally the install lines for any mods you use
• Save and reload Cookie Clicker — CCSE auto-loads

The current loader URL and exact syntax are documented on the CCSE GitHub README. Use that as the canonical reference rather than copying from third-party sources.

Backing up your save

Before enabling any new mod, export your save. Cookie Clicker’s vanilla save export is under Options → Save → Export Save. You’ll get a text string. Save it in a file.

Mods can occasionally corrupt save state — usually by adding fields the vanilla game doesn’t understand, then leaving them behind when uninstalled. A clean export gives you a guaranteed-restorable state. Disabling mods generally doesn’t break saves but reinstalling vanilla over a heavily modded save sometimes does.

For long-term modded saves, export weekly. Cloud saves on Steam are convenient but Steam Workshop changes that disable a mod can break saves you can’t roll back.

Starter mods worth installing

Cookie Monster

Cookie Monster (by Aktanusa, not to be confused with the Sesame Street character) is the most-installed Cookie Clicker mod. It adds payback time, return-on-investment, and bonus-income calculations to every building tooltip. Without Cookie Monster, you have to do those calculations manually or in your head. With it, the most efficient next purchase is highlighted automatically. Available on both Steam Workshop and through CCSE on the web.

Frozen Cookies

Frozen Cookies is an autoplay/optimization mod that can play the game for you, click golden cookies when they appear, and buy upgrades on the optimal schedule. It’s a hands-off way to progress past the early game grind. Some players consider it a cheat; others consider it a quality-of-life improvement. Use according to your preference.

CCSE itself

CCSE is technically a mod loader, but it also provides utility hooks that other mods rely on. Installing it gives you the framework even if you don’t load anything else.

Sugar Display

Sugar Display shows your sugar lump count and timing details next to the cookie counter. It’s a small quality-of-life addition for late-game players who plan sugar lump harvests around specific game events.

What can go wrong

Corrupted saves

The most common failure. Symptoms: cookies count is wildly wrong, buildings disappear, or the game refuses to load. Solution: paste your last clean save export and start the modded session over. If you don’t have an export, the save is usually gone.

Console errors

If CCSE or a mod fails to load, the console shows the error. Common causes: outdated mod that no longer matches the current Cookie Clicker version, blocked cross-origin script load, or conflict between mods. Try loading mods one at a time to isolate the bad one.

Browser updates breaking the loader

Chromium updates have occasionally tightened script-injection rules in ways that broke Tampermonkey loaders or direct console pastes. Keep the userscript manager updated.

Cheats vs mods

There’s a fuzzy line between mods that add features (Cookie Monster) and mods that cheat (autoclickers, infinite cookies, Game.cookies = 9e99 in the console). Orteil has been famously chill about cheats — the cheated-saves achievement is officially called “Cheated cookies taste awful” and Orteil himself has said in interviews that he doesn’t mind. Steam Workshop tends to skew toward feature mods rather than overt cheats. The console-based cheat scripts on the web version are well-documented in the Cookie Clicker wiki.

Our Cookie Clicker mods and cheats guide covers the deeper catalog. For game history, the Cookie Clicker Wikipedia entry tracks the release timeline.

Frequently asked questions

Are Cookie Clicker mods safe?

Mods from established sources (Steam Workshop, CCSE GitHub, Klattmose’s official repositories) are safe. Random console scripts from forum posts are not — they can be malicious or just buggy. Always check the source before pasting console scripts.

Do mods disable Steam achievements?

Some achievements are flagged as “cheated” if you use specific cheat mods. Feature mods like Cookie Monster generally don’t flag achievements. The flag is a separate “cheated cookies taste awful” badge — your other achievements still earn normally.

Can I use Steam Workshop mods on the web version?

No. Steam Workshop is Steam-only. The same mod authors usually publish a web-compatible version separately, loadable through CCSE.

What’s CCSE?

The Cookie Clicker Script Extender, built by Klattmose. It’s the de facto mod loader for the web version of Cookie Clicker and provides hooks that other mods rely on.

How do I uninstall a Cookie Clicker mod?

Steam: unsubscribe in the Workshop. Web with CCSE: disable in the CCSE mod menu, or refresh the browser to clear all session-loaded mods. Always export your save first.

The bottom line

Steam Workshop is the easy path — subscribe, restart, play. Web is more flexible but requires CCSE plus a userscript manager for persistence. Either way, export your save before enabling anything new. For a no-mod-needed reset between Cookie Clicker sessions, the Chrome Dino game is the original zero-friction click target.