Browser game saves: What Favorites keeps and how to protect progress
By WASM Arcade Directory · Updated
A game can remain in Favorites after its progress disappears. The bookmark and the game save are different records, often managed by different websites. Before resetting anything, identify which record is missing and which service controls it.
On WASM Arcade, Favorites remembers game pages. Recently launched remembers players you opened. Neither feature stores a Minecraft world, a puzzle position, a high score or a provider account. This guide explains what those lists contain and how to avoid deleting useful data while troubleshooting an external game.
What this directory actually remembers
Favorites and recent launches are kept in this browser's local storage. They are not uploaded to a directory account or synchronized between devices. A check on October 16, 2026 confirmed the following behavior on the current site:
| Action | Result in the directory |
|---|---|
| Save Riddle School 3 to Favorites | Its page is added to the local Favorites list |
| Open its player | Its listing is added to recent launches |
| Close the player | The favorite and recent entry remain |
| Reload and open the library | The saved directory entries are read again |
| Select Clear history | Recent launches are removed; the favorite remains |
These checks establish directory behavior, not that Riddle School 3 saved a puzzle session. A recent entry is created when the player is launched. It can exist even when the game never finishes loading.
The current code keeps up to 60 distinct recent launches, newest first. Launching the same game moves its existing entry to the front. Older entries can leave that list without any game save being deleted.
Why the game uses a different storage context
A game page belongs to wasmarcade.org, while its embedded player connects to a named external provider. For example, the current Bloxorz embed is supplied by Miniplay and the Minecraft entry uses a q13x-hosted Eaglercraft player. The provider name beside the launch control identifies that connection. External players remain off until you enable them in Privacy choices; enabling a player does not synchronize or back up its saves.
Browsers separate storage by website origin, and modern privacy features can further partition or restrict embedded storage. As a result, data available inside an embedded player may differ from data available when you open the provider directly. Changing a browser privacy setting can also affect the result. This is why "the game is still on the same directory page" does not establish that its save environment is unchanged.
The directory cannot promise that an external provider offers local saves, account saves or export. Check the current game's menu and the provider's instructions for the exact version you are using.
Before closing a long session
Look for an explicit save, export, stage-code or account option before you leave. If the game offers export, save the resulting file somewhere you can find again and keep a second copy. Check that the file exists and is not empty. Do not assume an export succeeded merely because you pressed a button.
For a stage-code game such as Bloxorz, record the code shown by the game. A screenshot or note can preserve that code independently of the directory. It is a way to resume a stage, not necessarily a record of every move made within it.
If the provider advertises account-based saving, confirm that you are using the intended provider account. Logging into an unrelated service does not connect the records. Test any documented import or continuation feature before relying on it for a valuable session.
If progress appears to be missing
First return through the same game listing, browser profile and provider you used before. Check whether the player has changed hosts or versions. A similarly named game can still use a different save format or storage location. Avoid creating and saving a replacement session until you understand whether that could overwrite the old one.
Next, inspect the game's own load or continuation menu. Some titles resume automatically; others require a stage code, an import or a provider login. Follow the current instructions rather than assuming that a blank opening scene means all data has been lost.
If the problem occurs only inside the embed, record that distinction for support. Opening the provider directly may help diagnose it, but does not prove the same save will appear there. Do not clear either site's storage as a first experiment.
What clearing data can remove
Use the narrowest action that addresses the problem. Closing and reopening a player, clearing the directory's recent list, and deleting browser site data have different effects.
| Action | What to expect |
|---|---|
| Clear history inside the directory | Removes the directory's recent-launch list |
| Remove one favorite | Removes that bookmark |
| Clear wasmarcade.org site storage | Can remove directory Favorites and recent launches |
| Clear provider or all-browser site data | Can remove locally stored game data or login state, depending on the provider |
| Use another profile or private window | Uses a separate storage context; previous progress may not appear |
Browser interfaces sometimes group cookies, local storage and other site data together. Read the selected category before confirming deletion. "Clear everything" is a poor first response when the data you hope to recover may be stored locally.
Moving to another device
A directory favorite does not transfer a game save. Use the provider's documented account synchronization or export-and-import method if it offers one. Keep the original browser and exported file until the destination shows the expected progress.
Check version compatibility before importing. A world or save from one implementation may not work in another, even when both use the same game name. This directory has not verified every provider's transfer tools and cannot reconstruct a lost local save from a Favorites entry.
What to send when asking for help
Include the directory page URL, provider name, browser, device, approximate last successful session and the symptom. Say whether the favorite disappeared, the game started fresh, a load menu was empty or an import failed. These describe different problems.
Do not send passwords, authentication cookies or an entire browser profile. Use the contact page for directory-list problems; the named provider is the appropriate starting point for its game-save behavior. The privacy policy explains the separation between directory storage and external players.
References
Directory behavior was checked against the current site and its storage implementation. Browser background: MDN: localStorage and MDN: storage quotas and eviction. Provider recovery and cross-device transfer remain game-specific.