> For the complete documentation index, see [llms.txt](https://docs.kouch.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kouch.dev/playing/save-states-and-screenshots.md).

# Save states and screenshots

Save states, load states, reset and screenshots from the Quick Menu, and where the files go.

Hold **Select + Start** in a game, choose **Game**, then:

| Action         | What it does                              |
| -------------- | ----------------------------------------- |
| **Save state** | Saves the game exactly where you are.     |
| **Load state** | Goes back to your saved state.            |
| **Reset**      | Restarts the game. Hold **A** to confirm. |
| **Screenshot** | Saves a picture of the game.              |

## How it works

Kouch presses the emulator's own keyboard shortcut for each action, the way you would. The emulator's profile says which keys those are. So:

* An action only works when the emulator's profile knows its shortcut. Profiles you import bring them with them. An emulator you added by hand in **Settings › Emulators › Add emulator** has none, so these actions tell you they aren't set up.
* **Save state** and **Load state** use the emulator's current slot. A [plugin](/mods-and-plugins/plugins.md) can add more actions to the Quick Menu. The sample plugin *Save slots*, for example, adds **Quick save** and **Quick load**.
* The emulator saves the state and the screenshot itself, in the folders Kouch set up for it.

## Where the files go

Everything an emulator saves lives in your Emulation folder, in the emulator's folder under `saves`:

```
Emulation\saves\<emulator>\
  saves\        the game's own saves
  states\       save states
  screenshots\  screenshots
  config\       the emulator's settings
```

To open it, go to **Settings › Emulators**, highlight the emulator and choose **Open data folder**.

{% hint style="info" %}
A game's **own** save (the one the game makes when you save in its menus) doesn't need the Quick Menu. It saves as usual, into `saves`.
{% endhint %}

## Screenshots in Steam

Once Kouch is on Steam, the screenshots you take in a game also show in **Steam's Screenshots view**. It's on by default; turn it off with **Settings › Display › Screenshots › Add game screenshots to Steam**. Until then the switch says **Starts once Kouch is on Steam**.

## Keeping them safe

* [Transfer](/online/online/lan-transfer.md) copies saves, states, screenshots and settings to another PC in your home.
* **Settings › Emulators › Export…** packs them into a `.kod` backup file. See [Back up and restore](/emulators/emulators/backup.md).
* Steam Cloud sync is on for every emulator and starts working once Kouch has its own Steam app. See [Steam Cloud saves](/steam/steam/steam-cloud.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kouch.dev/playing/save-states-and-screenshots.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.