Where Does Cookie Clicker Store Its Save File?
The Steam version keeps save.txt in Steam userdata under app ID 1454400, with config in AppData and export text for the web build.
Last updated
Cookie Clicker started as a browser game, and the Steam release is an Electron wrapper around that same code. The result is a single save.txt inside Steam's userdata tree under app ID 1454400. Settings and window state live in %APPDATA%\cookie-electron, not next to the save.
Steam Cloud syncs the save file. The web version has no file to find, but the in-game export text moves progress between the two builds, unofficially. If you play both versions, keep a text export as the common backup.
Where Cookie Clicker stores this, by platform
C:\Program Files (x86)\Steam\userdata\[SteamID]\1454400\remote\save.txt
Single save file for the Steam build. [SteamID] is your numeric account folder and 1454400 is the app ID. Steam Cloud syncs this file. Close the game before copying it.
%APPDATA%\cookie-electron
Electron config and cache. Deleting it resets window and settings but does not remove save.txt from Steam userdata.
~/.steam/steam/userdata/[SteamID]/1454400/remote/save.txt
Steam userdata path on Linux. The config lives inside the Proton prefix at compatdata/1454400, but the save itself stays in userdata.
Frequently asked questions
Where is the Cookie Clicker save file?
For the Steam build, in Steam\userdata\[SteamID]\1454400\remote\save.txt. The web build stores progress in browser data instead of a file you can open.
Can I transfer Cookie Clicker progress to the web version?
Yes, through the in-game export and import text. It works both ways, but the developer does not officially support moving saves between the Steam and web builds.
Does Cookie Clicker have cloud saves?
Steam Cloud syncs save.txt for the Steam version. The web version has no cloud save, so use the export text as your backup.
Notice an outdated path? Let us know.