# Why didn't my game save?

**URL:** https://community.muos.dev/t/why-didnt-my-game-save/343
**Category:** FAQ
**Tags:** emulator, save, sleep, sram, autosave
**Created:** [May 10, 2025, 11:56am UTC](https://community.muos.dev/t/why-didnt-my-game-save/343 "2025-05-10T11:56:54Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![system](https://community.muos.dev/user_avatar/community.muos.dev/system/32/2547_2.png) [@system](https://community.muos.dev/u/system)
#### Post date: [May 10, 2025, 11:56am UTC](https://community.muos.dev/t/why-didnt-my-game-save/343/1 "2025-05-10T11:56:55Z")

</div>

### [How do I properly save my game?](#properly)

To ensure your in-game save is written to storage, you **must exit content properly** using one of the following methods:

- Menu + Start shortcut
- RetroArch Quick Menu \> Close Content (`MENU + X`)
- Sleep to Shutdown (_not Sleep until Wake_)

If you do **not** use one of the methods above, the SRAM remains in memory and is **never saved to disk**.

> **Important:** This is _not_ a bug. It is how RetroArch is **intended** to behave. In-game saves (also known as **SRAM** ) are only written to disk **when the content is closed properly**.

### [What happens if I put the device to sleep?](#sleep)

So, if you:

- press Reset
- run out of battery while asleep, or
- use normal Sleep Suspend (not Sleep to Shutdown),

then the power is cut **without shutting the system down properly**!

This means your in-game save will be lost and you may potentially corrupt system files! These devices do not have the same advanced power management found in smartphones. Do not rely on Sleep for long periods.

### [Isn’t this an emulator issue?](#emulator)

**Not at all.** This behaviour also exists on **real retro consoles**!

Many older consoles stored game data in RAM and only flushed it to persistent storage (_if available_) **after the console was powered off properly**. Some didn’t even have persistent save storage, hence the use of **password systems** in older titles.

It’s more noticeable in emulation because:

- Users often leave games suspended for long periods
- Emulators simulate the original system’s save logic
- Unexpected shutdowns are more common on handheld or embedded systems

### [What can I do to prevent save loss?](#prevent)

Here are some suggested safer alternatives:

- **Use Sleep to Shutdown**  
Enable **Sleep to Shutdown** , so after a period of inactivity the system will shut down cleanly thereby saving your game before powering off.

- **Enable Auto Save/Load State**  
In RetroArch:

- **Adjust SaveRAM Autosave Interval (_optional_)**  
Also under `Settings > Saving`, you can enable `SaveRAM Autosave Interval`  
This periodically writes in-game saves to disk while playing (_e.g. every 30 minutes_).

> **Please Note:** Enabling SaveRAM uses more system resources and it may increase wear on your SD card. **Use this option with care.**

* * *

If you’re losing in-game progress, it’s not a bug or failure of the muOS or RetroArch. It is how many original systems, and by extension, emulators work.

**To avoid this:**

- Always **exit games properly**
- Use **safe shutdown** or **Sleep to Shutdown**
- Enable **Auto Save/Load State** and/or **SRAM autosave**

## Protect your progress!

---

_[View the full topic](https://community.muos.dev/t/why-didnt-my-game-save/343)._