# MacOS VST3 build not picked up by FL Studio

**URL:** <https://iplug2.discourse.group/t/macos-vst3-build-not-picked-up-by-fl-studio/196>\
**Category:** macOS\
**Created:** [22 August 2020 20:12 UTC](https://iplug2.discourse.group/t/macos-vst3-build-not-picked-up-by-fl-studio/196 "2020-08-22T20:12:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jfyive](https://avatars.discourse-cdn.com/v4/letter/j/b3f665/32.png) [@jfyive](https://iplug2.discourse.group/u/jfyive)\
**Post date:** [22 August 2020 20:12 UTC](https://iplug2.discourse.group/t/macos-vst3-build-not-picked-up-by-fl-studio/196/1 "2020-08-22T20:12:52Z")

</div>

**Build OS** : macOS Mojave  
**DAW** : FL Studio 20 and Reaper (Latest Download)

I am building the IPlugEffect example on a macOS Mojave. I have had success with the stand alone application, and AUv3.

When I open FL Studio and scan for plugins it does not find the VST3 I built, even though I have given FL Studio the location of the VST3 it will not pick it up as a plugin.

If I build AUv3 on macOS, and open Logic. When Logic opens, it scans the system for AU plugins, and it picks up the example project I built. Then I open FL Studio and the AU plugin of the project is available in FL Studio, but still the VST is not.

I decided to test with Reaper, and I found that when I search for the plugin I built, it shows up in Reaper as a _ **VST3i** _ instead of a _ **VST** _, and I can select it and use it as a _ **VST3i** _ .

How do I build a _ **VST3** _ so that it is picked up by FL Studio?

This is the target I selected for building:

![Screen Shot 2020-08-22 at 4.42.30 PM](https://global.discourse-cdn.com/free1/uploads/iplug2/original/1X/c51e847076b2194631b25c05558a088882a8b385.jpeg)

---

<div class="post-metadata">

**Author:** ![jfyive](https://avatars.discourse-cdn.com/v4/letter/j/b3f665/32.png) [@jfyive](https://iplug2.discourse.group/u/jfyive)\
**Post date:** [22 August 2020 22:28 UTC](https://iplug2.discourse.group/t/macos-vst3-build-not-picked-up-by-fl-studio/196/2 "2020-08-22T22:28:09Z")

</div>

Ok, I figured it out.

FL Studio looks for plugins in OS default plugin locations, additionally, FL allows you to provide custom search paths for new plugins. For some reason FL wasn’t picking up my VSTs in the custom search paths but when I added them to the OS default plug in location, FL accepted them!