Ruffle flash game save data loss: browser cache settings

The trouble starts when your progress disappears after a browser cleanup, a private browsing session, or a setting that quietly deletes site data every time you close the window.

This is the confusing part of Ruffle Flash game save data loss: your .sol files usually are not sitting in the browser cache. In a normal web session, Ruffle stores Flash Local Shared Objects in the browser’s Local Storage. That means a cache cleanup may leave your game progress untouched, while clearing cookies and other site data can erase it permanently.

I have found that the safest way to think about Ruffle saves is simple: treat them like small browser-based save slots, not like downloaded files. Once you know which browser setting controls them, protecting your progress becomes much more manageable.

How Ruffle Handles Flash Game Save Data

Older Flash games commonly saved progress through Local Shared Objects, usually called LSOs or .sol files. These worked much like browser cookies, although the data format and the way games used it were specific to Flash Player. A game could store unlocked levels, high scores, settings, inventory, or a full campaign state inside one of these objects.

Ruffle emulates that behavior rather than writing a traditional .sol file directly to your physical hard drive. When you play a Flash game in a browser, Ruffle encodes the save data and stores it in the browser’s Local Storage. The original Flash data uses the Action Message Format, including AMF0 and AMF3 structures, while Ruffle keeps the stored representation as base64-encoded text.

You do not need to decode any of that to play. The practical detail is where the data lives:

• Ruffle’s browser version stores game saves in Local Storage.
• The save belongs to the site and browser profile where you played.
• Clearing that site’s stored data can remove the save.
• A normal temporary-cache cleanup generally does not remove Local Storage.
• Private browsing sessions may discard the data when the session ends.
• A browser configured to delete site data on close can wipe progress every time.

Ruffle also takes steps to prevent one game from accidentally reading another game’s save. Local Storage keys are scoped with a prefix based on the SWF file’s URL. This is useful when several SWF files run on the same domain, because their save entries need separate spaces.

There is an important consequence, though. The save is tied not only to the game but also to the way that game is hosted. If the same SWF is moved to another domain, placed at a different URL, or loaded through a different wrapper, Ruffle may not see the old save automatically. Your browser may still contain the original data, but the new page is looking in a different storage context.

Ruffle saves behave more like website data than downloaded files. If you protect the site’s stored data, you protect the progress.

Why Local Storage is easy to overlook

Browsers group several different types of information under broad labels such as “site data,” “cookies,” “cached files,” and “offline data.” Those labels are useful for general browsing, but they are not always clear enough for old Flash games.

A browser cache normally holds temporary resources: images, scripts, stylesheets, and other files that help a page load faster next time. Local Storage is persistent data created by the site or application. Ruffle uses that persistent area for the encoded save information.

This is why pressing a browser option labeled “clear cached images and files” does not normally delete Ruffle progress. The save is not simply another cached game asset. The dangerous option is the one that removes cookies, site data, or offline website data.

The wording changes from browser to browser, but the pattern is consistent. Look for controls referring to:

• Cookies and other site data
• Site data
• Offline website data
• Stored data for a specific site
• Automatically deleting data when all browser windows close

If a cleanup tool offers one broad button for “all browsing data,” slow down before using it. A general cleanup can include the storage area where Ruffle keeps its .sol data.

Why Your Progress Disappears

Ruffle Flash game save data loss usually comes from one of a few predictable situations. The game itself may have a saving bug, but browser storage settings are often the first place to investigate.

1. The browser deletes site data on close

Chrome and Chromium-based browsers can be configured to delete data that sites have saved whenever all browser windows are closed. Microsoft Edge has a similar type of setting under its “clear browsing data on close” options.

If this setting includes cookies or site data, Ruffle starts each new session without the Local Storage entries from the previous one. The game may look as if it has forgotten everything overnight, even though the actual cause is an automatic cleanup rule.

This setting is particularly easy to miss because it may have been enabled for privacy reasons months ago. You might also inherit it from a managed browser profile, a privacy-focused setup, or a browser extension that performs cleanup in the background.

To check:

1. Open your browser’s privacy or site-data settings.

2. Search for an option that deletes cookies or site data when the browser closes.

3. Review whether the game’s domain is included.

4. Disable the automatic deletion, or create an exception for the site hosting the Ruffle game.

5. Fully reopen the game and test a small save before committing hours to it.

The exact menu names differ between browsers and versions. The useful distinction is not the brand of browser; it is whether stored site data survives after the final window closes.

2. You cleared cookies or site data instead of only the cache

A cleanup screen may list browsing history, cookies, cached files, passwords, and site settings together. If you select cookies or site data, you may also remove Ruffle’s Local Storage entries.

This can happen after troubleshooting a website, signing out of accounts, freeing up browser storage, or following a generic “clear your cache” guide. The phrase “clear your cache” is often used casually, but the browser may offer a much broader cleanup than the phrase suggests.

For Ruffle saves, the safest approach is to clear only the category you actually need. If a page is loading old images or scripts, temporary cached files may be relevant. If the site is misbehaving because of a stale login or permission, cookies and site data may be relevant—but clearing them can also reset the game.

Before confirming a cleanup, read the individual categories. A small amount of caution here can save a complete campaign later.

3. You played in private or incognito mode

Private browsing is designed to keep session data from lingering. That is useful for shared computers, quick testing, and temporary sessions, but it is a poor fit for a game that needs to remember progress.

A Ruffle game may appear to save while the private window is open. You can even refresh the page and see the progress remain during that session. Once the private session ends, however, the browser may discard the storage created inside it.

If you want persistent saves, open the game in a normal browser window. This is also a good first test when a game seems to lose data unpredictably: play a short section in a standard session, close and reopen the browser, then see whether the save remains.

4. A privacy extension or cleaner removes Local Storage

Browser settings are not the only possible cause. Privacy extensions, automatic cleaners, security tools, and system maintenance utilities may delete site data without using the browser’s standard cleanup page.

The behavior varies by tool, so it is safer not to assume that an extension will recognize Ruffle’s save entries as game data. Ruffle stores the information as encoded values in Local Storage, and an aggressive cleaner may treat the entire domain as disposable.

If saves disappear after every cleanup routine, temporarily disable the relevant cleaner or add an exception for the game’s domain. Make one change at a time and test it with a disposable game save. That gives you a better chance of identifying the setting without risking your main progress.

5. You changed the game’s URL or hosting domain

Ruffle’s save data is associated with the web storage context of the game. Moving from one host to another can make a perfectly good save appear to vanish.

For example, you might play a game on one archive page, then open what appears to be the same title on another site. The SWF may have the same name and look identical, but the browser sees a different origin or URL. Ruffle may therefore create a fresh storage entry instead of reading the original one.

The same issue can occur when:

• A site changes from one subdomain to another.
• A game is embedded through a new page structure.
• The SWF file is moved to a different path.
• A site switches to a different Ruffle integration.
• You open a local copy instead of the hosted version.

Before concluding that the save is gone, return to the exact page and domain where you created it. Browser history can help here. If the original page still exists and its site data was not cleared, the save may still be available there.

Cache and Site Data Are Not the Same Thing

The difference between browser cache flash saves and site data is the key idea behind reliable Ruffle preservation.

A cache stores temporary copies of resources. The browser can delete them and download them again later. Local Storage is designed for persistent key-value data created by a website. Ruffle uses it to hold the encoded contents of Flash .sol files.

Here is the useful comparison:

Browser interfaces do not always expose Local Storage as a completely separate checkbox. A button labeled “cookies and other site data” may include it. A site-specific settings panel may show the storage more clearly, but the labels still vary.

You will notice the difference most clearly when testing. If you clear only cached files and the game keeps its progress, that is expected. If you remove site data and the game resets, that is also expected. The two cleanup actions are not interchangeable.

A safer way to clean the browser

When a page refuses to load correctly, start with the least destructive option:

1. Refresh the page normally.

2. Close and reopen the game tab.

3. Try a hard reload if the problem looks like a stale resource.

4. Clear only cached files if the issue appears to involve loading assets.

5. Remove site data only when you are prepared for saved settings and game progress to disappear.

6. Export the Ruffle save first whenever the game supports the Save Manager.

This order is not magic, but it reduces unnecessary damage. A browser cleanup should solve a specific problem, not become a routine reflex.

If you need to remove data for one site, prefer a site-specific control over a browser-wide reset. That lets you target a broken page without wiping every Ruffle game stored in the same browser profile.

Using the Ruffle Save Manager

Ruffle includes a Save Manager that can export and import .sol files. This is the most dependable way to protect a valuable save before clearing site data or changing browser setups.

Open the game in a normal browser window and right-click the Ruffle game canvas. Depending on the version and the page’s interface, the Ruffle context menu will include the Save Manager. From there, you can download the available save data as a .sol file or replace existing save data with an imported file.

The workflow is straightforward:

1. Load the game and allow it to create a save.

2. Right-click directly on the game canvas.

3. Open the Ruffle Save Manager.

4. Export the relevant .sol file to a safe folder.

5. Give the file a useful name that identifies the game and date.

6. Keep another copy somewhere outside the browser profile.

7. Use Import or Replace later if you need to restore the progress.

Name your backups clearly. A filename such as game-title-domain-2025-02-14.sol is much easier to identify than a generic download name after several weeks.

A backup is especially useful before:

• Clearing cookies or site data
• Reinstalling the browser
• Moving to another computer
• Switching browser profiles
• Testing a new Ruffle version
• Changing the game’s hosting setup
• Running a system cleaner
• Resetting browser privacy settings

Export the save before troubleshooting the browser. It is much easier to test settings when your best progress is safely outside the browser.

The limitation that catches people out

The Save Manager can replace existing .sol files, but it does not generally let you create a brand-new save file from scratch for a game that has never generated save data.

That means you should first launch the game and let it create its save entry. If the game has no Local Shared Object yet, there may be nothing for the manager to replace. Creating an empty file manually is not the same thing as creating the storage record the game expects.

A practical sequence is:

1. Start the game.

2. Reach the first point where it saves or change a setting that creates save data.

3. Close or pause the game.

4. Open the Save Manager.

5. Export the generated file.

Some games save only after completing a level, returning to a menu, or using a dedicated save button. If the manager shows no useful entry, play far enough to trigger the game’s own saving behavior rather than assuming Ruffle has failed.

Restoring a save

To restore a .sol file, open the same game in the same browser context where you want the data to live. Use the Save Manager to replace the existing save with the backup.

Because Ruffle scopes storage around the game’s URL, restoration works best when the imported file matches the same title and hosting arrangement. If you exported a save from one domain and import it into a completely different version of the game, the file may not behave as expected.

After importing:

1. Reload the game if the manager requests it.

2. Open the game’s load menu or continue screen.

3. Confirm that the expected level, score, or settings appear.

4. Play briefly and save again.

5. Export a fresh backup if the restored state is important.

Do not overwrite your only backup during testing. Keep the original .sol file untouched until you know that the restored version works.

Browser Steps for Protecting Ruffle Saves

The broad strategy is the same in most modern browsers, but the menu names vary. Look for privacy, security, cookies, and site-data controls rather than following a rigid set of labels.

Chrome and Chromium-based browsers

In Chrome, Brave, Vivaldi, Opera, and similar browsers, inspect both global privacy settings and the individual site’s stored data.

Check for an option that deletes site data when all windows close. If it is enabled, either turn it off or add the game’s domain to an exception list, depending on what the browser supports.

For a specific site, open the site information panel near the address bar and look for permissions or stored-data settings. You may be able to inspect or remove data for that domain. Be careful: removing the site’s data is the destructive action. The point of opening this panel is to understand what is stored and to create a targeted exception where possible.

When clearing general browsing data, leave cookies and other site data unselected if your goal is only to refresh temporary page resources.

Microsoft Edge

Edge provides controls for clearing browsing data when the browser closes. Review the categories included in that automatic cleanup. If cookies, site data, or offline website data are selected, Ruffle saves may not survive between sessions.

Edge also offers site-specific controls through the address-bar permissions panel and privacy settings. The names can shift with browser updates, so focus on the category rather than the exact menu path: you want the game’s persistent site data to remain available.

Firefox

Firefox uses its own labels and privacy model, but the same principle applies. Strict automatic deletion, private windows, and add-ons that clear cookies or site data can interfere with Ruffle saves.

If Firefox is set to delete cookies and site data when it closes, add an exception for the game’s domain if the browser allows it. Also review whether a privacy extension is clearing website storage independently of Firefox’s own controls.

Safari

Safari can be more aggressive about tracking prevention and storage behavior, especially across embedded content. If a Ruffle game runs inside an embedded frame rather than as a direct page, its storage context may not behave exactly like a standalone game page.

For persistent play, use a normal browsing window and avoid clearing website data for the host domain. If a game’s saves fail only in an embedded version, try the direct page or another supported presentation of the game. The difference may be the storage context rather than the game itself.

What to Do If the Save Is Already Gone

Recovery depends on what happened. If you only cleared temporary cached files, the save may still be present. Return to the original game page and check the load menu before changing anything else.

If you cleared cookies or site data, the browser may have permanently removed the Local Storage entries. In that case, Ruffle cannot reconstruct the old progress from the cache. Check for an exported .sol backup, a second browser profile, another computer, or a desktop Ruffle installation where you may have played the same game.

Also check whether the game was opened in a private window. If the private session has already ended, its stored data may no longer be available.

If the page moved, search your browser history for the original URL. The old save might still be associated with the original domain even if a newer copy of the game has appeared elsewhere.

Finally, consider whether the game itself ever saved. Some older Flash titles use unusual save logic, save only at specific points, or have incomplete support under emulation. If there was never a successful save event, there may be no .sol data to recover.

A careful recovery attempt looks like this:

1. Reopen the exact original game page.

2. Use the normal browser window, not a private session.

3. Check the game’s load or continue screen.

4. Open the Ruffle Save Manager and inspect available entries.

5. Search your downloads and backup folders for exported .sol files.

6. Avoid clearing more browser data while investigating.

7. If the save is missing, test a fresh save and export it immediately.

This process separates a missing save from a game that never wrote one in the first place.

Desktop Ruffle vs. Browser Emulation

The Ruffle save file location depends on how you run Ruffle.

In the browser, save data lives inside the browser profile’s Local Storage. You generally should not expect to find a neat folder of .sol files on the desktop. The browser may store Local Storage internally using formats such as SQLite or LevelDB, but manually browsing those files is not the practical route for routine backups. The encoded values may also be difficult to identify safely.

The desktop version is different. Desktop Ruffle stores its data directly on the local disk. Common locations include:

• Windows: C:\Users\<username>\AppData\Local\Ruffle
• macOS: ~/Library/Application Support/ruffle
• Linux: ~/.local/share/ruffle

These paths are useful when you need to understand why a desktop installation keeps saves after browser cleanup. The desktop application is not relying on the browser’s Local Storage, so deleting Chrome or Edge site data does not normally remove those desktop saves.

That separation can work in your favor, but do not assume the two environments share progress automatically. A browser save and a desktop save may be stored independently, and the game may identify its data through different application contexts.

Running SWF files locally

Opening an SWF directly through a file:// URL is another common source of confusion. When Ruffle runs this way in a browser, security and cross-origin restrictions can prevent it from accessing Local Storage as it would on a normal web page. The result may be a game that plays correctly but cannot retain progress reliably.

If you are testing a local SWF collection, use a local web server rather than opening the file directly from the filesystem. The exact server setup depends on your operating system and tools, but the important point is that the game should load through a local HTTP address instead of a file:// path.

This gives the browser a consistent origin and gives Ruffle a storage context in which saving can work. It also makes local testing closer to the way a hosted Ruffle page operates.

A Reliable Routine for Long Retro Games

For a short arcade title, losing a score may be annoying. For a campaign game with unlocks and upgrades, it can erase an entire evening. I use a simple routine for anything that has a meaningful progression loop.

First, play in a normal browser window. Next, confirm that the game actually saves by closing and reopening the tab. Once the save works, export a .sol backup through the Ruffle Save Manager.

Keep that backup outside the browser. A downloads folder is better than nothing, but a second copy on another drive or cloud folder is safer. Do not rely on the browser profile as your only backup, because browser resets and site-data cleanup can remove it without much warning.

When returning to the game, use the same domain and, where possible, the same page. If a site presents several versions of the title, avoid switching between them until you understand whether they share the same save context.

You will notice that this routine takes less than a minute, while recovering a lost campaign may be impossible. That is a good trade for games whose original Flash-era save systems were never designed for modern browser cleanup tools.

Final Takeaway

Ruffle Flash game save data loss is usually not caused by the ordinary cache people mean when they say “clear the cache.” The bigger risks are clearing cookies and site data, enabling automatic deletion on browser close, using private browsing, running privacy cleaners, or opening the same game from a different storage context.

The most dependable protection is equally straightforward: play in a normal browser window, keep the game’s site data intact, return to the same host, and export .sol files with Ruffle’s Save Manager before making major browser changes.

For desktop Ruffle, remember that saves live in application folders rather than browser Local Storage. For local SWF testing, use a local web server instead of relying on a direct file:// launch. And before trusting a long retro campaign to any emulator, make one test save, close the game, reopen it, and create a backup.

That small habit turns Ruffle from a fragile trip into the past into a much more dependable way to preserve classic browser games.