What is the SAV file format?
The .sav file format is used to store computer game progress data. This type of file contains information regarding the state of the game, such as in-game progress, configuration settings, and best results. A .sav file enables the user to resume a game from a save point.
Each .sav file stores data specific to a single game, and the file structure and content can vary significantly between different titles despite sharing the same extension. Because of this, each game can only open a .sav file it created - .sav files are not cross-compatible with other game titles.
Beyond standalone games, .sav is also widely used by console emulators. Applications such as Dolphin Emulator (GameCube/Wii), mGBA and no$gba (Game Boy Advance) store cartridge SRAM dumps as .sav files. In this context the file content mirrors the save-memory layout of the original hardware chip, meaning a .sav produced by one emulator may not load correctly in another.
There is no universal file signature or header - because every game defines its own internal layout, .sav files cannot be reliably identified by magic bytes alone. The MIME type defaults to application/octet-stream. Related extensions used for game saves include .srm, .dat, .state, and .save.
Security & safety
RISK: MEDIUMOpening a save in its own game/emulator is safe. The real risks are with DOWNLOADED game saves: a 'modded' or '100% complete' .sav from a random site can be crafted to corrupt your profile, trigger bans in online games, or (rarely, via malformed data) exploit the game - back up your own save first and only use saves from trusted communities. Editing a save with a save editor can also corrupt it; keep a copy.
Format details
in a nutshell- SPSS / PSPP Statistics Data File - IBM SPSS (and the free PSPP) save datasets as a binary .sav that begins with the text marker '$FL2'; opened in SPSS/PSPP/R/Python, unrelated to game saves.
Programs that open SAV files
Technical details
deep spec| Format type | Per-game save state - binary in most cases, occasionally plain text or XML |
| Developer | No single developer - format is defined independently by each game or emulator |
| MIME type | application/octet-stream |
| File signature | None universal - each game uses its own internal layout; no standard magic bytes exist |
| Encoding | Raw binary memory dump (most common); some titles use JSON, XML, or proprietary text |
| File size | Typically 1 KB - a few MB; cartridge SRAM saves are often exactly 32 KB or 64 KB |
| Compression | Varies - some games compress save data internally; many write raw uncompressed data |
| Encryption | Some commercial titles encrypt save files to prevent tampering or cheating |
| Integrity check | Many games embed a CRC-16, CRC-32, or proprietary checksum to detect save corruption |
| Cross-compatibility | Title-specific - a .sav from one game cannot be opened by a different game |
| Emulator use | Stores cartridge SRAM/EEPROM/Flash dumps for GBA, GBC, SNES, NDS, and PS1 emulators |
| Endianness | Hardware-dependent - GBA saves are little-endian; GameCube/Wii saves are big-endian |
| Typical contents | Player position, inventory, progress flags, unlocks, high scores, and game settings |
| Platform scope | PC games and console emulators (GBA, GameCube, Wii, NDS, SNES, PlayStation) |
| Related extensions | .srm, .dat, .state, .save, .ss0 |
| Released | Decades old; no common origin - each title/emulator adopted .sav independently |
SAV conversions
Community Q&A
asked by usersNo questions yet - be the first to ask about SAV files.