# Native plug-ins and web DAWs

> Why a browser cannot load VST3, Audio Unit or CLAP plug-ins, the routes that bring plug-ins to a web DAW's users, and what Maru builds as native plug-ins.

Canonical: https://maru.audio/docs/native-plugins-and-web-daws
Documentation index: https://maru.audio/llms.txt

A browser cannot load a VST3, Audio Unit or CLAP plug-in. A plug-in bundle
contains a native library compiled for one operating system, which a desktop
host loads through that system's library loader. A web page can run
JavaScript and WebAssembly, and nothing else. A plug-in's preset or state file
does not help either: it is data for the matching plug-in, not the engine.

A Maru module avoids that problem by being one source with separate outputs:
a browser build that a web DAW hosts in its own page, and native plug-ins for
desktop hosts. Each output is built and tested on its own, so a module that
plays in the browser is not thereby a qualified native plug-in, and the
reverse.

## Routes that bring plug-ins to a web DAW's users

| Route | What runs where | Suits |
| --- | --- | --- |
| Your DAW's desktop app | Your native app loads Maru's native plug-in releases through its normal VST3, Audio Unit or CLAP support, with no browser involved | A DAW that already ships a desktop app |
| A browser build of the module | The module's web Release runs in your page through the module player, built from the same source as its native plug-ins | Every Maru module, in your web DAW; see [Host Maru modules in a web DAW](https://maru.audio/docs/host-modules-in-a-web-daw.md) |
| A local helper on the user's computer | A native program the user installs runs their own installed plug-ins, and your page sends it control and audio | Users' own commercial plug-ins, in a DAW that builds and supports such a helper |

A browser build comes from a module's source. It is not a conversion of an
existing plug-in binary, so it applies to modules built on Maru, not to
plug-ins your users bought elsewhere.

A local helper is software your DAW would ship and maintain: an installer,
updates, crash isolation for third-party plug-ins and plug-in state in your
projects. Browsers can require the user's permission before a website reaches
a service on their own computer, so plan the onboarding and the denied state
as you would for a microphone. Maru's local plug-in helper serves Maru's own
apps; it is not a route for a third-party web DAW.

## What Maru builds as native plug-ins

- **One plug-in per module.** A module can be built as its own VST3, CLAP and
  Audio Unit plug-in and as a standalone app, all from the same DSP
  definition. [Native plugins](https://maru.audio/docs/native-plugins.md) describes the
  build.
- **Maru Instrument and Maru FX.** Host plug-ins in VST3, Audio Unit and CLAP
  formats that each load one published instrument or effect per instance.
- **Maru Sampler.** A VST3, Audio Unit and CLAP plug-in that plays sampler
  banks.
- **Maru Samples.** A VST3 and CLAP sample browser for dragging audio into a
  session.

In every format, the host's process call runs Maru's compiled native engine:
audio does not pass through a web view or JavaScript. On macOS the plug-in
window shows the module's own face. A plug-in's saved state is the same preset
data the module's web edition uses, so a session can move between the web and
native editions of the same release.

Maru's signed native releases are for macOS. Qualification is recorded for
each module version, format and Mac architecture separately, so ask for the
record of the exact release you intend to load rather than relying on a
general format claim.

## Test a plug-in in your desktop host

Test the exact release your users will install. Format validators such as
Steinberg's validator, clap-validator and `auval` check that a bundle follows
its format; they do not show that it produces the right sound. Then load it
in your own host: play it, automate a parameter, save the session and reopen
it. [Testing your VST](https://maru.audio/docs/testing-your-vst.md) walks
through those checks in a test host.

[Contact Maru](https://maru.audio/contact) with your host, its formats and the operating systems
you support to plan a test with a specific release.
