> For the complete documentation index, see [llms.txt](https://wiki.retrobat.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.retrobat.org/advanced-features/save-states.md).

# Save States

Save states take a snapshot of a game at any moment, so you can reload it later exactly at the same point.

{% hint style="danger" %}
Save states are not a safe way to keep your progress. They often stop working after an emulator update. Always use the save system of the game itself (memory card, save menu…) first.
{% endhint %}

## How it works

* RetroBat manages save states for **RetroArch cores** and for several standalone emulators (see Compatible emulators). For these emulators, you can launch a game directly from a save state from the game list.
* Save states are stored in `saves\<system>`, in the folder of the emulator (for RetroArch: `saves\<system>\libretro.<core>`), with a screenshot of the moment of the save.
* A game that has save states shows an icon in the game list.
* Save states are not shared between emulators: a state made with one emulator can only be loaded by this emulator.

### Compatible emulators

Folders in `saves\<system>`. **Auto save**: AUTO SAVE/LOAD option supported. **Incremental**: INCREMENTAL SAVESTATES option supported.

| Emulator                   | Folder                                 | Auto save | Incremental |
| -------------------------- | -------------------------------------- | :-------: | :---------: |
| RetroArch (libretro cores) | `libretro.<core>`                      |     ✔     |      ✔      |
| Amiberry                   | `amiberry`                             |           |             |
| ArcadeDuck                 | `arcadeduck`                           |     ✔     |      ✔      |
| Azahar, Azahar Plus        | `azahar\states` / `azahar-plus\states` |           |      ✔      |
| BigPEmu                    | `bigpemu`                              |           |             |
| BizHawk                    | `bizhawk\sstates\<core>`               |           |             |
| BlastEm                    | `blastem`                              |     ✔     |             |
| DeSmuME                    | `DeSmuME\stateslots`                   |           |             |
| Dolphin                    | `dolphin`                              |           |             |
| DuckStation                | `duckstation`                          |     ✔     |      ✔      |
| Flycast                    | `flycast\sstates`                      |           |             |
| Gopher64                   | `gopher64\states`                      |           |             |
| Jgenesis                   | `jgenesis\states`                      |           |             |
| Keisho                     | `keisho\sstates`                       |           |      ✔      |
| Model3-Vulkan              | `model3-vulkan`                        |           |      ✔      |
| Mupen64 (RMG)              | `mupen64`                              |           |             |
| Odin                       | `odin\sstates`                         |           |      ✔      |
| OpenCDi                    | `opencdi`                              |           |      ✔      |
| openMSX                    | `openmsx`                              |           |             |
| PCSX2                      | `pcsx2`                                |     ✔     |      ✔      |
| Play!                      | `play\states`                          |           |             |
| PPSSPP                     | `ppsspp`                               |           |             |
| xbased                     | `xbased\sstates`                       |           |      ✔      |

{% hint style="info" %}
Azahar, Keisho, Odin, OpenCDi and Play! do not save a screenshot with their states: the manager shows the RetroBat save state icon instead. Odin keeps only one state per game (F2 / F4): RetroBat turns each save into a new save state in the manager.
{% endhint %}

## Saving and loading during a game

Use the standard RetroBat hotkeys:

| Action             | Controller          | Keyboard |
| ------------------ | ------------------- | -------- |
| Save state         | HOTKEY + WEST       | F2       |
| Load state         | HOTKEY + NORTH      | F4       |
| Previous save slot | HOTKEY + D-pad down | F6       |
| Next save slot     | HOTKEY + D-pad up   | F7       |

{% hint style="info" %}
If you customized your hotkeys, use your own combinations. See the Hotkeys page.
{% endhint %}

## Launching a game from a save state

1. In the game list, highlight the game.
2. Press **NORTH** (or **L3**) to open the **SAVESTATE MANAGER**. You can also hold **SOUTH** to open the **GAME OPTIONS**, then choose **SAVE STATES**.
3. Choose a save state, then press **SOUTH** (**LAUNCH**).

<div align="left"><figure><img src="https://990680527-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FexdzL60ZuqPLldz2AYta%2Fuploads%2FIYhqVWM6Q3xGIFhL8TNi%2Fimage.png?alt=media&amp;token=772f1d5c-6cc1-4853-b49e-7abac56a4b41" alt=""><figcaption></figcaption></figure></div>

The manager shows:

<table><thead><tr><th width="254">Item</th><th>Use</th></tr></thead><tbody><tr><td><strong>START NEW GAME</strong></td><td>Starts the game from the beginning, without loading any save state.</td></tr><tr><td><strong>START NEW AUTO SAVE</strong></td><td>Shown when AUTO SAVE/LOAD is on and there is no auto save yet: starts the game and creates an auto save when you quit.</td></tr><tr><td><strong>AUTO SAVE</strong></td><td>The state saved automatically when you last quit the game.</td></tr><tr><td>Save states</td><td>Your save states, with their date (and their slot number when incremental save states are disabled).</td></tr></tbody></table>

In the manager:

* **SOUTH**: launch the game from the selected state.
* **WEST**: delete the selected state.
* **NORTH**: copy the selected state to a free slot.
* **EAST**: go back.

{% hint style="info" %}

* A save state made with another emulator shows the name of this emulator. When you launch it, RetroBat uses this emulator automatically.
* If you enabled **ACCESS GAME OPTIONS WITH NORTH BUTTON**, the buttons are swapped: **NORTH** opens the game options, and holding **SOUTH** opens the save states.
  {% endhint %}

## Options

The options are in **MAIN MENU > GAME SETTINGS**, **SAVESTATES** group.

<div align="left"><figure><img src="https://990680527-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FexdzL60ZuqPLldz2AYta%2Fuploads%2FzcsAt649yMkJ0u6UmTvB%2Fimage.png?alt=media&amp;token=af73131d-a780-4597-b88e-5a901fc7d993" alt=""><figcaption></figcaption></figure></div>

### AUTO SAVE/LOAD

When it is on:

* when you quit a game, its state is saved automatically (**AUTO SAVE**);
* when you launch it again, the game resumes exactly where you stopped.

To start from the beginning instead, open the save state manager and choose **START NEW GAME**.

This option can also be set for one system only: **MAIN MENU > GAME SETTINGS > PER SYSTEM ADVANCED CONFIGURATION > (system) > AUTO SAVE/LOAD ON GAME LAUNCH** (AUTO, ON or OFF). It only appears when the emulator of the system supports it (**Auto save** column of the compatible emulators table).

### INCREMENTAL SAVESTATES

Decides when a save state can overwrite an older one (emulators ticked in the **Incremental** column of the compatible emulators table; the others always use the current slot):

<table><thead><tr><th width="289">Choice</th><th>Behavior</th></tr></thead><tbody><tr><td><strong>INCREMENT PER SAVE</strong> (default)</td><td>Each save creates a new save state: the older ones are never overwritten.</td></tr><tr><td><strong>INCREMENT SLOT</strong></td><td>During a game, saving overwrites the current slot, but each new game starts on a free slot.</td></tr><tr><td><strong>DO NOT INCREMENT</strong></td><td>The game uses the current slot: a new save can overwrite an older one, as in the emulator alone.</td></tr></tbody></table>

### SHOW SAVESTATE MANAGER

Opens the save state manager when you launch a game with **SOUTH**:

* **NO** (default): the game starts directly.
* **ALWAYS**: the manager opens for every game that supports save states.
* **IF NOT EMPTY**: the manager only opens when the game already has save states.

### Save state icon

To hide the icon of games with save states, disable **SHOW SAVESTATE ICON** in **MAIN MENU > USER INTERFACE SETTINGS**, **ICONS** group.

## Good to know

* **RetroAchievements:** in hardcore mode, loading a save state is disabled.
* **Emulator updates:** after an update, an old save state may no longer load. Keep a normal save of the game.
* **Emulators not managed by RetroBat:** other emulators may have their own save states, from their own menu. They do not appear in the save state manager.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.retrobat.org/advanced-features/save-states.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
