Skip to content
DOCS

Create a plugin

Make a new plugin with Quick Setup, choosing its framework and interface, or start from a template.

Click New Plugin (+) at the top left, or press ⌘N (Ctrl+N on Windows). Choose how to start:

  • Quick Setup: answer a few questions and get a small working plugin. The best way to start.
  • From a Template: pick a framework version and start from its Starter, or from a template you've saved or imported.

Quick SetupLink to this section

Click a finished step to go back to it.

BasicsLink to this section

  • Plugin name: up to 50 characters. It must start with a letter, and becomes the project's folder name (lowercase, with underscores).
  • Plugin type: Effect processes incoming audio (EQ, compressor, delay). Instrument makes sound from MIDI (synth, sampler).
  • Description: optional, up to 280 characters. It helps an agent understand your plugin.

The maker name your plugin shows in DAWs comes from Settings, Branding. Until you set it, plugins show "Placeholder".

FrameworkLink to this section

The language and framework your plugin is written with. Each card shows its license; the notes below are Studio's own wording.

FrameworkLanguageBuildsLicense
NIH-plugRustFastFree, GPLv3 for VST3: "The framework is ISC licensed; VST3 builds use GPLv3 bindings, so they must comply with GPLv3"
JUCE 9 or JUCE 8C++Slower (a large framework)Free up to $20K: "Free under the AGPLv3 or JUCE's Starter license (revenue up to $20K a year); above that, a commercial JUCE license may be required"
iPlug2C++AverageFree for all use

JUCE has a Version dropdown: JUCE 9 (latest) or JUCE 8. JUCE 7 projects can be imported, but new plugins use JUCE 8 or 9.

JUCE and iPlug2 need CMake. If it's missing, the card offers Install CMake.

InterfaceLink to this section

How your plugin draws its controls:

FrameworkOptions
NIH-plugWebView UI (HTML, CSS and JavaScript) · egui UI · No Custom UI
JUCEWebView UI · JUCE UI (Components) · No Custom UI
iPlug2WebView UI · IGraphics UI · No Custom UI
  • WebView gives you the most design freedom, at a moderate CPU cost.
  • The framework's own UI (egui, JUCE Components, IGraphics) is lighter and looks the same everywhere.
  • No Custom UI lets your DAW show basic controls. It uses the least CPU, but Studio can't preview it: test it in a DAW.

Check the summary, then click Create.

What you getLink to this section

  • A project folder in ~/Freqlab/projects/ (%USERPROFILE%\Freqlab\projects\ on Windows), with a git repository and a first commit.
  • A small working plugin to build on: a gain control for an effect, or a simple synth for an instrument, with its interface.
  • The licensing SDK already wired in, ready for licensed cloud builds.
  • Formats from Settings, Local Build, Build Formats, limited to what the framework can build (see Formats).
  • Its own plugin IDs (CLAP ID, VST3 class ID, or JUCE and iPlug2 plugin codes), made up fresh for each project.

Next, build it and start the preview.

If the name isn't acceptedLink to this section

MessageWhy
Name must contain at least one letter or numberA name made only of symbols has no folder name
Name must start with a letterThe folder name has to start with a letter
Windows keeps this name for itselfNames like CON, NUL, COM1 and LPT1 can't be folders on Windows
xtask is the name of the build tool your projects sharePick another name
A project with this name already existsCase doesn't count: "Delay" and "delay" are the same
"…" is the name of a library NIH-plug usesPick a name that isn't one of its libraries

The description can't contain " \ & < > ; $ or line breaks, because it goes into the plugin's code.