Make yours playable.

Start with a browser build.

Your effect can run on the listener’s device, with no streaming session or timer. A desktop VST file alone cannot be converted automatically. You need the source code and a supported build process, or a browser-ready WAM 2 package.

Have a WAM 2 build?

The local Patchwork packaging tool checks your files and prepares a ZIP. It checks metadata, paths, limits, and file integrity. It does not upload files or certify the effect’s sound or safety.

Download the source and packaging tool. See browser-lab/creator/README.md in the archive for complete instructions.

Try a working example

All 30 effects in this catalog also have tested WAM 2 versions. The downloaded tools include export-curated.py to package an effect with its controls, dependencies, licenses, and source. See the creator README for the build and export commands.

Have source code?

Keep the audio processing and add a browser build. Our first supported conversion pipeline is for the SWH effects in this catalog. Other frameworks need their own tested adapters. The following prompt can help a developer or coding assistant prepare a project.

Add a WAM 2 browser build using the existing audio-processing implementation. Preserve desktop builds. Expose parameters, presets, and saved state. Bundle dependencies and use relative asset paths. Preserve portable interface code; otherwise provide controls for every parameter. Respect the browser sample rate and avoid blocking or allocating in the audio callback. Report unsupported dependencies instead of approximating the sound. Include native-versus-browser audio tests, applicable licenses, and a Patchwork package manifest.

Publishing is the next step.

Public uploads, isolated preview testing, creator approval, and automatic catalog publication are not enabled yet. The current catalog runs curated SWH WebAssembly builds; it does not load arbitrary WAM packages. The separate WAM package tool prepares the files for that future workflow.

You can keep your source private and build on your own computer. Do not include account credentials or private files in a browser package.