Requirements, browser support & privacy

What you need

• Live device features need a GP-200 over USB in Chrome or Edge (Web MIDI).
• Offline, you can edit patches and import/export files, but not sync or save to the unit.
• Any desktop OS , Windows, macOS or Linux , plus ChromeOS and Android. Linux is worth calling out: the official Valeton editor does not support it at all, which is a large part of why this exists.

Browser support, precisely

The dividing line is Web MIDI, and it is not a preference , Firefox and Safari have not shipped it, so there is no setting or extension that makes device sync work in them. What they can do is everything that doesn't touch the pedal: build and edit a patch, run the browser drum machine, and import or export .prst files. The loop station additionally needs Web Audio capture of the GP-200's USB audio, which means a connected device and a one-time microphone permission for the input.

Privacy

Your patches never leave your machine , there is no account and no server storing them. Every byte of decoding, editing and encoding happens in the browser tab.

The site does record anonymous usage analytics (Google Analytics) to see which features get used: no patch names, file names or device details are ever sent, ad personalisation and Google Signals are switched off, and the browser's Global Privacy Control signal turns it off entirely.

Licence & limits

GP200 Studio is free software under the GPL-3.0, and the full source is on GitHub , which also means you can audit every claim on this page rather than take it on trust. It is an independent project and is not affiliated with, endorsed by, or supported by Valeton.

Two things are known to be incomplete: writing global settings (tuner reference, global EQ) back to the unit, and mapping the expression pedal to loop-station levels. Both are blocked on protocol capture rather than on effort, and both are read-only or experimental in the UI rather than quietly unreliable.