Where can I run plugdata patches?

You can run the same plugdata patch in four places: as a standalone desktop app (macOS, Windows, Linux, BSD), as a native iOS app on iPad or iPhone, as a plugin inside a DAW (VST3, AU, CLAP, LV2), or compiled to embedded hardware and C/C++ code via the built-in Heavy/hvcc toolchain. The right target depends on whether you need a live performance tool, a studio integration, or a self-contained device.

Standalone desktop app

Open plugdata, create a patch, and run it as a regular desktop application. This is the simplest target — no host software required, and the patch behaves like any other program on your machine.

• Platforms: macOS, Windows, Linux, BSD
• Use it when: you're designing or testing a patch, teaching, performing live, or you don't want a DAW in the loop.

Native iOS app

plugdata is available as a native iOS app for iPad or iPhone, distributed directly through the App Store. This gives you the same patching environment on a touch device rather than a desktop.

• Use it when: you want a portable instrument or a touch-controlled patch without carrying a laptop.

Plugin inside a DAW

Load the same patch as a VST3, AU, CLAP, or LV2 plugin. Once loaded, it sits in your DAW like any other instrument or effect: you can mix it with other plugins and automate it with MIDI.

• Use it when: you want your patch inside an existing session, synced to a host timeline, or automated alongside your other tracks.
• Format note: AU is the macOS-native format; VST3, CLAP, and LV2 cover the broader cross-platform and open-standard cases. Check which formats your DAW actually loads before committing to a workflow.

Embedded hardware and code export

Using the built-in Heavy/hvcc toolchain, you can export C/C++ code, flash it to an Electro-Smith Daisy, or export real audio plugins. This turns a patch into something that runs without plugdata at all.

• Use it when: you need a standalone hardware unit, a self-contained device, or source code you can build into another product.
• Caveat: this path involves a compiler toolchain and hardware flashing, so expect more setup than the desktop or plugin targets.

Choosing a target

A practical approach: prototype in the standalone app, then move the finished patch to whichever target matches how you'll actually use it. Because all targets run the same patch, you don't need to rebuild it from scratch when you switch.

plugdata is free and open source (GPL-3.0) with no account required, so you can download it and test each target before deciding which one fits your setup.