Understanding VST, AU, AAX and RTAS Plugins
Choosing a plugin format can feel confusing when the same synthesiser, compressor or reverb appears in several versions. VST, AU, AAX and RTAS are not different types of audio effect in the musical sense. They are software formats, or plugin standards, that allow a digital audio workstation to load an instrument or effect.
The format you need depends mainly on your DAW, operating system and workflow. A producer working in Logic Pro on a Mac will usually look for AU, while someone recording in Pro Tools will need AAX. A Windows user working in Cubase, FL Studio or Ableton Live will commonly install VST3. RTAS belongs largely to an older Pro Tools era and can create problems on current systems.
Understanding these differences helps prevent failed installations, missing plugins and duplicate libraries taking up valuable drive space. It also makes it easier to choose between native, Apple Silicon and Intel-compatible versions when buying software from an international developer.
For Australian producers, this matters in home studios from Melbourne apartments to suburban rooms in Brisbane and Perth. Download speeds may be excellent with a reliable NBN connection, but plugin purchases are still priced in changing Australian-dollar amounts, and GST can affect the final checkout total. A little format knowledge avoids paying for the wrong edition.
What A Plugin Format Actually Does
A plugin format is a set of technical rules that defines how a DAW communicates with third-party software. The host sends information such as incoming audio, MIDI notes, tempo, automation and sample rate. The plugin processes that information and returns sound or responds as a virtual instrument. The format provides the communication framework.
This means a VST compressor and an AU version of the same compressor should produce essentially the same result when their settings, processing mode and oversampling options match. The format itself does not make one version warmer, louder or more musical. Sound differences usually come from the plugin’s processing, internal settings, latency compensation or the host environment.
A plugin can be supplied in several formats because developers want it to work across many production platforms. A single purchase might include VST3, AU and AAX installers, although the licence terms vary. Some companies sell separate editions, while others install every compatible format automatically.
The format is also separate from the plugin’s content. A synthesiser may use gigabytes of samples, while the actual plugin file is relatively small. Moving the sample library to an external SSD does not change whether the instrument is VST, AU or AAX.
VST For Broad DAW Compatibility
VST, meaning Virtual Studio Technology, was created by Steinberg and became one of the most widely adopted plugin standards. VST2 was used for many years, while VST3 is the current version supported by most major developers. VST plugins are common in Cubase, Nuendo, Ableton Live, FL Studio, Studio One, Reaper and other DAWs.
VST3 introduced features such as more flexible audio input handling, improved side-chain support and the ability for some plugins to suspend processing when they receive no signal. This can reduce CPU use. VST3 plugins are usually installed in a standard system location, although advanced users can choose custom folders when a manufacturer allows it.
On Windows, VST3 is often the safest choice for modern music software. On macOS, it is also widely supported and can be useful when moving a project between different DAWs. A producer might build a drum arrangement in FL Studio, export stems to a collaborator using Ableton Live, and retain a familiar VST3 collection across both applications.
VST2 remains relevant because older sessions may depend on it, but support has declined. Some current DAWs no longer load VST2 at all, and new installers may provide only VST3. If a session contains a VST2 plugin, replacing it with VST3 is not always automatic: presets, automation paths and plugin identifiers can behave differently.
AU And Apple’s Audio Ecosystem
AU means Audio Units, Apple’s native plugin architecture for macOS and iOS-related devices. AUv2 is the established format used by Logic Pro, GarageBand and many Mac-based audio applications. Logic users generally need the AU version because Logic does not traditionally load VST plugins directly.
AU plugins are closely integrated with Apple’s operating systems, which can make them a dependable choice for Mac studios. AUv3 is a newer, more flexible format designed especially for modern Apple platforms, including iPad and iPhone music apps. AUv3 instruments can often run as self-contained apps as well as inside compatible hosts.
Apple Silicon has added another consideration. A plugin must be compatible with the Mac’s architecture, or the DAW may need to run through Rosetta translation. Many developers now provide universal binaries that work with both Intel and Apple Silicon processors. Checking compatibility is especially important when updating a Mac used for paid sessions in Sydney or a commercial post-production room in Melbourne.
AU is useful for Logic-based collaboration, but it is not automatically the best version for every Mac owner. If projects move between Logic and a cross-platform DAW, VST3 may provide a more consistent plugin format. The best choice is the one supported by the main host and the systems used by collaborators.
AAX And The Pro Tools Workflow
AAX, or Avid Audio eXtension, is the modern plugin format for Pro Tools. It replaced RTAS and TDM as Avid moved Pro Tools towards a newer architecture. Current Pro Tools systems generally use AAX plugins, available in AAX Native and, for compatible hardware-based workflows, AAX DSP editions.
AAX Native processing runs on the computer’s CPU. AAX DSP processing is designed for supported Avid hardware systems and can provide low-latency tracking by handling some processing outside the main computer. The two versions are not interchangeable in every setup, so a studio should check whether a product includes the required edition.
Pro Tools sessions are common in recording, broadcast, film and professional mixing environments. An Australian engineer working on a vocal session for an artist in Sydney may receive a Pro Tools project containing AAX inserts, while a songwriter in Adelaide may work in Logic and send consolidated audio instead. Knowing the expected format avoids last-minute plugin searches when exchanging sessions.
AAX plugins are not designed to load in Logic, Ableton Live or FL Studio. Likewise, installing a VST3 version will not make that plugin appear in Pro Tools. Some DAWs can host multiple formats, but this should not be confused with universal compatibility. The DAW still needs a specific plugin wrapper that it knows how to scan and authorise.
Why RTAS Is Now A Legacy Format
RTAS, short for Real-Time AudioSuite, was used by earlier versions of Pro Tools. It was a familiar format for many engineers working with Pro Tools 9 and Pro Tools 10, but it was superseded by AAX as the platform evolved. Current Pro Tools releases do not generally support RTAS, which makes it unsuitable for a new production setup.
RTAS plugins may still matter when opening archived sessions on an older computer. A studio with a vintage project, discontinued virtual instrument or irreplaceable mix might preserve an older Pro Tools installation for access. In that situation, the operating system, authorisation method and original plugin installers all become part of the archive.
Trying to force RTAS plugins into a modern DAW through unofficial wrappers can create instability, crashes or incorrect automation. Even if a bridge makes a plugin load, it may fail during rendering or lose its licence after an operating system update. For dependable current work, look for an AAX replacement or print the older track to audio.
The same principle applies to old VST2 instruments and discontinued AU products. Before upgrading a studio computer, open important sessions and bounce critical parts to stems. Save MIDI, presets and effect settings as well. A rendered audio track preserves the musical result even when the original plugin can no longer run.
Choosing The Right Format For Your Setup
Start with the DAW rather than the plugin shop. Logic Pro usually points towards AU, Pro Tools towards AAX, and Cubase, Ableton Live, FL Studio and Reaper commonly support VST3. Confirm the exact requirements in the manufacturer’s compatibility list because support can vary between Windows, macOS, Linux and mobile systems.
Then check the processor architecture and operating system. A current Mac may require Apple Silicon support, while a Windows workstation may need a 64-bit installer. A plugin can be technically compatible with a DAW yet still fail because its licence manager, copy-protection driver or sample library is outdated.
Think about collaboration as well as personal preference. If a Melbourne producer exchanges Logic sessions with a mix engineer using Pro Tools, the two people may need different plugin formats from the same developer. If the session is being shared with audio stems, format matters less; if the recipient must edit the original inserts, matching plugin editions becomes essential.
Keep installations organised. Install only the formats your workflow uses unless you regularly move projects between hosts. Store installers, serial numbers and licence details in a secure location, and keep a record of older versions before major system upgrades. For producers comparing monitoring and mix decisions, the practical guidance in this stereo and mono guide is also useful, since channel format and plugin format are separate technical questions.
A reliable community can help when a plugin fails to scan or a legacy project behaves unexpectedly. Producers can compare DAW versions, operating systems and installation paths through Melody Mix, where discussions, feedback and production resources support a range of workflows. Specific error messages and screenshots usually make troubleshooting more productive than simply stating that a plugin does not work.
The simplest rule is to match the plugin format to the host: VST3 for many modern cross-platform DAWs, AU for Apple-focused hosts, AAX for current Pro Tools, and RTAS only for carefully maintained legacy systems. Check architecture, licensing and project-exchange needs before installing, then preserve important tracks as rendered audio so your music remains usable when software standards change.