Cookie Clicker offline progress not working? Check these three things.
A normal desktop-browser save needs Twin Gates of Transcendence to earn cookies while the tab is closed. If your bakery and buildings returned and the cookie counter rises with the tab open, check whether you own that heavenly upgrade. Keep your save while you diagnose the issue.
Scope: one continued early-game desktop Chrome save, version 2.058. One Cursor, displayed 0.1 cookies per second, Stats showing 0 unlocked ordinary upgrades. No ascension, added offline upgrade, mod, game-console command or cleared browser data during this test. This is not a Steam, mobile-app, sleeping-computer or later-game performance test.
Use this order before treating it as a broken game
- Check whether the intended save loaded. Compare the bakery, owned buildings and progress you recorded before leaving. Our return kept the same bakery and one Cursor. A different or empty state is not the same result. Preserve your backup before attempting an import or reset.
- Check whether production exists while the page is open. Stats showed one building and 0.1 cookies per second in our opening. If your owned count or production is zero, waiting for an offline feature is not a diagnosis of that zero-production state. If you sold your only Cursor, follow the separately tested Buy-mode recovery route.
- If the save and producer both returned, check closed-game eligibility. The ordinary browser game's offline calculation has a condition involving Twin Gates of Transcendence. A Cursor purchase is not that upgrade. The condition and exceptions are explained below; do not assume that the word “idle” means identical production with the page open and closed.
What our saved return actually showed
We used Options → Save before closing the only Cookie Clicker tab in the test profile. The options text also identified a 60-second autosave interval. We made no purchases or manual cookie clicks during these observations. The first attempt is deliberately reported with its reading delay: the returning page initially showed a loader, and we did not read the loaded counter until later.
| Condition | Observation |
|---|---|
| First manual save and closure | 101 cookies; 0.1 per second. Closed at 22:24:43.350 Hong Kong time. |
| First reopen attempt | Started at 22:26:54.381, after 131.031 seconds between browser actions. Initial observation was a loader, not a cookie counter. |
| Delayed loaded-page read | 103 cookies at 22:27:13.571, about 19 seconds after starting the reopen. This includes possible open-page production and is not an exact offline-earnings measurement. |
| Open-page comparison | 105 cookies at 22:27:36.664, after the previous 103-cookie read. The tab remained open; production still displayed 0.1 per second. |
| Second saved return | Saved at 105; closed at 22:27:41.160. Reopen began at 22:30:23.741, after 162.581 seconds between actions. The counter node was initially empty. The first nonempty read was 106 at 22:30:32.714, about 9 seconds after starting the reopen. |
The first return is useful precisely because it does not justify subtracting 101 from 103 and calling the difference offline earnings. Production resumed while the returning page was open, and the display rounds its values. The open-page comparison confirms that the Cursor could still produce; it does not turn the closed interval into an exact rate experiment.
What changes when offline production is unlocked?
We checked the official browser game's source, rather than relying on a genre label. Its closed-game cookie calculation is conditional on mobile mode, Perfect idling, or ownership of Twin Gates of Transcendence. Twin Gates is defined in the prestige upgrade pool. These exceptions matter: this article tests the ordinary early desktop-browser run, not those other modes.
That code inspection explains why an intact early save and a working Cursor can coexist with no closed-game catch-up. It is not a direct test of purchasing Twin Gates or its later upgrade branches. We have not tested their returns here, and this article does not recommend an ascension timing or promise that an unlocked run earns at the same rate as an open one.
Source rechecked October 21: the live official script still has the same closed-game condition as the source inspected for our October 13 test. This is a code recheck, not a new gameplay experiment. The recorded return observations remain dated October 13.
Which problem are you actually trying to fix?
| What you see | Useful next action |
|---|---|
| Your bakery or buildings are missing | Investigate which save and browser profile loaded. Keep your backup; do not overwrite it with the unexpected state. This is a persistence problem, not evidence about an offline rate. |
| Your save is intact, but open-page production is zero | Check the owned producer and Buy/Sell mode. If the last Cursor was sold, use our tested first-Cursor recovery steps. An offline setting cannot explain away a missing producer. |
| Your save is intact and open-page production works | Check the closed-game eligibility above. If you already own the relevant upgrade, this early-save test is not a complete diagnosis of your upgraded run: record the version, upgrade state, absence duration and first loaded reading before requesting help. |
The reader confusion is real. A new-save player discussion contains conflicting claims about whether offline production is automatic; another not-earning discussion directs attention to ascension upgrades. Those are player reports, not controlled evidence for your browser. Our test and the current official code provide the narrower checks above.
How to repeat the check without risking your run
- In Options, use Export save or Save to file to keep a backup. These are the game's own displayed backup choices. Keep the original until a restored copy has been verified.
- Record the version, bakery, owned producer count, current bank and displayed production. Use Save before the closure.
- Close the game tab, record your action time, and reopen the same address in the same browser profile. If another game tab remains running, that is a different setup.
- Read the loaded counter promptly and record any loader delay. Check that the intended save and buildings returned before interpreting the cookie difference.
- Compare a short open-page observation separately. Do not clear browser data, wipe the save or ascend simply to diagnose why an intact opening did not earn while closed.
Quick answers
Does saving enable offline production?
No such result follows from this test. Saving and restoring the opening did not itself add an offline upgrade. Our save-and-refresh report covers persistence; this page asks what happens during a deliberately closed interval.
What if the tab is open in the background?
That was not the closed-tab condition tested here. The Options panel exposes Sleep mode timeout and describes an inactive-page behavior, but we did not toggle or benchmark it. Record whether the tab was closed, backgrounded or left on a sleeping computer instead of treating those conditions as interchangeable.
Should I restart or ascend to fix this?
Neither action is justified by our intact-save result. First follow the save, production and upgrade checks. This report does not establish the right time to ascend or diagnose every later-game problem.
What if I will leave the game open instead?
That is a different purchase decision. Our 100-cookie upgrade-versus-Grandma comparison checks manual click power and open-page automatic production separately. Its October 16 purchases happened after the closed-tab experiment described here; they do not change this report's original one-Cursor, no-upgrade conditions.
If you are comparing the best incremental games for short check-ins, decide whether you want an open-page background project or verified closed-game progress at your current stage. Our separate offline field report shows why the save condition must be stated for each game. This Cookie Clicker result is one early save, not a ranking of the entire game.
Looking for a different game instead of fixing this save? Compare four personally tested browser openings after Cookie Clicker, with a try/skip reason and a stated endpoint for each. That is a play-style comparison, not a promise that every alternative earns while closed.