Where FL Studio Stores Samples, Plugins, and Projects (Windows & Mac)

The User Data Folder: Your Main Save Location

Since FL Studio 20, Image-Line keeps your work outside the program install. The User data folder is the default save location for projects, recordings, the plugin database, presets, and most FL-native content^[1].

On both Windows and macOS the default root is Documents/Image-Line/, with FL Studio creating a FL Studio subfolder for everything it owns^[2]. You can change this path in Options → File settings (F10) → User data folder, but Image-Line warns against cloud sync folders (iCloud, OneDrive, Dropbox) and network drives because locked or moved files can crash sessions^[1].

Backing up Documents/Image-Line/ is the safest way to preserve beats, presets, and plugin favorites when you migrate machines. For a broader DAW context, see what is FL Studio.

Windows vs macOS: Default Path Reference

Paths below assume you have not moved the User data folder. Replace [username] with your OS account name. Many subfolders are created only after you save that type of file for the first time^[2].

Projects, Templates, and Autosave Backups

Every .flp (or zipped project) you save lands in Documents/Image-Line/FL Studio/Projects unless you pick another folder in the save dialog^[2]. Subfolders include Templates for starter sessions and Project bones for exported project data.

Autosave copies go to Projects/Backup and also appear under Browser → Backup^[1]. Configure interval and retention under F10 → File → Backup (Autosave). To recover a crash, use File → Revert to last autosave or drag a backup from the Browser.

If you upgraded from FL Studio 12 or older, the Browser may still show an Old projects shortcut pointing at legacy install-folder paths. Image-Line recommends moving those files into the modern Projects folder^[2].

Samples, Recordings, and Rendered Audio

FL Studio splits working audio into subfolders under Audio^[2]:

Recorded holds Edison takes, mixer-freeze files, and other capture paths. Rendered stores bounced stems and exports you route there. Sliced audio collects Slicex and Edison slices plus samples you drag out of the editor. Shapes stores single-cycle waveforms exported from generators like Sytrus.

Third-party sample packs you download do not automatically appear here. Unless you install them into a Browser-linked folder (next section), FL Studio will not index them. For naming and folder hygiene across DAWs, read sample organization.

• Packs in Downloads Move or extract to a dedicated folder, then add that folder as a Browser extra search path — FL Studio does not scan Downloads by default.
• One-shots in projects Embedded samples travel inside the .flp; external WAV references break if you move files without using Collect all samples.
• Plugin-specific saves Many third-party instruments save to Documents/Image-Line/[PluginName]/ by default^[2].

Where VST, AU, and CLAP Plugins Live

FL Studio scans OS-standard plugin directories. Use each vendor's installer and accept the default location whenever possible — manual copies are mainly for legacy plugins without installers^[3].

On Windows, 64-bit VST2 files go to Program Files\Common Files\VST2. VST3 must land in Program Files\Common Files\VST3 or Program Files\VST3 (32-bit builds also use the Program Files (x86) equivalents). CLAP installs to Program Files\Common Files\CLAP^[3].

On macOS, VST2/VST3 sit under /Library/Audio/Plug-Ins/VST and /Library/Audio/Plug-Ins/VST3. Audio Units use /Library/Audio/Plug-Ins/Components/. CLAP uses /Library/Audio/Plug-Ins/CLAP^[3]. VST3 and AU cannot use custom scan paths — only VST1/VST2 extra folders can be added in the Plugin Manager^[1].

After installing, run F10 → Manage plugins → Find plugins with Verify plugins enabled so instruments and effects sort correctly. Scanned plugins appear in Browser → Plugin database, not as raw .dll files. The database itself is stored at Documents/Image-Line/FL Studio/Presets/Plugin database^[1]. Compare formats in plugin formats VST, AU, and AAX.

Do not install to the FL Studio program folder

Image-Line explicitly says not to drop third-party VSTs into …\Image-Line\FL Studio\Plugins\VST — that folder is reserved for legacy native FL plugins^[3].

Browser Extra Search Folders (Why Samples Go Missing)

This is the most common reason producers cannot find WAVs in the Browser: FL Studio only lists folders you wire in. The Browser extra search folders panel (F10 → File) accepts 30+ custom paths. Anything added there appears in the left Browser tree and is included when FL Studio searches for missing samples on project load^[1].

You can also drag a folder from Finder or File Explorer onto the Browser — FL Studio adds it automatically. Give each row a custom Name so packs read cleanly in the tree.

Important distinction: Plugin search paths in the Plugin Manager find VST binaries but do not surface those folders in the sample Browser^[1]. Samples and plugins use separate routing.

1. Open File settings
   Press F10 and click the File tab.
2. Add a Browser folder
   Click the folder icon on an empty row under Browser extra search folders, browse to your sample library, and confirm.
3. Name the entry (optional)
   Type a label in the Name column — e.g. Drum Kits 2026 — so it is easy to spot in the Browser.
4. Verify in the Browser
   Open the Browser panel; your folder should appear in the tree. Right-click it and choose Open to jump to the OS path.
5. Reload missing projects
   Reopen any .flp that referenced samples from this folder — FL Studio will now resolve paths during the search pass.

How to Open Any FL Studio Folder From Inside the App

You do not need to memorize every path. Image-Line built shortcuts straight into the Browser and settings panels^[4].

• Browser → right-click → Open Opens the selected Browser folder in your OS file manager — works for Projects, Backup, Plugin database, and custom search folders.
• F10 → User data folder icon Jumps to or lets you reset the root Documents/Image-Line location.
• Save preset once When unsure where a plugin stores files, save a preset and note the folder in the save dialog — Image-Line's recommended discovery method^[1].
• Plugin database folder Right-click Plugin database in the Browser and choose Open to edit categories or favorites on disk.

Moving Computers, External Drives, and Common Fixes

To migrate FL Studio, copy the entire Documents/Image-Line folder to the new machine, reinstall plugins to their default system paths, then re-add any Browser extra search folders and run a Verify plugins scan^[2].

If samples show as missing (red in the Channel Rack), the WAV still exists but FL Studio cannot match the stored path. Use Browser → search or Options → File → Reset browser cache after you fix folder links. For save errors tied to permissions or cloud sync, reset the User data folder to default via the Reset button in File settings^[5].

Want a structured first session after paths are sorted? Start with the FL Studio 21 tutorial for beginners or how to make loops in FL Studio.