FL Studio on Mac: Apple Silicon, plugins and what differs from Windows
FL Studio has run natively on Mac since FL Studio 20 (2018), on Intel and Apple Silicon. Most differences from Windows come down to plugins: AU, VST, VST3 and CLAP formats, Intel plugins handled by FL's bridge or by Rosetta, and a rescan each time you switch modes. This guide covers each case, current as of FL Studio 2026 (version 26.1) and Apple's announcement that Rosetta ends after macOS 27.
Does FL Studio run natively on Apple Silicon?
Yes. FL Studio has run natively on Apple Silicon Macs (M1 and later) since version 20.8.4 in September 2021, and it still supports Intel Macs. Image-Line's download page asks for macOS 10.15.7 or newer, 4 GB of RAM and 4 GB of free disk space (checked November 9, 2026).
A MacBook and a desktop Mac behave the same way: only the processor matters.
Apple Silicon or Rosetta: what the mode changes
On an Apple Silicon Mac, FL Studio can start in native mode or under Rosetta 2, Apple's translation layer for Intel code. Image-Line's manual ("Installing plugins" page) describes how the mode affects plugins:
| FL mode | Intel VST | Intel AU | CPU | Rescan |
|---|---|---|---|---|
| Native Apple Silicon | loaded through FL's bridge | handled by macOS, seen as native | a bridged plugin uses more CPU than an Apple Silicon version | the first time you use the mode |
| Rosetta 2 | handled by macOS | handled by macOS | all of FL is translated, no bridge | the first time you use the mode |
To see which mode FL is running in, open Activity Monitor: the Kind column shows Apple or Intel for each app. To switch, quit FL, select FL Studio in the Applications folder, choose File > Get Info, then check or uncheck "Open using Rosetta". Restart FL and rescan your plugins.
Intel plugins and FL's bridge
The bridge runs an Intel plugin in a separate process. The manual points out three side effects:
- CPU: a bridged plugin will almost always use more CPU than its Apple Silicon version, when one exists.
- Stopped playback: a bridged plugin can take the audio focus and stop playback. The manual's fix on Mac is to turn off Auto close in the audio settings. Its other fix, the FL Studio ASIO driver, is described for Windows.
- Crashes: FL's version history lists many fixes for bridged plugins, for example "Bridged plugins crash when opened in macOS 15.4" (fix 19599).
To check whether a plugin is Intel-only, open Terminal and run lipo -archs on the plugin's binary, for example lipo -archs "/Library/Audio/Plug-Ins/VST3/Name.vst3/Contents/MacOS/Name". x86_64 alone means Intel-only; x86_64 arm64 means a universal binary.
macOS 27 and the end of Rosetta: which plugins may stop loading
Apple announced on September 1, 2026 (developer.apple.com) that macOS 27 is the last version to support Rosetta: "Intel-only apps will no longer run on Mac computers with Apple silicon after this update". Apple plans to keep part of Rosetta for older games, according to MacRumors (June 2026). The same source reports that Intel Macs stop at macOS 26.
What Image-Line's manual says: in native Apple Silicon mode, FL Studio runs Intel VST plugins through a process bridge, at about 2% extra CPU per plugin; Intel AU plugins are handled by macOS; in Rosetta mode, macOS handles Intel VST and AU plugins and FL bridges nothing. The manual doesn't say whether the bridge relies on Rosetta, and as of November 9, 2026 Image-Line has published nothing on what happens to Intel VST plugins after macOS 27.
What to do now:
- List your Intel-only plugins with
lipo -archs. - Check each developer's site for an Apple Silicon or universal version.
- For an abandoned plugin, pick an Apple Silicon replacement and swap it into your current projects.
- Switch FL to native mode if it isn't already, and rescan.
This section will be reviewed with each macOS release.
AU, VST, VST3 or CLAP: which format to use on Mac
FL Studio for macOS supports 64-bit VST 1 and 2, VST3, 64-bit AU, CLAP and FL's native format.
| Format | On Windows | Folder on Mac | Note |
|---|---|---|---|
| AU | no | /Library/Audio/Plug-Ins/Components | no MIDI output |
| VST (1 and 2) | yes | /Library/Audio/Plug-Ins/VST | the only format that accepts custom search folders |
| VST3 | yes | /Library/Audio/Plug-Ins/VST3 | must be in the system folder |
| CLAP | yes | /Library/Audio/Plug-Ins/CLAP | supported since FL Studio 2024.1 |
| Native FL | yes | managed by FL | only exists inside FL Studio |
So, AU vs VST in FL Studio? The manual recommends VST when a plugin comes in both formats: your projects stay compatible with Windows, and a VST usually needs slightly less processing than an AU, which developers often build as an extra layer on top. Don't install anything in the FL Studio folder, which is reserved for FL's native plugins. VST and VST3 plugins can also live in ~/Library/Audio/Plug-Ins; that folder is hidden by default (press Cmd+Shift+period in Finder to show it).
Missing plugins: rescanning in the Plugin Manager
A plugin installed in its default location only shows up in FL after a scan.
- Open Options > File settings > Manage plugins.
- Check Verify plugins: FL opens each plugin and files it as an instrument or an effect.
- After updating a plugin, also check Rescan previously verified plugins.
- Start the search with Find plugins (the manual's "Installing Plugins" page also calls it Find installed plugins).
Rescan after every mode switch (native or Rosetta) too. FL Studio 26.1 shows the plugin list faster and warns you when Rescan all is on, since a full scan can take a long time.
Audio settings on Mac
macOS uses Core Audio, selected in Options > Audio settings. Buffer values from the manual:
- Apple Silicon: start at 128 samples, which engages the performance cores. If you hear crackles, step up to 192, then 256. 128 has been the default on Apple Silicon since FL Studio 2024.1.
- Intel: 10 to 20 ms (440 to 880 samples).
To use more than one audio interface, create an Aggregate Device in Audio MIDI Setup (Utilities folder), then select it in FL. The manual notes that this setup makes interfaces more reliable. FL Studio 26.1 adds a separate audio input selector on macOS.
What's different from Windows
- AU plugins exist only on Mac.
- Plugins must be 64-bit: FL for macOS has no 32-bit bridge, unlike Windows.
- A Windows VST won't load on a Mac: you need the developer's macOS installer.
- To share projects with Windows users, use the VST version of your plugins. FL doesn't match an AU to its VST equivalent when it opens a project. Since FL Studio 26.1, AU plugins sit at the end of the "More" list by default.
- Shortcuts: Ctrl becomes Cmd, Alt becomes Opt. Since FL 25.1.5, Cmd+Q quits FL and the Piano roll's Quick Quantize moved to Opt+Cmd+Q.
- Right-click on a trackpad: two fingers. Ctrl+click also works since the fix in FL 26.1.1 (July 2026).
Native FL Studio plugins
FL's native plugin format is neither AU nor VST and only runs inside FL Studio. Fern is one example: a native effect, built as a universal binary (Apple Silicon and Intel), that goes in a slot on the Master and measures up to 125 mixer tracks. Its .pkg installer puts it in the user's home folder (~/Library/Application Support/Fern), outside the FL Studio app folder, without an administrator password: an FL update doesn't remove it, and it shows up in FL without a scan. It is tested on FL Studio 25.2.5 and FL Studio 2026. Under Rosetta, some of its features are turned off, such as reading internal names. See what these FL Studio plugins for Mac do once they're part of the mixer.
More FL Studio mixing topics are covered in the guides.
FAQ
Do Intel-only plugins work in FL Studio on Apple Silicon?
Yes, for now. In native mode, FL loads Intel VSTs through its bridge, and macOS handles Intel AUs. The bridge costs extra CPU. After macOS 27, Apple will stop running Intel-only apps; how that affects FL's bridge is yet to be confirmed by Image-Line.
Why don't my plugins load after switching from Rosetta to Apple Silicon?
FL keeps a separate plugin list for each mode. The first time you start FL in a new mode, open Options > File settings > Manage plugins and run a scan with Verify plugins checked.
Can I open a Windows FL Studio project on a Mac?
Yes, the project file opens. Third-party plugins only load if their macOS VST version is installed: a Windows VST won't run on a Mac, and FL doesn't swap a VST for its AU equivalent.