Where Are Blazing Chrome Save Files Located?
Blazing Chrome saves .bin files in AppData with config beside them, plus a Store package split and full cloud cover.
Last updated
Blazing Chrome is GameMaker with per store folders. Standard builds save .bin files in AppData under a Blazing_Chrome folder, with config INIs beside them. The Store build uses its Xbox package folder instead.
File copies only work within the same store, with each store cloud bridging its own side. The 58 FPS cap surprises performance hunters but changes nothing about files. Copy the AppData folder for Steam moves and leave the package tree to Store owners.
Where Blazing Chrome stores this, by platform
%APPDATA%\Blazing_Chrome
Progress as .bin files with config beside them. Paste the path into Explorer. The folder appears after the first save.
%LOCALAPPDATA%\Packages\DotEmu.BlazingChrome_map6zyh9ym1xy\LocalState
Microsoft Store copies. Packaged builds write into LocalState instead of AppData.
<SteamLibrary>/steamapps/compatdata/609110/pfx/
Steam Play prefix, app ID 609110. The AppData tree is mirrored inside it.
Frequently asked questions
How do I move Blazing Chrome saves to a new PC?
Copy the Blazing_Chrome folder to the same AppData path with the game closed. Progress and config travel together. Cloud mirrors exist on every store, but the folder copy is exact.
Where is the Blazing Chrome config file?
Open gog_config.ini in the same folder with a text editor while the game is closed. Display and audio toggles live there. Most options also exist in game, which is safer than hand editing.
Can I move a Steam save to the Store version?
The Microsoft Store copy writes into its DotEmu package folder instead of AppData. Copying between store trees does not transfer progress, so stay within the same store when moving.
Notice an outdated path? Let us know.