Long before a Flash game could ask you to sign in, or sync your progress to a server somewhere, it still needed some way to remember you the next time you opened it. High scores, unlocked levels, saved character builds — none of that data disappeared between sessions, and the mechanism responsible was a piece of Flash Player itself that most players never knowingly encountered: the Local Shared Object.
A Cookie by Another Name, Built to Hold More
Local Shared Objects, often nicknamed "Flash cookies" for the role they played, worked much like the browser cookies web developers had used for years, but were managed entirely by the Flash Player plugin rather than the browser itself. Unlike a standard cookie's tiny handful of kilobytes, an LSO could store up to 100 kilobytes of data by default without even prompting the user — plenty of room for a full save file's worth of level progress, inventory state, or settings a player had fine-tuned over dozens of sessions.
Stored Outside the Browser's Normal Reach
Because Local Shared Objects lived in a Flash Player-managed folder on the user's hard drive rather than inside the browser's own cookie storage, clearing your browser history, cookies, or cache in the ordinary way did nothing to remove them. A player who wiped their browser data expecting a clean slate would often relaunch a favorite Flash game only to find their old save file waiting exactly as they'd left it — a persistence quirk that developers relied on and casual privacy-conscious users found genuinely surprising.
The Privacy Backlash That Followed
That same persistence eventually drew scrutiny once researchers and journalists started publicizing it in the late 2000s, framing Flash cookies as a way for sites to track users even after they'd deliberately tried to opt out through their browser settings. Some advertising networks were shown to be using LSOs specifically to "respawn" regular browser cookies that users had deleted, a practice that drew lawsuits and eventually forced Adobe to add a dedicated Flash Player Settings Manager panel letting users manage and clear LSOs directly.
What Ordinary Games Actually Used Them For
Away from the advertising controversy, the vast majority of Flash games used Local Shared Objects for exactly the mundane purpose they were designed for: remembering a player's high score table, which levels had been unlocked, whether a tutorial had already been shown, or how far into a long RPG like Sonny or Mardek someone had progressed. For genres like tower defense and idle games, where session-to-session progress was the entire point, LSOs were the quiet infrastructure making persistent play possible at all without any server or account system.
An Ending That Arrived Alongside Flash's Own
When Flash Player itself reached end-of-life in December 2020, every save file stored as a Local Shared Object became inaccessible along with it, unless a player had specifically preserved their old Flash Player data folder. Modern emulation projects generally can't recover those original save files at all, which means restarting a beloved Flash RPG or tower defense game today usually means starting completely from zero — one of the quieter, less-discussed forms of data loss that came with the format's disappearance.