Where Is the Application Data Folder on Your Computer?
If you've ever gone searching for app settings, save files, or configuration data that doesn't appear in your Documents or Downloads folder, you've likely bumped into the Application Data folder — a hidden part of your file system that most users never see. Here's what it is, where to find it, and why its location varies depending on your setup.
What Is the Application Data Folder?
The Application Data folder is a system-level directory where installed programs store user-specific data that isn't part of the program itself. This includes things like:
- Configuration files and preferences
- Cached data
- Saved states and session history
- License information
- Local databases and logs
The key distinction: this is not where the program is installed. That's typically in Program Files. The Application Data folder holds the user-generated and user-specific runtime data the program creates while running.
Where Is It on Windows?
On Windows, Application Data is stored inside the AppData folder, which lives in your user profile directory. The full path looks like this:
C:UsersYourUsernameAppData By default, this folder is hidden. To access it, you have a few options:
- Run dialog: Press
Win + R, type%AppData%, and press Enter - File Explorer address bar: Type
%AppData%directly into the address bar - Show hidden files: In File Explorer, go to View → Show → Hidden items
The Three AppData Subfolders
AppData is divided into three subdirectories, each serving a different purpose:
| Subfolder | Path Shortcut | What It Stores |
|---|---|---|
| Roaming | %AppData% | Settings that follow you across PCs on a network |
| Local | %LocalAppData% | Large files, caches, device-specific data |
| LocalLow | %AppData%..LocalLow | Data for apps running with low permissions (e.g., browsers in sandbox mode) |
When most people say "AppData," they usually mean the Roaming subfolder — that's the default destination of the %AppData% shortcut. But depending on the app, you may need to look in Local instead. Browser caches, for example, almost always live in Local.
Where Is It on macOS?
macOS handles this differently. There's no single "Application Data" folder with that name, but the equivalent locations are:
~/Library/Application Support/— the closest equivalent to AppData/Roaming; stores preferences, databases, and support files~/Library/Preferences/— stores.plistpreference files for most apps~/Library/Caches/— temporary cached data
The ~/Library folder is also hidden by default on macOS. To access it:
- In Finder, hold Option and click the Go menu — Library will appear as an option
- Or press
Cmd + Shift + Gand type~/Library
Where Is It on Linux?
On Linux, application data follows the XDG Base Directory Specification. Most apps store user data in:
~/.config/— configuration files~/.local/share/— application data (equivalent to AppData/Roaming)~/.cache/— cached data
Some older or non-compliant apps still store data in hidden folders directly in the home directory (e.g., ~/.mozilla or ~/.steam). On Linux, any folder or file beginning with a dot (.) is hidden by default.
Why Does This Matter? 🗂️
Understanding where application data lives is useful in several real-world situations:
- Backing up settings: If you reinstall an app or migrate to a new machine, copying the relevant AppData folder can preserve all your preferences
- Troubleshooting: Corrupted app data is a common cause of crashes or weird behavior — deleting or renaming the app's data folder forces it to rebuild from scratch
- Freeing up space: Caches inside Local (Windows) or
~/Library/Caches(macOS) can grow surprisingly large over time - Syncing between devices: Some apps store sync-eligible data in Roaming, which works with Windows domain environments or manual sync tools
Variables That Affect Where Your App Data Actually Is
Not every app follows the conventions above. The actual location of your application data depends on:
- The operating system and version — folder structures differ, and older Windows versions (XP, Vista) used a different path entirely (
C:Documents and SettingsUsernameApplication Data) - How the developer built the app — some apps use standard OS locations; others write data to custom paths or even inside their own install directory
- Whether it's a desktop app or a Store/sandboxed app — Microsoft Store apps on Windows 10/11 store data in a separate, heavily restricted location under
C:UsersUsernameAppDataLocalPackages - Whether the app is portable — portable apps often store all data in their own folder, bypassing AppData entirely
- Admin vs. standard user accounts — some system-wide settings go to
C:ProgramData(Windows) rather than the per-user AppData folder
Roaming vs. Local: A Practical Distinction ⚙️
The split between Roaming and Local on Windows is more than organizational. Roaming data is designed to sync across machines in managed environments (like corporate networks using Windows domain policies). Local data stays on the device it was created on.
For most home users this distinction doesn't change day-to-day experience — but it does explain why, for example, your browser cache doesn't follow you to a new PC even if your browser settings do.
Finding a Specific App's Data Folder
If you're hunting for one particular app's data, the fastest approach is usually to search inside AppData for a folder matching the app's name or developer name. Many apps name their subfolder after the company rather than the product — so a folder called Adobe might contain subfolders for several different Adobe applications.
On macOS, ~/Library/Application Support/ follows the same pattern, often organized by developer or bundle identifier.
Where your data actually ends up depends heavily on which app you're dealing with, how it was installed, and which OS version you're running — making the specific path something worth verifying for each application individually.