Flash Save Viewer (.sol Shared Objects)
Flash games saved progress as Local Shared Objects. Drop a .sol file to read every stored value — both the older AMF0 format and AMF3 are supported.
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.
Flash games stored their saves as Local Shared Objects — ordinary serialised data with no encryption. Both AMF0 (Flash 8 and earlier) and AMF3 (ActionScript 3) are supported, including typed objects, which are shown with their original class name. Objects a game marked as externalizable define their own private byte layout and cannot be decoded generically; those are reported rather than guessed at.
Frequently Asked Questions
Where are .sol files stored?
On Windows, %AppData%\Roaming\Macromedia\Flash Player\#SharedObjects, then a random folder name, then a folder per site or game. Flash projectors and Ruffle keep them in similar per-user locations.
What is the difference between AMF0 and AMF3?
AMF0 came with ActionScript 1 and 2; AMF3 arrived with ActionScript 3 and adds reference tables so repeated strings and objects are stored once. The version is recorded in the file header and handled automatically.
Are .sol files encrypted?
No. They are plain serialised data, which is why Flash game saves were always so easy to edit. Some games obfuscated values themselves, but the container has no encryption.
It says an object is externalizable. What does that mean?
That the game's own ActionScript class controls how its bytes are written, so there is no general rule for reading it back. Rather than guess and show wrong values, the tool reports it.