Chrome Profile Location: Free Browser File Finder

How to Find Your Chrome Profile Location

1. Check what the tool detected

   The card above shows your browser and operating system. If it guessed wrong, or you need the paths for another computer, change the Browser and System pickers.

2. Pick the profile and install type

   Chromium browsers name the first profile Default and later ones Profile 1, Profile 2 and so on. On Linux, choose Snap or Flatpak if you installed the browser that way, because those builds keep their files somewhere else.

3. Confirm the exact path in the browser

   Type the address shown in the card, such as chrome://version, into the address bar and read the Profile Path line. That is the folder in use right now, including custom locations set by an administrator or a command-line flag.

4. Copy the path you need

   Press Copy next to a file. On Windows, paste it into the File Explorer address bar or the Run box (Windows key + R). On a Mac, press Command-Shift-G in Finder and paste. On Linux, paste it into your file manager’s location bar or a terminal.

5. Close the browser before touching the files

   Quit the browser completely before you copy, replace or delete anything in the profile, so it can’t overwrite your change or leave a half-written file behind.

How This Tool Works and What It Can’t See

The page reads the user-agent details your browser already sends to every website to guess the browser and operating system. On Chromium browsers it also asks for User-Agent Client Hints to tell Windows 10 from Windows 11. Everything happens on this page and nothing is sent anywhere.

A website can’t look inside your disk, so the tool can’t see your user name, which profiles exist or whether you moved the folder. It shows the default location for each browser, built from environment variables such as %LOCALAPPDATA% on Windows and ~ (your home folder) on macOS and Linux.

Web pages also aren’t allowed to open chrome://, edge:// or about: pages, which is why the tool shows those addresses for you to type or paste rather than as links.

What Is the Chrome User Data Folder?

Chrome, Edge, Brave, Opera, Vivaldi, Arc and Chromium all store their data in the same way, because they share the Chromium code. There are two levels. The user data folder (called User Data on Windows) holds everything the browser has on this computer. Inside it, each profile gets its own profile folder. Your first profile is called Default. When you add a person in the profile menu, Chrome creates Profile 1, then Profile 2, and so on.

Files at the top of the user data folder are shared by all profiles. The most important one is Local State, a JSON file that lists your profiles, their display names and some browser-wide settings. On Windows it also holds the key Chrome uses to encrypt saved passwords. Everything personal, such as bookmarks, history, open tabs, extensions and saved passwords, sits inside the profile folder.

Firefox uses the same two-level idea with different names. A Profiles folder holds one folder per profile, named with eight random characters and a label such as a1b2c3d4.default-release. The file profiles.ini, one level up, lists them. Safari is the odd one out: it has one set of data per macOS user, split between ~/Library/Safari and its sandbox container, ~/Library/Containers/com.apple.Safari.

Opera’s opera://about page lists both the profile and the cache folder. Firefox’s about:profiles page shows every profile’s Root Directory and its Local Directory, which is where the cache lives.

Chrome Profile Location on Windows, macOS and Linux

These are the default profile folders for the first profile (Default) of each browser. Replace Default with Profile 1, Profile 2 and so on for other profiles. Chrome Beta, Dev and Canary use separate folders (Canary’s is Chrome SxS on Windows).

Opera keeps its data in the roaming AppData folder (%APPDATA%), while Chrome, Edge, Brave and Vivaldi use the local one (%LOCALAPPDATA%). Older Opera profiles that were migrated to the current layout may still have copies of files in the root of Opera Stable; the files Opera uses are in Default.

What Each File Does and When You Need It

Most people open the profile folder for one of a handful of reasons. Here is what the main files are, in Chromium browsers, and when each one matters.

Login Data, logins.json and key4.db give access to your saved passwords to anyone who can also decrypt them on your account. Never attach them to a support ticket, upload them to a website or leave copies in a shared folder.

Where Is the Chrome Cache Location?

On Windows the Chrome cache location is inside the profile folder, in Default\Cache (with a Cache_Data folder inside). On macOS and Linux Chromium moves it out of the profile to the system cache folder, ~/Library/Caches or ~/.cache, so backup tools can skip it. Firefox does the same on every desktop system: the profile lives in one place and its cache2 folder in a separate local folder.

For Opera and Opera GX the table shows the folder that holds the cache, because the exact subfolder differs between versions. opera://about shows the full cache path. For Firefox, about:cache shows the disk cache location in use.

Chrome History Location and Bookmarks File Location in Firefox and Safari

Firefox keeps bookmarks and history together in one SQLite database, places.sqlite, rather than two files. It also keeps up to 15 dated bookmark backups in the bookmarkbackups folder by default, which is the first place to look when bookmarks vanish. Open windows and tabs are in the sessionstore-backups folder while Firefox runs, and in sessionstore.jsonlz4 after it closes. All paths below are relative to the Firefox profile folder, except the cache.

Where Does Safari Store Bookmarks, History and Tabs?

Safari only runs on macOS, and it keeps one set of data per Mac user account. Since Safari 13, when Apple sandboxed it, part of its data lives in the container at ~/Library/Containers/com.apple.Safari. Open tabs and Tab Groups are stored in an SQLite database, SafariTabs.db, in that container. Older versions used a file called LastSession.plist in ~/Library/Safari.

macOS blocks apps from reading ~/Library/Safari and the Safari container unless you allow it. To copy these files with Terminal or a backup app, add that app under System Settings, Privacy & Security, Full Disk Access. Finder can copy them without any change.

Linux Snap and Flatpak Profile Locations

On Linux the location depends on how the browser was installed. A .deb or .rpm package uses ~/.config. A Snap keeps its files under ~/snap, and a Flatpak under ~/.var/app, because each package runs in its own sandbox. Firefox 147 and later also follow the XDG Base Directory rules for new installs, putting profiles in ~/.config/mozilla/firefox and the cache in ~/.cache/mozilla. Existing profiles in ~/.mozilla/firefox are not moved.

ChromeOS keeps the browser profile in /home/chronos, which you can only browse after switching the device to developer mode. From the Files app you can reach Downloads and My files, not the profile.

Why Are the Files Locked While the Browser Is Running?

The browser keeps its databases open the whole time it runs. History, Login Data, places.sqlite and SafariTabs.db are SQLite databases, and while they’re in use recent changes may still be sitting in a separate write-ahead log (the -wal and -journal files next to them). On Windows the open files are locked, so copying gives an error. On macOS and Linux the copy works but can catch a database halfway through an update.

The session files have a second trap. Chromium browsers and Firefox rewrite them every few seconds and replace them on the next start. If you copy a file after reopening the browser, you may copy the new, empty session instead of the one you wanted to recover.

The safe order is always the same: quit the browser completely (on Windows, check that no browser process is left in Task Manager, since Chrome and Edge can keep running in the background for apps and extensions), copy the files, then open the browser again.

How to Show Hidden Folders Like AppData and ~/Library

• Windows: the AppData folder is hidden. Paste %LOCALAPPDATA% or %APPDATA% into the File Explorer address bar and press Enter, or turn on View, Show, Hidden items.
• macOS: the Library folder in your home folder is hidden. In Finder, choose Go, Go to Folder (Command-Shift-G) and paste the path, or hold Option while opening the Go menu to see Library. Command-Shift-. (period) shows all hidden files.
• Linux: folders starting with a dot, such as .config and .mozilla, are hidden. Press Ctrl+H in most file managers, or use ls -a in a terminal.
• ChromeOS: the profile isn’t visible in the Files app. Use chrome://version to see the path, and the browser’s own export features to get data out.

How to Back Up, Move or Copy a Browser Profile Safely

A full copy of the profile folder is the most complete backup you can make, because it includes extensions, their settings, site logins (cookies) and open tabs. It works best as a copy on the same computer and the same operating system account.

• Quit the browser, then copy the whole user data folder (not only Default) so Local State comes with it. For Firefox, copy the profile folder and note its name in profiles.ini.
• Restore by quitting the browser and putting the copy back in the same place. To move a Chromium profile to another drive, use the --user-data-dir flag or, in managed setups, the UserDataDir policy, instead of moving the folder and hoping the browser finds it.
• To move to a new computer, use browser sync, or export bookmarks as an HTML file and passwords as a CSV. Saved passwords and cookies are encrypted with keys tied to your operating system account, so a copied profile opens on another computer without them.
• For just one profile, copy only its folder (for example Profile 2) and keep the rest. The browser only shows it in the profile menu if Local State lists it.
• Keep backups somewhere other than the browser folder, and delete old copies that contain Login Data or logins.json.

Profile Folder Copies Compared With Other Ways to Keep Your Data

Troubleshooting: When the Path Doesn’t Match

• The folder isn’t there: the browser may be installed as a Snap, Flatpak or Microsoft Store app, or an administrator changed the location. Trust the path in chrome://version, edge://version or about:support over any list.
• There’s no Default folder in Opera: older installs kept files in the root of Opera Stable. Check the Profile line on opera://about.
• The Sessions folder is empty: the browser was restarted after the loss and replaced the files. Check a system backup such as File History or Time Machine for an older copy.
• Copying fails with “file in use”: the browser is still running. Close it fully, including background processes, and try again.