Es3: Save Editor

Easy Save 3 is a popular asset for Unity developers that allows them to save and load data efficiently. Unlike saving data to a simple text file (like JSON or XML), ES3 saves data in a binary format. This makes the files smaller and faster to load, but it also makes them unreadable to humans without specific tools.

When you see a file ending in .es3 or a file that looks like scrambled gibberish when opened in Notepad, it is likely an ES3 file.

Look for tags that make sense. Common tags include: es3 save editor

The tree structure will often mirror the game’s code objects. For example, a PlayerStats tag might contain strength, agility, and intellect as child nodes.

Never use an ES3 save editor on online multiplayer games that store save data locally (rare but exists). Anti-cheat systems like Easy Anti-Cheat (EAC) or BattlEye may detect altered file hashes, resulting in a permanent ban. Easy Save 3 is a popular asset for

Safe to edit:

Not safe to edit:

Typically, ES3 saves are found in:

Look for files with extensions like .es3, .save, .txt, or no extension at all. Use a tool like Everything (voidtools) to search for files modified around your last play session. The tree structure will often mirror the game’s

This is trickier because you need the correct syntax. An ES3 editor that supports raw JSON viewing allows you to copy an existing item’s structure. For example:

"inventory": [
  "itemID": "potion_small", "quantity": 5,
  "itemID": "sword_iron", "quantity": 1
]

To add a rare sword, duplicate the sword line and change the ID to "sword_legendary".