EMUKING

Save files and save states

These are two completely different mechanisms that both feel like "saving". Mixing them up is the most common way people lose progress.

A save file is the game saving itself, the same way it would on real hardware. A save state is a photograph of the entire console, taken from outside the game. Only one of them existed in 1998.

Save files: how cartridges remembered

Game Boy cartridges had no hard drive. Games that could save shipped with a small amount of memory inside the cartridge and a coin cell battery to keep it powered. When you chose Save on the menu, the game wrote your progress into that memory, and the battery held it there while the console was off.

This is why old cartridges eventually forget everything. The battery is thirty years old. When it dies the memory loses power and the save goes with it, which is also why a dead battery cannot be fixed by anything other than replacing it.

A .sav file is a copy of exactly that memory. Nothing more. It is a small file, often 8 KB to 128 KB, in a format every emulator agrees on. The same file works in EmuKing, in mGBA, in RetroArch, and on a flash cartridge in a real Game Boy.

Because a save file is the game's own save, it obeys the game's own rules. You get the save slots the game offers, at the points the game allows. If a game only saves at a church or a rest point, that is where your save file updates.

Save states: a photograph of the console

A save state has nothing to do with the game. It records the entire emulated machine at one instant: every processor register, all of working memory, the video memory, the sound channel positions, and where the picture processor was on the screen.

Loading one puts all of that back exactly as it was. The game is not told anything happened. As far as it knows, no time has passed at all.

That is why save states can do things the game never permitted. You can save in the middle of a boss fight, mid jump, or during dialogue, because nothing is asking the game's permission.

The trade offs

EmuKing versions its save states, so if the emulator changes internally your existing states either keep working or are clearly marked as unreadable. What it will never do is claim to load a state and quietly leave your game untouched.

Where your progress actually lives here

EmuKing runs entirely in your browser, and your game file is opened read only. It is never modified. When a game saves, that data goes into your browser's own private storage for this website.

That has one consequence worth understanding properly: your progress exists in exactly one place. It is attached to this browser, on this device, for this address. Specifically it does not follow you to:

And it is deleted if you clear your browsing data, since to the browser it is site data like any other.

Export your save if it matters to you. The Export .sav button downloads a real save file to your device. That downloaded copy is the one that is genuinely yours, and it is the only copy that survives clearing your browser, switching machines, or reinstalling.

Moving progress to another device

  1. On the device that has your progress, load the game and press Export .sav.
  2. Move the downloaded file across however you like: a cable, a USB stick, cloud storage, email.
  3. On the new device, load the same game and press Import .sav.

Save states do not transfer this way, and that is expected. Export the save file, then make a fresh state on the new device if you want one.

A habit worth keeping

Use save states freely while you play. They are excellent for difficult sections and for trying cheat codes without risk. But treat them as convenience, not as your record of progress.

Every so often, save properly inside the game, then export the .sav. That file is your real backup. Do it before clearing your browser, before switching devices, and before experimenting with cheats.