FL Studio 
Your plugin loads fine, but finding it means scrolling past tools you never touch. To organize the FL Studio Plugin Database, curate its Effects and Generators favorites folders and leave the installed plugin binaries exactly where they are. Start with one useful category, back up the database, then add a working plugin with the opening state you actually want.
One distinction is worth holding on to: Installed holds the entries FL Studio detected, while your favorites feed the Plugin Picker and loading menus. Tidying folders should never turn into a reinstall.
What does the FL Studio Plugin Database control?
Image-Line’s Browser documentation separates the top-level Effects and Generators favorites from the entries inside Installed. The first two folders hold your curated choices. Installed is the discovery inventory, and it is the wrong place to build your personal category tree.
| Location or action | What it changes | What it does not do |
|---|---|---|
| Plugin database → Installed | Entries discovered by scanning; verification identifies the plugin type | Create your ideal shortlist automatically |
| Plugin database → Effects / Generators | Favorite presets, categories and associated thumbnails | Move or install a VST3, AU, CLAP or VST2 component |
| Browser star | Add a file to the Starred tab | Perform the plugin-favorite command |
| Refresh content | Reread Browser files and folders | Run a verified plugin scan |
If the plugin has never loaded, finish its installation and first verified scan first. If an entry you expect is missing or shows an error, follow the missing-plugin diagnostic. This guide picks up once discovery works.
Choose plugin categories around the job
A vendor folder helps when you remember the manufacturer. When you need an EQ, a category named after the job usually gets you there faster. Try six starting groups across the two branches: Generators → Synths, Samplers and Effects → EQ, Dynamics, Space, Utility. These are only suggestions; FL Studio does not require these folder names.
Add Drums, Bass, Saturation or Metering only when your own collection needs the split, and keep the existing categories that already work. Two well-chosen reverbs do not need an elaborate filing system, while a big sound-design collection might justify separate Reverb and Delay folders.
Pick a few entries from your stock-plugin toolkit before adding more downloads. A small free-plugin rack can cover a missing job without turning every scan result into a favorite.
Find and back up the active Plugin Database folder
Right-click Plugin database in the Browser and choose Open, and Explorer or Finder opens that folder. Copy the whole folder to a dated backup outside the active database before you move, rename or remove anything. During ordinary organizing, leave the active parent folder’s name and location alone.
The usual location is Documents/Image-Line/FL Studio/Presets/Plugin database. A custom User data folder changes it, so trust the folder FL Studio opens for you over any guess. Older tutorials may point inside the application installation, but the current database normally lives in your user data.
A favorite consists of an .fst preset plus its metadata and image files, when they exist. The Browser manual describes .nfo and .bmp, yet existing collections may hold a .png thumbnail instead. Keep whatever bundle you actually find, and don’t convert image extensions or throw a file away because it differs from an example.
Keep your active User data on a reliable local drive. Image-Line’s User data guidance warns against iCloud, OneDrive and other cloud-synced locations for active data. Keeping a separate archived backup is fine; letting a sync service manage the working database is the problem.
Organize the Plugin Database in eight steps
Before a close-and-reopen test: FL Studio Trial can save a project but cannot reopen it until you buy FL Studio, so export any work you need to keep before closing. In a licensed host, native plugins you do not own can also still be in Trial: they may reopen as empty Channels or FX Slots, and resaving before unlocking them loses their saved settings. Don’t use that project as a cleanup test. Image-Line explains the separate host and plugin Trial restrictions.
- Check one working plugin. Load an instrument or effect from Installed and confirm sound at a sensible listening level. Do not troubleshoot scanning by moving database files.
- Choose a small category plan. Separate instrument jobs under Generators from processing jobs under Effects. Start with categories you will actually use.
- Open the active folder. Right-click Plugin database in the Browser and choose Open. Confirm that this is the database used by your current FL Studio installation.
- Make a dated backup. Copy the complete Plugin database folder outside the active location. Keep it unchanged while testing.
- Create the needed subfolders. Add a category inside the top-level Effects or Generators branch. Leave Installed and the plugin binaries alone.
- Add a favorite deliberately. Use the Plugin Manager Favorite box for a quick entry, or open the desired Browser category and use Add to plugin database (flag as favorite) from the loaded plugin’s menu.
- Refresh and inspect. Use Browser Refresh content after file changes. Check the destination and, for a thumbnail, the tab’s Show images setting.
- Test loading and recall safely. Check F8, the appropriate Add choice, Channel Rack and Mixer. Test a separately named saved project only with a licensed host and licensed plugins; Trial users should preserve audio and defer reopening.
Add favorites with or without a thumbnail
For the quick route, open Options → Manage plugins and tick the plugin’s F (Favorite) box. The Plugin Manager instructions note that this adds a favorite without creating a thumbnail. If the product has separate VST2, VST3 or other entries, pick the format you intend to use.
For a favorite with a picture, load the plugin, set up its preferred starting state and open the target subfolder under Plugin database → Effects or Generators. From the loaded plugin’s top-left menu, choose Add to plugin database (flag as favorite) and confirm the destination. The Wrapper command uses whichever database location is currently open.
If FL Studio asks you to choose a subcategory, open the category inside its Browser (Finder or Explorer will not do) and try again, checking the destination before accepting. You can repeat this in a second category when a plugin really serves two jobs, but skip duplicates that only make the list longer.
The Browser star is no substitute. Image-Line explicitly distinguishes plugin favorites from starring files: the star feeds the Starred tab and has nothing to do with the plugin loading-menu favorites.
Capture a useful thumbnail and opening state
The .fst saves a starting state; it is more than a link to the plugin. If you want a neutral instrument, load its initial patch before adding it. If you want a particular analyzer range or GUI scaling, set that on purpose. Capture yesterday’s extreme effect settings and that is exactly what tomorrow’s “fresh” instance will open with.
Some GUI options are stored with presets rather than in the Wrapper’s ordinary per-plugin options. Check the new favorite by loading it into a fresh slot, since not every vendor setting comes back the same way. Channel color and icon can also be kept if you set them before creating the favorite.
Make editor thumbnail is a different command, and its image shows up under Browser → Current project. It is not the usual way to add a Plugin Database favorite. For the database, use the favorite command with the plugin interface visible, then check Show images on the Browser tab and refresh its content.
Move, rename or remove favorites without uninstalling
When moving a favorite to another category, keep its .fst, the matching metadata and the thumbnail together, and work only inside the curated Effects or Generators branch. Move one bundle, refresh and load it before moving the next. There is no need to rebuild the Installed tree to mirror your categories.
Renaming a category folder is easier than renaming a favorite’s individual files. The metadata may refer to the thumbnail by filename, so changing only the visible preset name can leave the image behind. For routine organizing, keep the original filenames. If you need custom names, back up first and check the associated metadata instead of blindly renaming three files. A working preset with a missing picture needs its thumbnail fixed; reinstalling the plugin will not help.
The Plugin Manager also has a Name field on its Plugin tab for changing a plugin’s display name in the database. That is separate from renaming the installed component. After changing it, check the newly created favorite and its image, because separately saved custom entries may keep their old names.
To remove a favorite, right-click its entry in the curated Effects or Generators folder and choose Delete file. Read the confirmation and check the target. Image-Line states that this removes the database entry and leaves the installed plugin alone. Don’t confuse it with Delete in the Wrapper’s top-left Plugin Menu, which removes an instance from the current project, or with the Delete control in Wrapper options, which clears saved options.
A second entry may be a different format or a state you saved on purpose, so check which one you actually use before removing the unwanted favorite. Uninstalling an older plugin version just to shorten a menu can leave older projects without a component they need.
Test F8, loading menus and project recall
Press F8 to open the Plugin Picker, with generators on the left and effects on the right. Type part of a name to narrow the list. If a plugin or your operating system grabs that key, use Add → View plugin picker; the shortcut reference covers other navigation commands.
The current Add menu separates Channel for a generator from Effect for the Mixer, so check both with the matching favorite. Loading menus that offer Simple, Categories or Tree views can show the same library in different ways; look at the chosen view before deciding a category has vanished.
| Symptom after organizing | First check |
|---|---|
| Folder changes are absent | Confirm the active User data location, then Refresh content |
| Favorite exists but its picture is hidden | Show images, the associated image file and favorite capture |
| Entry opens with unwanted settings | The saved favorite state; preserve the original before replacing it |
| Only one loading menu lacks the entry | Instrument/effect destination and menu display mode |
| Nothing loads, or a scan reports Error | Plugin discovery or compatibility—not folder decoration |
In a licensed host with licensed plugins, build a small, separately named project with one instrument and one effect loaded through the new favorites. Save and reopen that test, and keep the original database backup. Trial users should follow the warning above and put off recall testing instead of risking a session.
Move your favorites to another computer
A Plugin Database backup carries presets and their associated files; third-party binaries, licenses and full sample libraries stay behind. On the destination computer, install the required plugins and libraries, authorize them, scan as needed and back up the existing database before copying your curated folders. Test a small selection before merging the rest, and never overwrite another working library blindly.
For a complete move, follow Image-Line’s FL Studio migration procedure. Cross-platform projects also need matching plugin formats and versions; copying an AU favorite’s folder will not turn it into a Windows VST3 preset.
Use the Apple Silicon compatibility guide for architecture issues. If a loaded plugin causes processing spikes, troubleshoot high CPU. Putting a plugin in a category changes neither its processing cost nor its license, and your FL Studio edition and separate purchases still decide what is unlocked.
When should you reset the default Plugin Database?
Resetting is meant for a damaged or missing default structure; routine sorting never calls for it. First check the active folder and your backup. Image-Line’s database reset procedure copies the default Effects or Generators content from the installation resources into user data, and those defaults do not include your custom plugins.
The source is Data/System/Plugin databases inside the Windows installation. On macOS, use Show Package Contents on FL Studio, then go to Contents/Resources/FL/Data/System/Plugin databases. Pick the default structure you need and replace only the affected user-data branch after backing it up. The support procedure deletes the folders it replaces, so keep an external copy you can restore.
After that recovery, the procedure calls for Options → Manage plugins with Verify plugins, Rescan previously verified plugins and Rescan plugins with errors. You do not need that full recovery scan every time you create a category. Restore your own favorites from backup once the default library checks out, and test before deleting any recovery copies.
FL Studio Plugin Database FAQ
Where is the FL Studio Plugin Database folder?
Right-click Plugin database in FL Studio’s Browser and choose Open. The usual path is Documents/Image-Line/FL Studio/Presets/Plugin database, but a custom User data location changes it.
What is the difference between Installed and favorites?
Installed holds the plugin entries FL Studio detected. The top-level Effects and Generators folders hold the curated favorites that the Plugin Picker and loading menus use, so organize those and leave the Installed tree alone.
How do I add a plugin thumbnail?
Load the plugin and set its desired starting state. Open the target Effects or Generators subfolder in FL Studio’s Browser, choose Add to plugin database (flag as favorite) from the plugin menu, and confirm the destination.
Why does starring a plugin not add it to the menu?
The Browser star adds a file to the Starred tab. Use the Plugin Manager Favorite box or Add to plugin database (flag as favorite) for plugin loading-menu favorites.
Can I organize plugins without moving VST files?
Yes. Work with favorite presets, metadata and associated images inside Effects or Generators. Leave VST2, VST3, AU and CLAP components in their installed locations.
Does deleting a favorite uninstall the plugin?
No. Delete file on a curated database entry removes that entry, not the installed plugin. Check that you selected the intended favorite and keep a backup before removing it.
Why does a favorite open with the wrong sound?
A favorite recalls the state saved when you created it. Load the patch or settings you actually want and recreate that favorite, keeping a backup before replacing the old entry.
How do I refresh the Plugin Database?
Use Browser Refresh content after changing files. It rereads the folders and is no substitute for a verified plugin scan. If a thumbnail is hidden, also check Show images for that Browser tab.
Can I copy the database to another computer?
You can transfer favorites and their associated files, but the destination still needs compatible plugins, licenses and libraries. Back up its existing database before merging, then test loading and project recall with licensed software.
Should I reset the database to fix a messy menu?
No. Start with category organization, menu display options and the correct active folder. Reserve the default-database reset for damaged or missing structure, and back up first, since it can replace your custom content.
Keep the favorites you actually reach for, hold on to a recoverable copy and test the real loading menus. For samples, search scopes and tabs outside this plugin branch, continue with the FL Studio Browser guide. The Plugins library ties these setup tasks together, and Troubleshooting covers failures that no amount of organizing can fix.
