How to inspect a FL Studio project
An .flp names every generator, plugin and sample in the Channel Rack. This reads it in your browser, without FL Studio.
- Drop the project: Drop the .flp, or the whole project folder so the inspector can check which samples came with it.
- Read the report: Third-party plugins on channels and mixer inserts, FL’s own generators and effects, every channel, tempo, meter, pattern count and the FL version that saved it.
- Decide: Install what is missing, collect the samples, or convert the project to the DAW you use.
What the inspector tells you
Every plugin, channels and mixer
A third-party plugin in FL — an instrument in the Channel Rack or an effect on a mixer insert — sits inside the Fruity Wrapper. The inspector reads which ones and lists them apart from FL’s own generators and effects.
Samples it points at
An .flp stores no audio. With the project folder dropped, samples that are not in it are listed as missing — the channels that would otherwise play silence.
Nothing leaves your computer
The project is read by this page, in your browser. Nothing is uploaded or stored.
Questions about the FL Studio inspector?
We have answers.
Do I need FL Studio to use this?
No. It runs in any modern browser, on any system. To play or edit the project you still need FL Studio, or the project converted into a DAW you have.
Does it list mixer effects?
Yes. Effects on mixer inserts are listed with the Channel Rack’s instruments — third-party ones under “Plugins it needs installed”, FL’s own under “FL Studio plugins”.
Is my project uploaded?
No. The page reads the file on your device and nothing is sent anywhere.
Inspect a project from another DAW
The same report for every format — read in your browser, nothing uploaded.
Try these Doseedo tools
- Project inspectors
- From Logic
- From Ableton
- From FL Studio
- From REAPER
- From Pro Tools
- Session files