What preset file format does GP200 Studio use?

Native .prst files, byte-for-byte the same format the official Valeton editor reads and writes, so presets move between the two freely.

Importing & exporting .prst files

The FILE row inside the PATCHES sheet handles files: IMPORT .PRST accepts native GP-200 .prst presets, and EXPORT .PRST names the current patch and downloads it as a .prst. Importing while connected also previews the patch live on the device.

Why the format matters

.prst is the GP-200's own preset format , the same files Valeton's official editor reads and writes, not a conversion or an export. Presets move between the two applications in both directions, and patches you download from other players work here unchanged. Nothing is uploaded to do it: the decoding happens in your browser, so importing a preset works with the pedal unplugged and with no network connection at all.

The initial reverse engineering of the .prst and SysEx layout came from phash/gp200editor, which is credited in the project README.

Backing up more than one patch

The FILE row is a single-patch tool. For everything at once, use the bulk ZIP export in the patch manager , the selected bank, or all 256 slots, in one archive. That is the backup to take before Bulk Apply overwrites anything.

The export dialog naming the patch before download — EXPORT: name the patch and author, then download a .prst file.

EXPORT: name the patch and author, then download a .prst file.

Frequently asked questions

What preset file format does GP200 Studio use?: Native .prst files, byte-for-byte the same format the official Valeton editor reads and writes, so presets move between the two freely.