Profile folder - Firefox: Difference between revisions

From MozillaZine Knowledge Base
Jump to navigationJump to search
Line 83: Line 83:
|-
|-
| Cache  
| Cache  
| Previous to 1.5
|  
| Contains cached Internet files.  In 1.5 and above, only profiles in custom locations include the Cache folder.  Use [[About_protocol_links |about:cache]] to find the  location.  See [[browser.cache.disk.parent directory]].
| Contains cached Internet files.  On Windows, in 1.5 and above, only profiles in custom locations include the Cache folder.  Use [[About_protocol_links |about:cache]] to find the  location.  See [[browser.cache.disk.parent directory]].
|-
|-
| OfflineCache
| OfflineCache
|
| 2.0 and above
|
| On Windows, only profiles in custom locations include the OfflineCache folder.
|-
|-
|[[chrome folder|chrome]]   
|[[chrome folder|chrome]]   

Revision as of 12:13, 16 March 2008

This article is about Firefox's profile folder. See also Profile folder - Thunderbird and Profile folder - SeaMonkey.

Firefox stores a user's personal information such as bookmarks, extensions, and user preferences in a unique profile. The first time you start Firefox, it will automatically create a default profile; additional profiles can be created using the Profile Manager. The settings which form a profile are stored in files within a special folder on your computer — this is the profile folder.

Finding the profile folder

Profile folders are placed in the same area by default but are named randomly for additional security. If you chose a custom location, see Other methods of finding a profile below.

The installation directory includes a folder named "profile" (for example, C:\Program Files\Mozilla Firefox\defaults\profile on Windows), but this folder contains program defaults, not your user profile data. On Windows 2000/XP/Vista and on Linux, the folder containing your user profile data is hidden by default and you will need to show hidden files and folders to navigate to the profile folder.

Windows 95, 98, and ME

Profile folders are in one of these locations:

  • C:\Windows\Application Data\Mozilla\Firefox\Profiles\<profile folder>
  • C:\Windows\Profiles\<Windows login/user name>\Application Data\Mozilla\Firefox\Profiles\<profile folder> .

Windows 2000 and XP

  1. Choose Start → Run
  2. Type in %APPDATA%
  3. Press OK. A Windows Explorer window will appear.
  4. In the Windows Explorer window, choose Mozilla → Firefox → Profiles. Each folder in this folder is a profile on your computer.

You can also navigate directly to your folder at the following path:

  • C:\Documents and Settings\<Windows login/user name>\Application Data\Mozilla\Firefox\Profiles\<profile folder>

The Application Data folder is a hidden folder; to show hidden folders, open Windows Explorer and choose "Tools → Folder Options → View (tab) → Show hidden files and folders".

Windows Vista

  1. Click the Start button on the Windows taskbar to open the Windows Start menu.
  2. Type in %APPDATA% in the "Start Search" box.
  3. Click the "Roaming" item that appears on the menu.
  4. In the Windows Explorer window that opens, choose Mozilla → Firefox → Profiles. Each folder in this folder is a profile on your computer.

You can also navigate directly to your profile folder at the following path:

  • C:\Users\<Windows login/user name>\AppData\Roaming\Mozilla\Firefox\Profiles\<profile folder>.

The AppData folder is folder is a hidden folder; to show hidden folders, open a Windows Explorer window and choose "Organize → Folder and Search Options → Folder Options → View (tab) → Show hidden files and folders".

Linux and Unix

Profile folders are located here:

  • ~/.mozilla/firefox/<profile folder>

The ".mozilla" folder is a hidden folder. See this article for more information. To show hidden files in Nautilus (Gnome desktop's default file browser), choose "View -> Show Hidden Files".

Mac

Profile folders are in one of these locations:

  • ~/Library/Mozilla/Firefox/Profiles/<profile folder>
  • ~/Library/Application Support/Firefox/Profiles/<profile folder>

The tilde character (~) refers to the current user's Home folder, so ~/Library is the /Macintosh HD/Users/<username>/Library folder.

Other methods of finding a profile

File search

Specific files in profiles can be found by using the file and folder search feature of your operating system. This is also useful for finding profile folders that are not in the default location. In Windows 2000 and later, you must ensure that you're including hidden files and folders in the search, as detailed in this article.

Using the JavaScript or Error Console

You can use the following technique to find the location of the profile that you are currently using. This is useful, for example, if you are using a profile that is not in the default location.

From the Firefox menu bar, choose "Tools -> Error Console" (Firefox 2) or "Tools -> JavaScript Console" (Firefox 1.5). Copy the following code. It is one very long line ending in path—make sure that you get all of it:

Components.classes["@mozilla.org/file/directory_service;1"].getService( Components.interfaces.nsIProperties).get("ProfD", Components.interfaces.nsIFile).path

In the Error Console or JavaScript Console window, paste the code in the field near the top. Click the Evaluate button. The console should display the location of the profile that is currently in use. If you don't see it, make sure you have the "All" button pushed.

Managing profiles

You can select a profile to use, create a new profile, and delete or rename an existing profile using the Profile Manager. Profiles can become corrupted, in which case you need to create a new profile then transfer your data and settings to the new profile. To safeguard your important data you should make a backup copy of up your profile.

It is possible to change the location of the Firefox profile folder but you should read this article for instructions. If you delete, rename or move the profile folder, Firefox may report that it is "already running, but is not responding" when you next start the application (bug 278860). See this article for more information.

Files and folders in the profile

None of these files should be write-protected ("read-only" or "locked"), which might be a side effect of backing up the profile to removable media and then restoring your profile from that media. Having read-only or locked files in the profile can result in serious profile issues, as described in this article.

It's not recommended to edit these files directly. Instead, use their respective interfaces. The three files whose names begin with "user" are exceptions to this—they are designed to be edited directly. For more information on these three files, follow their links in the tables below.

Folders

Name Version Description
bookmarkbackups 1.5 and above Daily rotating backups of your bookmarks.
Cache Contains cached Internet files. On Windows, in 1.5 and above, only profiles in custom locations include the Cache folder. Use about:cache to find the location. See browser.cache.disk.parent directory.
OfflineCache 2.0 and above On Windows, only profiles in custom locations include the OfflineCache folder.
chrome Contains userChrome.css and userContent.css.
extensions Installed extensions
microsummary-generators 2.0 and above Regularly-updated succinct compilations of the most important information on web pages.
minidumps ?
searchplugins 1.5 and above Contains search engine plugins and their icons for the Search Bar

Files

Name Version Description
.autoreg Temporary empty file that signals a change in the installed extensions.
.parentlock (Mac OS X) See parent.lock
blocklist.xml 2.0 and above Automatically downloaded list of dangerous extensions.
bookmarks.bak Previous to 3.0 Backup of bookmarks.html [1]
bookmarks.html Previous to 3.0 Bookmarks
bookmarks.html.moztmp Temporary bookmarks file. If found, remove the 'read-only' attribute, as it results in creation of multiple numbered bookmarks-n.html files. [2]
bookmarks.postplaces.html 3.0 and above Backup of bookmarks stored in "places.sqlite", created when you exit Firefox. [3] [4]
bookmarks-(date).html in bookmarkbackups 1.5 and above Daily rotating backups of your bookmarks.
bookmarks-(date).json in bookmarkbackups 3.0 and above Daily rotating backups of your bookmarks.
cert8.db Security certificates
compatibility.ini Stores version and path of the application this profile was last used with. When the profile is loaded with an application of a different version/path, the XPCOM components registration process is triggered. This file is automatically generated and can safely be deleted.
components.ini Previous to 1.5 Lists extension folders with XPCOM components. Replaced with extensions.ini in 1.5.
compreg.dat Lists registered XPCOM components. Automatically regenerated whenever XPCOM registration process is triggered.
content-prefs.sqlite 3.0 and above Individual settings for pages.
cookies.sqlite 3.0 and above Cookies [5]
cookies.txt Previous to 3.0 Cookies
cookies.txt.moztmp Temporary cookies file. If found, remove the 'read-only' attribute or delete the file, as it results in multiple numbered cookies-n.txt files. [6]
defaults.ini Previous to 1.5 Lists extension folders with default pref files. Replaced with extensions.ini in 1.5.
downloads.rdf Previous to 3.0 Download history. Can be deleted to resolve slow downloads or hangs. [7]
downloads.sqlite 3.0 and above Download history [8]
extensions.cache 1.5 and above Lists installed extensions, their IDs, and the folders they are installed to, along with their last-modify time. It is used, for example, to register extensions installed by dropping a folder into one of known install locations. This file is automatically regenerated and can be deleted to resolve various issues.
extensions.ini 1.5 and above Lists folders of installed extensions and themes. The file is automatically generated by nsExtensionManager and is used by low-level code to detect chrome packages and XPCOM components provided by installed addons. Can be deleted to resolve various issues.
extensions.rdf Installed extension information. Can be deleted to remove "ghost" entries from the extension list [9] and to resolve various other issues.
extensions-startup.manifest 1.5 alphas This file was used in Deer Park alphas and was later renamed to extensions.cache [10]
formhistory.dat Previous to 3.0 Saved form data
formhistory.sqlite 3.0 and above Saved form data
history.dat Previous to 3.0 Browsing history. Can be deleted to resolve various issues.
hostperm.1 Previous to 3.0 Per-site preferences for allowing cookies and popups.
key3.db Key database
kf.txt 2.0 Key database for phishing protection.
localstore.rdf Toolbar and window size/position settings. Can be deleted to resolve various issues. See Corrupt localstore.rdf.
localstore-safe.rdf 1.5 and above Special version of localstore.rdf used in Safe Mode to set toolbars and window customizations to defaults. [11]
lock (Linux) See parent.lock
mimeTypes.rdf Action to perform when downloading certain types of files. Can be deleted to reset download actions.
parent.lock (Windows) Marker showing that the current profile is in use. Can be deleted to unlock the profile.
permissions.sqlite 3.0 and above ?
persdict.dat Personal spelling dictionary.
places.sqlite 3.0 and above Bookmarks and browsing history [12]
places.sqlite-journal 3.0 and above ?
places.sqlite-stmtjrnl 3.0 and above ?
pluginreg.dat 3.0 and above Registration of plugin MIME types. Previous to 3.0, pluginreg.dat was located in the "Firefox" folder containing the profiles.
prefs.js All preferences. See: about:config
search.rdf Previous to 2.0 Information about your search plug-ins
search.sqlite 2.0 and above Information about your search plug-ins
secmod.db Security module database
sessionstore.js 2.0 and above Stored sessions
signons.txt Previous to 1.5.0.10
2.x previous to 2.0.0.2
Encrypted saved passwords, requires key3.db to work
signons2.txt 1.5.x after 1.5.0.10
2.0.0.2 and above
Encrypted saved passwords, requires key3.db to work [13]
signons3.txt 3.0 and above Encrypted saved passwords, requires key3.db to work
urlclassifier.sqlite or urlclassifier2.sqlite or urlclassifier3.sqlite 2.0 and above Phishing protection data.
urlclassifierkey3.txt 3.0 and above
user.js
(does not exist by default)
User-set overriding preferences
userChrome.css in chrome
(does not exist by default)
User-set CSS to change the way the application looks
userContent.css in chrome
(does not exist by default)
User-set CSS to change the way webpages look
userChrome.js in chrome
(does not exist by default)
User-set JavaScript to change the way the application works
webappsstore.sqlite 2.0 and above DOM storage
xpti.dat Lists registered XPCOM interfaces. Automatically regenerated whenever XPCOM registration process is triggered.
xul.mfasl (Linux) See XUL.mfl
XPC.mfl ?
XUL.mfl (Windows) Previous to 1.5 Cached user interface data. Can be deleted to resolve various issues. Located in the profile folder prior to Firefox 1.5. In 1.5 and above, only profiles in custom locations contain XUL.mfl. See Cache folder for file location. [14]
XUL FastLoad File (Mac OS X) See XUL.mfl

Files without specific names

Name Version Description
*.src in searchplugins Search engine plugins for the Search Bar

Files outside the profiles folder

Name Version Description
pluginreg.dat Previous to 3.0 Registration of plugin MIME types. Located in the "Firefox" folder containing the profiles. In 3.0 and above, pluginreg.dat is located in the profile folder.
profiles.ini Keeps track of profile location. Located in the "Firefox" folder containing the profiles. Can be edited to point to a moved profile folder. If deleted, profiles.ini will be regenerated along with a new default profile folder upon program restart.
registry.dat ? Kept track of profile location in early Firefox versions (no longer used). Located in the "Firefox" folder containing the profiles.

External links