FL Studio 
Native Access does not connect to FL Studio as a live service. It installs and activates Native Instruments software. FL Studio then scans the installed VST3, VST2 or AU plug-in. If the product is a Kontakt library, FL Studio finds Kontakt once and the library appears inside Kontakt—not as another item in the Channel Rack.
Use the correct three-stage setup
- Open Native Access and install or update the NI product.
- Check its Installation Paths, especially the plug-in format and location.
- Open FL Studio’s Options > File settings > Manage plugins.
- Enable Verify plugins and run Find installed plugins.
- Find the instrument under Add/More plugins, favorite it if useful, and load it in the Channel Rack.
- For Kontakt, choose the actual library inside Kontakt’s browser.
Check Native Access locations before installing
In Native Access 2, open Preferences > File Management. Download Location is temporary installer storage. Application Location holds standalone applications. Content Location holds large libraries, Reaktor instruments and expansions. Native Instruments explicitly warns against using the same folder for Downloads and Content.
Keep Application Location at its default unless you have a reason to change it. Put Content on a fast internal or external drive with enough space, using a dedicated folder such as NI Libraries. A content drive is not a VST folder and should not be added wholesale to FL Studio’s Plugin Manager.
Changing Native Access preferences affects future installations. It does not silently move installed products. If a library was moved, use Native Access Repair or Relocate so the product’s stored path is updated.
Know the plug-in paths FL Studio should scan
On 64-bit Windows, Native Access installs VST3 plug-ins to C:\Program Files\Common Files\VST3. Some products can still include VST2 versions, commonly under a Native Instruments VSTPlugins 64 bit folder. On macOS, the system VST3 path is /Library/Audio/Plug-Ins/VST3; AU components use /Library/Audio/Plug-Ins/Components.
VST3 and AU formats belong in their standard system locations. Image-Line recommends custom Plugin Manager search paths mainly for VST2 or a genuinely custom legacy install. Do not move a VST3 file into a sample folder to make it “easier.” The current Image-Line plug-in installation guide documents the expected locations and scan behavior.
Run a verified FL Studio plug-in scan
Open the FL Studio Plugin Manager through Options > File settings > Manage plugins. Leave the default VST3 locations in place, add only the exact VST2 folder if Native Access shows a custom VST2 installation, and enable Verify plugins. Then click Find installed plugins.
Verification is slower than a fast scan because FL Studio opens and identifies each plug-in. The benefit is correct classification as Generator or Effect plus stable plug-in identification. If Kontakt was already scanned before an update, enable Rescan previously verified plugins. If the earlier scan produced Error status, use Rescan plugins with errors.
When the scan finishes, filter for the product name. Favorite the current VST3 version you intend to use rather than every duplicate format. Instruments load through the Channel Rack or Add menu; effects such as Guitar Rig load in a Mixer effect slot.
Understand Kontakt plug-in versus Kontakt library
Kontakt is the plug-in FL Studio scans. A piano, orchestra or drum collection built for Kontakt is content loaded by Kontakt. Electric Mint, a sampled piano or an orchestral library will not normally appear as separate VST3 files merely because Native Access lists them as installed.
Open Kontakt in the Channel Rack, then select the library in Kontakt’s browser. If Kontakt opens but one library is missing, the FL Studio scan has succeeded. Move the diagnosis to Native Access, Kontakt’s library view and the content drive.
Repair a library after moving content
Close FL Studio, Kontakt and other audio applications. Move the library folder once, open Native Access, find the affected product under Installed, and choose Repair or Relocate. Point Native Access at the library’s new root folder, finish the repair, then reopen Kontakt.
Do not add the entire sample drive to FL Studio’s plug-in paths. FL Studio is looking for plug-in binaries; Kontakt is looking for its library content. Mixing those jobs creates long scans without fixing the missing library.
Fix Native Access or Kontakt not showing in FL Studio
The product is installed but no VST appears
Use Native Access’s three-dot menu for the product and inspect Installation Paths. Confirm the VST3 file exists in the default system folder, then run Verify Plugins with previously verified and error rescans enabled.
Kontakt appears in Plugin Manager but not Add
Confirm it is classified as a Generator and mark the Favorite column. You can also use More plugins to open an installed plug-in that is not in the short favorite list.
Kontakt opens but the library is absent
Repair or relocate the library in Native Access. Do not rescan FL Studio repeatedly; the host already found Kontakt.
The scan reports Error
Update the NI product and FL Studio, close standalone instances, and rescan the error. On Apple Silicon, use current compatible product builds and follow Image-Line’s current Apple Silicon plug-in guidance rather than copying old binaries between folders.
The plug-in loads but the project is heavy
Large sample libraries can increase memory and disk activity. The high-CPU guide separates CPU load from disk, buffer and plug-in behavior before you disable random options.
Keep the setup maintainable
Use one current plug-in format where possible, keep VST3 in its standard folder, keep content in a dedicated library location, and document any custom VST2 path. Update Native Access products before opening old projects on a new machine, but keep installers and backups for critical work.
When both VST2 and VST3 appear, do not swap formats inside an established project just to make the database look cleaner. FL Studio identifies plug-ins by more than the visible name, and an old project may ask for the exact format it was saved with. Keep the legacy entry available until important projects have reopened and saved correctly with the intended replacement. For new projects, favor the current supported format and name the favorite clearly enough that you know which one you loaded.
Also test one preset before declaring the installation complete. Load the instrument, play MIDI, save the FLP, close FL Studio, reopen it, and confirm that both the plug-in and library reload without a locate dialog. If Kontakt loads and responds but the project remains silent, leave installation troubleshooting and trace the FL Studio audio path from Channel to output.
For an effect, route a test sound through the Mixer slot and repeat the reopen check. That five-minute test catches an unregistered library path, a duplicate obsolete plug-in, or a content drive that was not mounted before the first real session depends on it.
On a new Apple Silicon Mac, update Native Access, the NI product and FL Studio before troubleshooting compatibility. Use the current native/compatible plug-in build documented by its vendor. If a verified scan still reports an error, capture the exact format and status rather than repeatedly moving files between system folders.
The FL Studio installation guide covers host updates, while the stock-plugin guide helps decide whether a third-party tool is needed at all. For vetted no-cost additions, use the free-plugin guide. The complete selection route lives in the Plugins hub.
Frequently asked questions
Do I add Native Access itself to FL Studio?
No. Native Access installs and activates products. FL Studio scans the installed instrument or effect plug-in, such as Kontakt, Massive or Guitar Rig.
Why is my Kontakt library not listed as an FL Studio plug-in?
A Kontakt library is content, not a separate VST. Load Kontakt in FL Studio, then choose the library inside Kontakt’s browser.
Where does Native Access install VST3 on Windows?
The standard 64-bit Windows VST3 location is C:\Program Files\Common Files\VST3. FL Studio scans that default system folder.
Should I add my Native Instruments content drive to Plugin Manager?
No. Add only a valid custom VST2 plug-in folder when necessary. Kontakt and Native Access manage the content drive.
Why did changing Content Location not move existing libraries?
Native Access location preferences affect future installs. Move an existing library carefully, then use Repair or Relocate to register its new path.
