---
title: "Save state vs save file: what’s the difference?"
description: "Save states snapshot your entire emulator memory; save files mirror the cartridge’s on-board battery. Here’s when to use each and how they’re stored."
url: "https://retrogamespace.com/guides/save-state-vs-save-file"
canonical_html: "https://retrogamespace.com/guides/save-state-vs-save-file"
canonical_md: "https://retrogamespace.com/guides/save-state-vs-save-file.md"
locale: "en"
slug: "save-state-vs-save-file"
author: "Mira Köhler"
author_slug: "mira-koehler"
date_published: "2025-10-01"
date_modified: "2026-04-30"
last_reviewed: "2026-04-30"
keywords: ["save state","save file","emulation savedata","SRAM emulation"]
source: RetroGameSpace
source_url: "https://retrogamespace.com"
---

# Save state vs save file: what’s the difference?

Save states snapshot your entire emulator memory; save files mirror the cartridge’s on-board battery. Here’s when to use each and how they’re stored.

## Save state — a memory snapshot

A save state is a complete snapshot of the emulator’s RAM, CPU registers, GPU state, audio buffers — everything. When you load it, the emulator resumes exactly where you froze it, mid-jump, mid-attack, mid-dialog. Save states are typically 64 KB to 4 MB depending on the system and are stored in your browser’s IndexedDB with a slot identifier.

Save states are an emulator-only feature — the original hardware had no equivalent. They’re the single biggest convenience emulation offers over real cartridges.

## Save file — the cartridge battery

A save file (often called SRAM, savedata, or .sav) is the data the original cartridge would have written to its on-board battery-backed SRAM. Pokémon Red’s save file holds your party, items, and badges. Final Fantasy VI’s holds your three save slots. The emulator persists this file to disk (or browser storage) and reloads it on next launch, exactly like the original hardware would.

Save files are typically 8 KB to 128 KB. Because they only persist between in-game saves at the in-game save points, they don’t let you rewind out of an unwinnable battle the way a save state does.

## When to use which

- Save state — quick rescue points before a hard boss, exploring a branching dialog, save-scumming for rare drops.
- Save file — long-term progress that you’d expect to survive the original hardware. Use save files for the runs you want to feel canonical.
- Both — most people use save states for tactical rescue and rely on save files for narrative progress. The two systems coexist; they don’t overwrite each other.

## Where they’re stored

In a browser-based emulator like EmulatorJS, both save states and save files live in IndexedDB scoped to the page’s origin. They are not synced across devices unless the host site explicitly implements cloud-sync. Clearing your browser data wipes both. Most browser emulators expose an export/import button to back them up as files on your local filesystem.

## FAQ

Q: Does the original game know about save states?
A: No. The game has no concept that a save state is being taken — it just runs as it would on hardware. Save states are entirely an emulator-side feature.

Q: Can I share save files between emulators?
A: Usually yes for save files (.sav format is fairly portable across libretro cores). Save states are emulator-specific because they include core-internal state.

Q: Will my saves transfer to another device?
A: Only if the emulator site supports cloud sync, or if you manually export and re-import them.

---

Source: [Save state vs save file: what’s the difference?](https://retrogamespace.com/guides/save-state-vs-save-file) — Mira Köhler • Last reviewed 2026-04-30 • RetroGameSpace