---
title: "mGBA: game won't save — how to fix GBA save types and RTC"
canonical_url: https://emudesk.com/issues/mgba-game-not-saving-save-type-fix
content_locale: en
source_locale: en
entity_type: issue
index_status: index
published_at: 2026-08-31T18:22:23.000Z
updated_at: 2026-09-01T00:45:02.756Z
freshness_status: fresh
---

# mGBA: game won't save — how to fix GBA save types and RTC

mGBA can emulate every Game Boy Advance save method — but only if the save type is set correctly for each game. A wrong setting means the game silently discards every save, or the save file exists but loads to a blank screen.

You hit one of these:


  The in-game "Save" option works but the next time you open mGBA the save is gone
  The game shows "The data could not be read" or takes you back to a new-game screen on load
  Pokémon FireRed/Emerald/Ruby/Sapphire — save works but the clock is always wrong or the Berry glitch fires
  The .sav file appears on disk but mGBA ignores it or loads blank data
  Saving works in one session but vanishes after you close and reopen the emulator


Why this happens: Original GBA cartridges used four different save hardware types (SRAM, Flash 64K, Flash 128K, EEPROM 512B/8KB). mGBA defaults to automatic detection, which works for most games but occasionally guesses wrong — especially on licensed re-releases, ROM hacks, or less-common titles. When the detected type doesn't match what the game writes, bytes go to the wrong addresses and the save corrupts or disappears. Real-time clock (RTC) games like Pokémon Ruby/Sapphire/Emerald add a second layer: the clock must also be set once inside the emulator or time-dependent events break.

Re-test after completing each step.