Technical note
What we mean by StudioZIO Verified
Compatible is not the same as directly tested. StudioZIO Verified marks the host environments for which we have direct test evidence.
Format compliance versus host testing
Audio plug-in formats are defined by formal specifications. A plug-in that passes the Audio Unit validation utility, the VST3 validator, or the AAX validator satisfies the structural requirements of the format. In theory, any conforming host should load it seamlessly.
In practice, every digital audio workstation implements host-side scheduling, process threading, buffer resizing, and UI hosting differently. Format compliance establishes that a plug-in conforms to the API specification; it does not guarantee how a specific host interacts with it under session load.
The StudioZIO Verified standard
On our compatibility surfaces, a host marked with the StudioZIO Verified badge indicates that we have direct, firsthand test evidence for that specific environment.
Currently, REAPER, Logic Pro, and Pro Tools are StudioZIO Verified. For these hosts, we have executed repeatable test suites covering audio thread stability, sample rate transitions from 44.1 kHz to 192 kHz, parameter automation recording and playback, state persistence across session saves, and bypass switching.
What the label does not claim
StudioZIO Verified is a statement of our own internal testing. It is not a vendor endorsement or official certification. For instance, our AAX validation in Pro Tools reflects our test passes; it is not an Avid Certified designation.
It also does not claim that every point release or historical version of a DAW behaves identically. Testing is conducted on current modern releases on macOS.
Unverified is not incompatible
Hosts that do not carry the StudioZIO Verified mark, such as Ableton Live, Bitwig Studio, or Cubase, are not incompatible. Because our plug-ins adhere strictly to the AUv2 and VST3 standards, they generally run without issue in conforming DAWs.
However, we do not apply the verified status until we have completed and documented explicit test protocols in-house. To review current test status or report community host findings, visit the Community Compatibility page.