World Library  
Flag as Inappropriate
Email this Article

Flash cookies

Article Id: WHEBN0026039931
Reproduction Date:

Title: Flash cookies  
Author: World Heritage Encyclopedia
Language: English
Subject: Google Analytics, XB Browser
Publisher: World Heritage Encyclopedia

Flash cookies

"Sol file" and ".sol file" redirect here. For mathematical data format, see Sol (format).

Local shared objects (LSOs), commonly called flash cookies (due to their similarities with HTTP cookies), are pieces of data that websites which use Adobe Flash may store on a user's computer. Local shared objects are used by all versions of Adobe Flash Player and version 6 and above of Macromedia's now-obsolete Flash Player.[1]

While websites may use local shared objects for purposes such as storing user preferences, there have been privacy concerns regarding local shared objects, and they may be considered a breach of browser security.


Local shared objects contain data stored by individual websites. With the default settings, the Flash Player does not seek the user's permission to store local shared objects on the hard disk. By default, a SWF application running in Flash Player from version 9 to 11 (as of Sept 1, 2011) may store up to 100 kB of data to user's hard drive. If the application attempts to store more data than the allotted default, the user is shown a dialog to allow or deny the request for more storage space.[2]

Adobe Flash Player does not allow 3rd-party local shared objects to be shared across domains. For example, a local shared object from "" cannot be read by the domain "".[1] However, the first party website can always pass data to a third party via some settings found in the dedicated XML file and passing the data in the request to the third party. Also, third party LSOs are allowed to store data by default.[3][4] By default LSO data is shared across browsers on the same machine. As an example:

  • A visitor accesses a site using their Firefox browser, then views a page displaying a specific product, then closes the Firefox browser, the information about that product can be stored in the LSO.
  • If that same visitor, using the same machine now opens an Internet Explorer browser and visits any page from the site viewed in Firefox, the site can read the LSO value(s) in the Internet Explorer browser, and display dynamic content or otherwise target the visitor.

This is unique from cookies which have directory isolated storage paths for saved cookies while LSOs use a common directory path for all browsers on a single machine.


Many web based Flash games use LSO files to store the user's personal game data, such as user preferences and actual game progress. Backing up files such as these requires a more technical understanding of software, and would be considered by most average users to be a difficult task. However, both browser updates and programs designed to remove unused files may delete this data.

To help combat cheating, game developers may render LSO files unusable if moved or uploaded from another location or backup. This has been criticized, however, as it may cause users to lose data despite backups.

Privacy concerns

As with HTTP cookies, local shared objects can be used by web sites to collect information on how people navigate those web sites even if people believe that they have restricted the data collection.[5] Online banks, merchants, or advertisers may use local shared objects for tracking purposes.[6]

On 10 August 2009, Wired magazine reported that more than half of the top websites used local shared objects to track users and store information about them but only four of them mentioned it in their privacy policy. "Flash cookies are relatively unknown to web users," it said, "even if a user thinks they have cleared their computer of tracking objects, they most likely have not." The article further asserts that some websites use Flash cookies as hidden backups, so that they can revive HTTP cookies when user deletes them.[7]

According to New York Times, since July 2010, there had been at least five class-action lawsuits in the United States against media companies for using local shared objects.[8]

In certain countries, it is illegal to track users without their knowledge and consent. For example, in the United Kingdom, customers must consent to use of cookies/local shared objects:[9][10]

Local shared objects were the first subject to be discussed in the Federal Trade Commission (FTC) roundtable in January 2010.[11] FTC Chairman Jon Leibowitz has been talking with Adobe about what it describes as "the Flash problem." [12]

User control

Users can disable local shared objects using the Global Storage Settings panel of the online Settings Manager at Adobe's website.[13] However, using this feature will permanently place a flash cookie on the user's computer, informing all other websites that the user does not want flash cookies stored on their computer. Users can also opt-out of them on a per-site basis by right-clicking the Flash Player and selecting "Settings" from the popup menu that will appear, or using the Website Storage Settings panel. The latter also allows users to delete local shared objects.[14]

Users may also delete local shared objects either manually or using third-party software. For instance, BetterPrivacy,[15] a Firefox add-on, or CCleaner, a standalone computer program for Microsoft Windows, allow users to delete local shared objects on demand.

Since version 10.3 of Flash, the Online Settings Manager (letting users configure privacy and security permissions via Adobe's website) is superseded by the Local Settings Manager under the Windows Control Panel, Mac OS System Preferences, Linux KDE System settings or Linux GNOME System > Preferences.[16] Users of other operating systems still use the Adobe Online Settings Manager. Since at least April 2012 (v, updating by downloading a new Flash version resets the security and privacy settings to the defaults of allowing local storage and asking for media access again, which may be against users' wishes.

Browser control

Browser control refers to the web browser's ability to delete local shared objects and to prevent the creation of persistent local shared objects when privacy mode is enabled. As for the former, Internet Explorer 8, released on March 19, 2009,[17] implements an API that allows browser extensions to co-operate with the browser and delete their persistent data stored when user issues a Delete Browsing History command.[18] However, two years passed since its introduction until Adobe, on March 7, 2011, announced that Flash Player v10.3, which was still in development at the time, supports co-operating with Internet Explorer 8 or later to delete local shared objects.[19]

Also on January 5, 2011, Adobe Systems, Google Inc., and Mozilla Foundation finalized a new browser API (dubbed NPAPI ClearSiteData). This will allow browsers implementing the API to clear local shared objects.[20] Four months later, Adobe announced that Flash Player 10.3 enables Mozilla Firefox 4 and "future releases of Apple Safari and Google Chrome" to delete local shared objects,[19] so since version 4, Firefox treats LSOs the same way as HTTP cookies - deletion rules that previously applied only to HTTP cookies now also apply to LSOs.[21][22] This caused loss of data and backward-incompatible flash application behavior[23] for those Firefox and Flash users which used HTTP cookies and Flash local shared objects for different goals. Mainly this had an impact on the flash gaming community, which relies heavily on Flash LSOs to store saved games.[24][25] The resulting support requests cannot be solved favorably for the Mozilla Firefox users without changes to the browser, because of the introduced equivalence between HTTP and flash cookies.[21][22] Currently, the workaround in use is to either configure the browser to never clear history data and cookies, or to revert the part of the changes affecting this use case, using third-party patches.[26]

As for the behavior in browser's privacy mode, Adobe Flash Player 10.1, released on June 10, 2010, supports the privacy modes of Internet Explorer, Mozilla Firefox, Google Chrome, and Safari. Local shared objects created in privacy are discarded at the end of the session. Those created in a regular session are also not accessible in privacy mode.[20][27]

File locations

The default storage location for local shared objects is operating system-dependent, and depends on the flash plugin being NPAPI or PPAPI.


On Microsoft Windows NT 5.x and 6.x, they are stored in:[28]

  •  %APPDATA%\Macromedia\Flash Player\#SharedObjects\
  •  %APPDATA%\Macromedia\Flash Player\\support\flashplayer\sys\

On Mac OS X, they are stored in:

  • ~/Library/Preferences/Macromedia/Flash Player/#SharedObjects/
  • ~/Library/Preferences/Macromedia/Flash Player/

On Linux or Unix, they are stored in:

  • ~/.macromedia/Flash_Player/#SharedObjects/
  • ~/.macromedia/Flash_Player/

For Linux and Unix systems, if the open-source Gnash plugin is being used instead of the official Adobe Flash, they will instead be found at:

  • ~/.gnash/SharedObjects/


When using Google Chrome the location for the Pepper Flash (PPAPI) storage is:

  • Windows:   %APPDATA%\..\Local Settings\Application Data\Google\Chrome\User Data\Default\Pepper Data\Shockwave Flash\WritableRoot\#SharedObjects
  • MacOS X:   ~/Library/Application Support/Google/Chrome/Default/Pepper Data/Shockwave Flash/WritableRoot/#SharedObjects/
  • Linux:       ~/.config/google-chrome/Default/Pepper Data/Shockwave Flash/WritableRoot/#SharedObjects/

Editors and toolkits

Software Developer Operating system Abilities First public release Latest stable version License
Cookie Stumbler WriteIt! Studios Ltd. Mac OS X 10.6 - 10.8 Remove 2011 Shareware
Cookie SweetP Productions Mac OS X 10.6 - 10.7 Remove 2011 3.0.14 Shareware
Safari Cookies SweetP Productions Mac OS X 10.5 - 10.7 Remove 2009-04-12 1.9.4 (2012-04-05) Freeware
BetterPrivacy Ingo Krüger Linux, BSD, Mac OS X, Windows (Firefox/SeaMonkey addon) Remove, Read AMF0 2008-08-04 1.68 (2012-01-20)  ?
Dojo Toolkit Dojo Foundation OS-Independent Write AMF0/AMF3 (in browser via Flash) 2004 1.9.0 (2013-05-01) BSD, AFL
MAXA Cookie Manager Maxa Research Windows Remove ? 5.3 (2011-12-11) Shareware
.minerva Gabriel Mariani OS-Independent (Adobe Air) Read AMF0/AMF3, Write AMF0/AMF3, AMF0/AMF3-JSON prior to 2008-07-15 (1.5.1) 3.5.0 (2012-12-13) BSD
PyAMF Nick Joyce OS-Independent Read AMF0/AMF3, Write AMF0/AMF3 2007-10-07 0.6.1 (after 2010-08-11) MIT
.sol Editor Alexis Isaac Windows Read AMF0, Write AMF0 2005-02 (2005-02-21) MPL
SOLReader Alessandro Crugnola Windows Read AMF0 2007-10-25 1.0.0 (2007-10-25) ?
FlashDevelop Alessandro Crugnola Windows Read AMF0/AMF3 2009-06-14 (3.0.0) 4.4.0 (2013-04-18) MIT
SolVE Darron Schall Windows, Mac OS X Read AMF0, Write AMF0 2004-09 0.2 (2004-10-15) CPL
s2x Aral Balkan OS-Independent AMF0-XML, XML-AMF0 2003-12 0.75 (2003-12) Freeware
Click&Clean Vlad & Serge Strukoff Linux, BSD, Mac OS X, Windows (Firefox/SeaMonkey addon) Remove 2010-01-23 ( 4.1 (2013-03-16) MIT

See also


External links

  • Adobe's online tool on its Web site to erase Flash cookies and manage Flash player settings
  • What are local shared objects?, Adobe Flash Player security and privacy help
  • How to create SharedObjects in 10 minutes
  • How to block Flash cookies
  • Electronic Privacy Information Center on "Local Shared Objects"
  • Legal action on 'zombie cookies' filed in US court
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.

Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.