How to Safely Edit Game Saves
Editing a save file can unlock creative freedom in your favorite games — but one wrong byte can mean a corrupted save and lost progress. This guide covers everything you need to know to edit safely: backups, checksums, common mistakes, and recovery strategies.
Step 1: Always Back Up First
This is the single most important rule. Before you touch any save file, make a copy. If your edit goes wrong, you can restore the original and try again. Here's a quick procedure:
- 1
Locate your save file
Use our save file locations guide to find the exact folder for your game.
- 2
Copy the entire folder
Right-click the save folder and choose Copy, then paste it somewhere safe (Desktop, a "Backups" folder, or a USB drive). Don't just copy a single file — some games spread save data across multiple files.
- 3
Name the backup clearly
Rename the copy with a date and description, such as "EldenRing_Backup_2026-03-20_BeforeEdit". This makes it easy to find if you need to restore.
- 4
Verify the backup loads
Optionally, copy your backup back to the original location and confirm the game loads it. This proves the backup is valid.
SaveEditor tip: When you open a file in SaveEditor, you'll see a backup reminder before making changes. You can also use the Export button to download the unmodified file as a backup before editing.
Understanding Checksums
Many games embed a checksum(or hash) inside the save file — a small value calculated from the file's contents. When the game loads, it recalculates the checksum and compares it to the stored value. If they don't match, the game knows the file was tampered with and may refuse to load it.
Games that use checksums include:
- Dark Souls series (.sl2 files)
- Elden Ring (BND4 container checksum)
- Monster Hunter World
- Borderlands series (SHA-1 hash)
- Grand Theft Auto V (custom CRC)
- Pokémon games (16-bit checksum)
If you're editing a game that uses checksums, you'll need to either recalculate the checksum after editing or use a tool that does it automatically. SaveEditor recalculates checksums for supported game formats so your edited saves load correctly.
Common Mistakes That Corrupt Saves
Editing the wrong offset in a binary file
Binary saves pack data at exact byte positions. If you change a value at the wrong offset, you'll overwrite something else entirely — player coordinates might become item IDs, or a health value might become a quest flag. Always use a structured editor or confirmed offset tables.
Changing string lengths in binary files
Many binary formats store strings as a length prefix followed by the characters. If you change "Hero" (4 bytes) to "Champion" (8 bytes) without updating the length prefix, the game reads the wrong number of bytes and every field after the string shifts — cascading corruption.
Removing required fields in JSON or XML saves
Text-based saves (Stardew Valley, Hollow Knight, Undertale) are easier to edit but still fragile. Deleting a required XML tag or JSON key will cause the parser to crash. Always keep the structure intact and only change values.
Saving with the wrong encoding
Opening a UTF-8 save in a text editor that re-saves as UTF-16 (or vice versa) can silently corrupt the file. Use a code editor like VS Code that preserves the original encoding, or edit in SaveEditor which handles encoding automatically.
Editing while the game is running
Most games write to the save file periodically. If you edit the file while the game is open, the game may overwrite your changes on the next auto-save — or worse, merge them into an inconsistent state. Always close the game first.
SaveEditor's Built-in Safety Features
Backup Warning
A reminder appears before you make any changes, prompting you to download the original file first.
Validation Checks
For supported formats, SaveEditor validates the file structure on load and flags any anomalies before you start editing.
Value Range Warnings
When you enter a value outside a field's normal range (e.g., 999999999 gold), SaveEditor warns you that the game may not handle it correctly.
Hex View + Data Inspector
For binary files, the hex view shows your changes in context. The Data Inspector helps you verify you're editing the correct data type and offset.
Version Compatibility
Game updates frequently change save file formats. A save edited on version 1.04 may not load on version 1.06 if the developers added new fields or changed the file layout. Best practices:
- Edit saves that match your current game version.
- If a major patch drops, test your edited save immediately — don't wait days to discover it's broken.
- Keep backups of saves from each major version so you can roll back if needed.
- Check community forums or patch notes for save format changes before updating.
Online Play & Anti-Cheat Warnings
Using edited saves in online multiplayer can result in permanent bans. Anti-cheat systems actively scan for modified game data:
- Easy Anti-Cheat (EAC): Elden Ring, Apex Legends, Fortnite — detects modified game memory and files at runtime.
- Valve Anti-Cheat (VAC): CS2, Team Fortress 2 — monitors for code injection and file tampering. Bans are permanent and account-wide.
- Game-specific server validation: Dark Souls 3, GTA Online — the server validates your stats and items. Impossible values trigger soft-bans or account flags.
Our recommendation: Only use edited saves in offline or single-player mode. If a game has both online and offline modes (like Elden Ring), play offline while using a modified save. Never take edited saves into ranked or competitive modes.
Recovery Strategies
If an edited save won't load, don't panic. Try these steps in order:
- 1
Restore your backup
If you followed Step 1, copy your backup over the corrupted file and you're back in business.
- 2
Check for .bak files
Many games (Terraria, Skyrim, Stardew Valley) automatically create .bak backups alongside saves. Rename the .bak to the original filename and try loading.
- 3
Use Steam Cloud
If Steam Cloud is enabled, your pre-edit save may still be on Valve's servers. Delete the local save, then launch the game — Steam will re-download the cloud version. Choose "Download from Steam Cloud" when prompted.
- 4
Binary diff your changes
Open both the working backup and the broken edit in a hex editor side-by-side. Compare byte-by-byte to find exactly what changed. Tools like HxD (Windows) or hexdump with diff (Linux) can highlight differences.
- 5
Ask the community
Game-specific modding communities (Nexus Mods forums, r/saveediting, game-specific Discord servers) are often helpful. Share the error message and someone may have seen it before.
Edit Saves the Safe Way
SaveEditor is built with safety in mind — backup reminders, validation, value range checks, and automatic checksum recalculation for supported formats.
Open SaveEditor