How to Find the Plugin Folder on Your System or Application

Whether you're troubleshooting a misbehaving extension, manually installing a plugin, or cleaning up files you no longer need, knowing where your plugin folder lives is a surprisingly practical skill. The answer isn't universal — it depends on which application you're using, your operating system, and how the software was installed.

What Is a Plugin Folder?

A plugin folder (sometimes called an extensions directory or add-ons folder) is a dedicated location on your file system where an application stores its plugins — small programs that extend the core software's functionality. When an app launches, it typically scans this folder and loads whatever plugins it finds there.

Some applications manage plugins entirely through a built-in interface, hiding the folder from you. Others expect you to drop files directly into the directory yourself. Understanding which type you're dealing with shapes how you'll find and interact with that folder.

Why the Location Varies So Much

Plugin folder paths differ based on several factors:

• The application itself — Every piece of software decides where to store its plugins. There's no universal standard.
• Operating system — Windows, macOS, and Linux each have different conventions for where apps store user and system data.
• Installation type — A system-wide installation (available to all users) often stores plugins in a different place than a per-user installation.
• Plugin source — Plugins installed through an app's built-in marketplace often land in a different folder than ones you install manually.

Common Plugin Folder Locations by Application Type 🗂️

WordPress (Self-Hosted)

For self-hosted WordPress sites, plugins live inside the web server's file structure:

/wp-content/plugins/ 

Each plugin typically has its own subfolder inside this directory. You can access this via FTP/SFTP, your hosting control panel's file manager, or directly on the server if you have shell access. The exact server path depends on where WordPress was installed (e.g., /var/www/html/wp-content/plugins/ on a Linux server).

DAW and Audio Software (e.g., VST Plugins)

Audio plugins follow the VST (Virtual Studio Technology) standard on Windows and macOS, though individual DAWs let you customize scan paths.

VST2 plugins often use a different default directory, and many DAWs allow you to add custom scan folders through their preferences panel.

Browsers (Chrome, Firefox, Edge)

Modern browsers no longer use local plugin folders the way they once did — the old NPAPI plugin era is largely over. Extensions (the modern equivalent) are managed entirely within the browser and stored in the browser's profile directory:

• Chrome/Edge (Windows):C:Users[YourName]AppDataLocalGoogleChromeUser DataDefaultExtensions
• Firefox (Windows):C:Users[YourName]AppDataRoamingMozillaFirefoxProfiles[profile]extensions

These paths aren't typically meant to be browsed manually — the files are stored in compressed or hashed formats that don't reflect readable plugin names.

Video Editors and Creative Apps (Adobe, DaVinci Resolve, etc.)

Adobe applications store plugins in application-specific directories, often under Program FilesAdobe on Windows or /Library/Application Support/Adobe/ on macOS. DaVinci Resolve uses its own OFX plugin path:

• Windows:C:Program FilesCommon FilesOFXPlugins
• macOS:/Library/OFX/Plugins/

Text Editors and IDEs (VS Code, Sublime Text, etc.)

VS Code stores extensions in:

• Windows:C:Users[YourName].vscodeextensions
• macOS/Linux:~/.vscode/extensions/

Sublime Text keeps packages (its equivalent of plugins) in a user-specific Packages folder, accessible directly from the app via Preferences > Browse Packages.

How to Find the Plugin Folder When You're Not Sure 🔍

If you're working with an application not listed above, these methods usually work:

1. Check the app's own preferences or settings. Most applications that support plugins have a Plugins, Extensions, or Add-ons section in their settings menu. This often displays the current plugin path and lets you change it.

2. Search your file system. Use your OS's search tool to look for a folder named plugins, extensions, or the name of a plugin you know is installed. On Windows, use File Explorer's search or the Everything app for faster results. On macOS, use Spotlight or Finder's search. On Linux, use find / -type d -name "plugins" in the terminal.

3. Check the application's documentation. Most software publishers document their default plugin directories in installation guides or developer resources.

4. Look in AppData or Library folders. On Windows, hidden folders like AppDataRoaming and AppDataLocal are common homes for per-user plugin data. On macOS, ~/Library/Application Support/ holds similar per-user application data. These folders are hidden by default — on Windows, enable Show hidden items in File Explorer; on macOS, press Cmd+Shift+G in Finder and type the path directly.

The Variables That Determine Your Specific Path

Even with all of the above, your exact plugin folder depends on:

• Whether the app was installed system-wide or just for your user account
• Whether you or the application customized the default plugin path
• Which version of the software you're running — older versions sometimes used different directories
• Whether you're on a managed or enterprise system, where IT policies may redirect user data folders

A DAW user who changed their VST scan path years ago, a WordPress developer on a shared host with a non-standard directory structure, and a VS Code user running a portable installation will all find their plugin folders in completely different places — even if they're using similar software.

The most reliable starting point is always the application itself: its preferences, its documentation, and any file management options it exposes directly. What the app tells you about its own folder structure will always be more accurate than any general path guide.