Extract Strings from a Binary File
Scan any binary file for runs of readable text. Even in an opaque save format this usually exposes field names, item IDs and player names.
Intended for your own single-player save files. Editing saves in multiplayer or online games breaks their terms of service and can get your account banned. Always keep a backup of the original file before you change anything.
Works like the Unix strings command: it scans for runs of printable characters and ignores everything else. Even in a binary save this usually reveals field names, item IDs and player names — which tells you what the format stores and roughly where. Switch to UTF-16 for files written by .NET or Unity games on Windows, where text is stored two bytes per character.
Frequently Asked Questions
What is this useful for?
Working out what an unknown format stores. Field names like playerGold or questComplete tell you the structure, and their byte offsets tell you roughly where the values sit. It is normally the first thing to try after the File Inspector.
When should I use UTF-16?
For files written by .NET or by Unity games on Windows, where text is stored two bytes per character. In ASCII mode those strings appear as single letters separated by dots; switching to UTF-16 reads them properly.
Why do I get so much noise?
Because random binary data occasionally produces printable byte runs by chance. Raise the minimum length — going from 4 to 8 characters typically removes most false positives while keeping genuine field names.
It found nothing at all. What does that mean?
That the file is compressed or encrypted. Both destroy the byte patterns that make text recognisable. Decompress or decrypt first, then run the strings scan on the result.