Freqlab Docs
How to use every part of Freqlab, from your first plugin to getting it in front of Collectors.
Common questions
- Your first plugin in StudioInstall Freqlab Studio, make a plugin, hear it, and open it in your DAW.
- Build a plugin with an AI agentSet up an AI agent in Freqlab Studio, describe the plugin you want, and shape it by talking it through.
- Bring an existing projectImport a JUCE, NIH-plug, iPlug2 or other CMake or Cargo plugin project into Freqlab Studio or Freqlab Express, and get it building, previewing and ready to release.
- Get your plugin signedSet up code signing for macOS and Windows before your first release, in the right order, and check it worked.
- Pass the Freqlab StandardCheck your plugin the way hosts use it, fix what fails, and get it ready for freqlab.co without wasting cloud credits.
- From plugin to freqlab.coBuild your plugin in the cloud, release it in Distro, and list it on freqlab.co, step by step.
- Ship an updateRelease a new version of a plugin that's already on freqlab.co, try a beta first, and deal with a broken version.
By product
- StudioThe audio plugin IDE: write it, hear it as you go, debug and validate it, and keep every version.
- ExpressKeep your own setup: scaffold or import any Rust or C++ plugin project, then build, install and cloud-sign it from one app.
- Creatorcreator.freqlab.co: your Freqlab account, cloud builds and signing credentials.
- Distrodistro.freqlab.co: where creators release their plugins on freqlab.co and keep them up to date.