How to Open AAX Plugins in FL Studio

FL Studio does not natively open AAX plugins, but you can use workarounds to run them

FL Studio uses its own plugin format called VST and VST3, not AAX. If you have an AAX plugin you want to use in FL Studio, the plugin will not load directly into the software. However, you have two practical options: use a wrapper program that converts AAX to VST, or switch to a different audio workstation that supports AAX natively.

The reason this matters is that some professional plugins—particularly those from companies like Pro Tools—are released in AAX format first or exclusively. If you own one of these plugins and use FL Studio as your main production software, you need to know your actual options before spending time troubleshooting.

Key Takeaways

FL Studio accepts VST and VST3 plugins, but not AAX plugins in any version.
Blue Cat's PatchWork and similar wrapper software can convert AAX plugins to VST, though this adds a step and potential compatibility issues.
If you frequently need AAX plugins, switching to Reaper, Ableton Live, or another DAW that supports AAX may be simpler than using a wrapper.
Check your plugin's documentation to confirm whether a VST version exists before attempting a workaround.

Why FL Studio does not support AAX format

AAX is the plugin format owned and maintained by Avid, the company behind Pro Tools. FL Studio's developer, Image-Line, chose to build the software around VST instead, which is an open standard supported by hundreds of audio workstations. This is a deliberate design choice, not a limitation that will change in future updates.

VST plugins are more widely compatible across different DAWs and operating systems. FL Studio supports both VST2 and VST3, which covers the vast majority of third-party plugins on the market. If your plugin exists in VST format, FL Studio will open it without any workaround.

Check if your plugin has a VST version

Before attempting any wrapper or conversion method, visit the plugin manufacturer's website and check their download page. Many companies that release AAX plugins also release VST versions of the same software. This is the simplest solution and requires no additional software.

Look for a downloads section on the company's website, filter by your operating system (Windows or Mac), and see what formats are listed. If both AAX and VST are available, download the VST version. If only AAX is listed, then you know you need a workaround or alternative.

Using a wrapper to convert AAX to VST

A wrapper is a piece of software that sits between your DAW and your plugin, translating one format into another. Blue Cat's PatchWork is the most commonly used wrapper for converting AAX to VST in FL Studio. You install the wrapper as a VST plugin in FL Studio, then load your AAX plugin inside it.

The process works like this: open FL Studio, add Blue Cat's PatchWork as a VST plugin on a track or mixer channel, then open PatchWork's interface and load your AAX plugin from inside the wrapper. The audio and MIDI will route through the wrapper to your AAX plugin and back out to FL Studio. This method works, but it adds latency and uses extra CPU resources because the audio is being converted twice.

Wrappers are not perfect. Some plugins behave unpredictably inside a wrapper, automation may not work correctly, and you lose the ability to save the plugin's settings as part of your FL Studio project in some cases. If the wrapper method fails, you will need to either find a VST alternative or use a different DAW.

Switching to a DAW that supports AAX

If you own multiple AAX plugins or work frequently with Pro Tools users who send you AAX sessions, switching to a DAW that natively supports AAX may be more practical than using wrappers. Reaper, Ableton Live, Logic Pro (Mac only), and Studio One all support AAX plugins directly.

This is a larger decision than installing a wrapper, but it eliminates compatibility issues entirely. You will not have to troubleshoot plugin behavior or deal with conversion overhead. If you are already considering switching DAWs for other reasons, AAX support might tip the decision in favor of one of these alternatives.

Checking FL Studio's plugin folder settings

If you have installed an AAX plugin and expected FL Studio to find it automatically, the software will not scan AAX folders because it does not recognize the format. FL Studio only scans for VST plugins in its designated plugin directories. You can verify this by opening FL Studio's settings, navigating to the Plugins section, and checking which file paths are listed for plugin scanning.

Even if you manually point FL Studio to a folder containing AAX plugins, the software will skip over them and only load VST files. This is not a configuration issue—it is how the software is designed. If you see AAX files in your plugin folder but they do not appear in FL Studio's plugin list, that is the expected behavior.

Frequently Asked Questions

Will FL Studio ever support AAX plugins?

Image-Line has not announced plans to add AAX support to FL Studio. The company has committed to VST and VST3 as the plugin standards for the software. If AAX support becomes important to your workflow, you would need to switch to a different DAW rather than wait for an update.

Can I convert an AAX plugin file to VST myself?

No, you cannot manually convert the plugin file. The plugin format is built into the compiled code, and changing it requires the original source code and the plugin developer's involvement. Only the company that created the plugin can release a VST version.

Does the wrapper method work on both Windows and Mac?

Blue Cat's PatchWork and similar wrappers work on both operating systems, but AAX plugin availability varies. Some AAX plugins are Mac-only, particularly older Pro Tools plugins. Check whether your specific AAX plugin is available for your operating system before purchasing a wrapper.

If I use a wrapper, will my FL Studio project still open on another computer?

If the other computer does not have the wrapper and the AAX plugin installed, FL Studio will not be able to load that track or channel. The project file will open, but the plugin will show as missing. This is one reason wrappers are not ideal for collaborative work or archiving projects long-term.

What if the wrapper does not recognize my AAX plugin?

Some AAX plugins, particularly very new or very old ones, may not work reliably inside a wrapper. If the wrapper cannot load your plugin, your options are to contact the plugin developer and ask for a VST version, or switch to a DAW that supports AAX natively. There is no other workaround.

This guide is for general information only and is not medical, financial, legal, or other professional advice. For decisions specific to your situation, consult a qualified professional. See our Editorial Policy.