Audio Plugin Development Frameworks & APIs
March 30, 2026 · View on GitHub
A reference page for audio plugin frameworks, plugin formats, SDKs, and build tools relevant to VST3, AU, CLAP, and LV2 development.
Back to the hub: README.md
Core Frameworks
- JUCE — Industry-standard C++ framework for audio plugins and apps.
- iPlug2 — Lightweight C++ framework for VST2/3, AU, AAX, and web audio.
- DPF — Cross-platform framework with LV2, VST2/3, and CLAP support.
- CLAP — Open plugin standard by Bitwig and u-he.
- NIH-plug — Rust-based plugin framework.
Build Tools & SDKs
- VST3 SDK — Official VST3 SDK.
- Projucer — JUCE project creation and editing workflow.
- CMake — Common build system for modern cross-platform plugin projects.
- pluginval — Plugin validation and compatibility testing.
- Pamplejuce — JUCE starter template with CI and CMake.
Framework Comparison
| Framework | Language | Strength | Best Fit |
|---|---|---|---|
| JUCE | C++ | mature end-to-end workflow | general-purpose plugin development |
| iPlug2 | C++ | lighter-weight framework | leaner projects |
| DPF | C++ | open-source and Linux-friendly | cross-platform open toolchains |
| NIH-plug | Rust | Rust-native development | Rust DSP stacks |
| CLAP | format / API spec | modern open standard | future-facing format support |
Plugin Formats
- VST3 — dominant in many modern DAW workflows
- AU — essential for Apple ecosystems
- CLAP — open standard with growing developer interest
- LV2 — relevant in Linux and open-audio communities
How Frameworks Matter
A framework generally provides:
- host integration
- parameter handling
- UI abstractions
- project organization
- format wrapping
- lifecycle management for processing and state
Build Pipeline Notes
A typical plugin-development workflow:
- choose a framework
- scaffold the project
- configure builds with CMake or the framework’s workflow
- validate with
pluginval - test in hosts
- iterate on DSP/UI separation and packaging