^{OwlPlug is an audio plugin manager. It provides a complete view of your plugin setup and simple tools to manage it.}

OwlPlug simplifies the way you organize, discover and install audio plugins. No more tedious file management, scattered folders, or missing dependencies — OwlPlug gives you a centralized experience for VST, AU, and LV2 plugins.

• 🔎 Manage — Detect and list your existing audio plugins.
• 🔗 Organize — Merge plugins from multiple locations into a single root directory.
• 📂 Analyze Projects — Scan DAW projects to identify referenced and missing plugins.
• 🌐 Discover — Connect to remote sources to browse and install plugins.

🌍 OwlPlug Website | 📌 Roadmap | 📄 Documentation | 💬 Discord

• About
• Installation
• Features
• Supported Formats & DAWs
• How to Contribute
• Development
• License

OwlPlug is an open-source plugin manager designed to simplify the installation, discovery, and management of audio plugins. It was born out of frustration with the tedious process of installing and organizing plugins. Inspired by dependency managers and online content stores, OwlPlug offers a seamless way to manage your audio tools while also helping you discover new plugins from the community. All feedback, contributions, and suggestions are warmly welcomed.

1. Download the installer for your platform from the Releases page.
   • Windows (x64): *-x64.msi installer
   • MacOS (x64): *-x64.dmg file
   • MacOS (arm64): *-arm64.dmg file
   • Linux (x64): *-x64.deb package or *-x64.AppImage file
2. Run the installer.
3. Launch OwlPlug.

⚠️ macOS Users: On some versions of macOS, you may see a warning that OwlPlug is damaged. This can be fixed by following the instructions on the Troubleshooting wiki page. This issue occurs because the app is not notarized by Apple.

winget install --exact --id=OwlPlug.OwlPlug

OwlPlug can discover VST2, VST3, AU and LV2 Plugins. OwlPlug is compatible with all previously installed plugins as long as they are all in a specific root directory, for example C:/AudioPlugins. Additional directories can be configured if your plugin setup is fragmented on the filesystem.

After downloading OwlPlug, you can still organize (add, move, delete, ...) your plugins with a file explorer or with your favorite DAW without breaking anything.

A Link allows you to create and manage symlinks across your filesystem and plugin directories. With Links, you can access directories anywhere on your filesystem (Hard drive, USB keys, custom directories...) through a single root plugin directory. For example, you can configure a link named usb-drive in C:/AudioPlugins to target your usb hard drive D:/myPlugins. All plugins in D:/myPlugins will be accessible using C:/AudioPlugins/usb-drive. This feature may be useful for DAW that scans plugins from predefined or limited number directories. On some Windows version, symlinks creation may require admin privileges.

OwlPlug can scan DAW projects to extract referenced plugins. Plugins references in project files are compared to plugins installed in configured directories. This way, users can quickly identify missing plugins required to open projects.

The list of compatible DAWs is available in the documentation

OwlPlug can be connected to several remote sources to download plugins. A Remote Source (or Registry) is a collection of downloadable plugins that can be installed locally. OwlPlug can be configured to use any compatible third-party source in Explore Tab > Sources > Add a new source.

Here are some recommended compatible sources.

OwlPlug official plugin registry for Free or Open Source plugins

• kind: registry
• url: https://registry.owlplug.com/registry.min.json

Open Audio Stack registry plugins maintained by community.

• kind: registry
• url: https://open-audio-stack.github.io/open-audio-stack-registry

Discover more plugin sources in this wiki page.

• (Recommended) Distribute your plugins from the open-audio-stack-registry.
• Distribute your plugins from the legacy owlplug-registry.
• Setup and host a custom remote source to distribute multiple plugins, following the open-audio-stack-registry or owlplug-registry specification.

See the full compatibility list for details and version notes.

There are several ways to support and get involved in the OwlPlug development.

• Downloading OwlPlug, using it, and talking about it around you.
• Reporting issues or feature suggestions. Most of the existing features have been inspired by the community feedback.
• Contributing to the OwlPlug source code — see CONTRIBUTING.md for the workflow, branching conventions and PR checklist. Code contributions require agreeing to the Contributor License Agreement.
• Submitting or requesting plugins to be distributed with OwlPlug.
• Donating to help support development and server costs.

Thanks to everyone who already contributed to OwlPlug 💛 — see the full list in CONTRIBUTORS.

• Client: Spring Boot, Hibernate/JPA, H2
• UI: JavaFX, AtlantaFX, ControlsFX, Ikonli
• Parsing: ANTLR4, used to parse DAW project files
• Native plugin scanning: a JUCE-based native host (owlplug-host) plus a companion native scanner binary
• Build: Maven

OwlPlug is a multi-module Maven project:

• JDK (Version referenced in pom.xml)
• Maven (no wrapper is committed, so a local Maven install is required)
• Building owlplug-host from source additionally requires the JUCE toolchain (Projucer and a platform build toolchain).

1. Clone the repository, including its submodules (JUCE, VST SDKs):

   git clone --recursive https://github.com/DropSnorz/OwlPlug.git

2. Run following commands

   # Install dependencies
   mvn clean install
   # Move to owlplug client folder
   cd owlplug-client
   # (Optional) Create the runnable JAR file in /target/ folder
   mvn clean install spring-boot:repackage
   # Run owlplug
   mvn spring-boot:run

mvn test

Code style is enforced automatically via Checkstyle when running mvn install or mvn validate — a style violation will fail the build.

OwlPlug is licensed under the GNU General Public License v3.0.