Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a workstation running Win2008 that's logged in an AD domain and I have a dual boot with Ubuntu Linux. When running Linux, I'd like to be able to use the same Thunderbird profile I use under Windows, so I pointed Thunderbird to use a profile I found under:


Turns out it was not the correct profile -- it had the right configuration, but the Inbox was an old version. I eventually found out the correct path was:


What's the rationale behind those different places to store application data?

share|improve this question
up vote 107 down vote accepted

Roaming is the folder that would be synchronized with a server if you logged into a domain with a roaming profile (enabling you to log into any computer in a domain and access your favorites, documents, etc. Firefox stores its information here, so you could even have the same bookmarks between computers with a roaming profile.

Local is the folder that is specific to that computer - any information here would not be synchronized with a server. This folder is equivalent in XP to C:\Documents and Settings\User\Local Settings\Application Data.

LocalLow is the same folder as local, but has a lower integrity level. IE8, for example, can only write to the locallow folder (when protected mode is on).

This document from Microsoft (downloads a .doc file) has a long explanation for what these three folder areas are and how they are used, as well as the changes implemented between XP and Vista (Windows 7 retains the Vista structure).

It is one of a series of documents in the Windows Vista Step-By-Step Guides for IT Professionals.

share|improve this answer
As for Thunderbird, the TB profile should actually live in Roaming but the cache of downloaded mails, at least for IMAP accounts definitely should be elsewhere. If I were in a domain here, there'd be a lot of copying going on on each logon/-off with 1+ GiB of mails. – Joey Aug 11 '09 at 21:56
Yeah, that would be bad - especially if the roaming profile was trying to sync on a slow connection! – Jared Harley Aug 11 '09 at 22:17
I guess the choice of Local* bs Roaming is the app developer's choice? – Howiecamp Dec 28 '09 at 0:08
This link from Microsoft (same as above, but not a doc) has a good explanation of folders, what is used where, and relationship to folders in XP. – mindless.panda Aug 24 '11 at 14:33
@Howiecamp, yes, this link details the SpecialFolders enumeration for .NET 4.0. Developers choose which folder to save data to, in this case either ApplicationData or LocalApplicationData. – mindless.panda Aug 24 '11 at 14:35

Roaming. This folder (%appdata%) contains data that can move with your user profile from PC to PC—like when you’re on a domain—because this data has the ability to sync with a server. For example, if you sign in to a different PC on a domain, your web browser favorites or bookmarks will be available.

Local. This folder (%localappdata%) contains data that can't move with your user profile. This data is typically specific to a PC or too large to sync with a server. For example, web browsers usually store their temporary files here.

LocalLow. This folder (%appdata%/…/locallow) contains data that can't move, but also has a lower level of access. For example, if you're running a web browser in a protected or safe mode, the app will only be able access data from the LocalLow folder.

The apps themselves choose whether to save to the Local, LocalLow, or Roaming folders. Most desktop apps use the Roaming folder by default, while most Windows Store apps use the Local folder by default.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .